Administrative controls are the best controls to be strengthened by a clear organizational code of ethics, because they are the policies, procedures, standards, and guidelines that define the expected behavior and conduct of the employees and management. A code of ethics is an example of an administrative control that sets the ethical principles and values of the organization and helps to prevent or deter unethical or illegal actions. The other options are not the best controls to be strengthened by a clear organizational code of ethics, because they are not directly related to the ethical culture or governance of the organization. Detective controls are the controls that monitor and report the occurrence of unwanted events or incidents. Technical controls are the controls that use hardware, software, or network devices to protect the information systems and data. Preventive controls are the controls that prevent or avoid the occurrence of unwanted events or incidents. References = ISACA Certified in Risk and Information Systems Control (CRISC) Certification Exam Question and Answers

The percentage of system availability is the most important key performance indicator (KPI) to establish in the service level agreement (SLA) for an outsourced data center. This KPI measures the uptime or reliability of the systems hosted by the data center provider, and reflects the ability of the provider to meet the customer' s expectations and requirements for system performance and accessibility. A high percentage of system availability indicates that the provider is delivering consistent and quality service, while a low percentage of system availability indicates that the provider is experiencing frequent or prolonged system failures or disruptions, which can negatively affect the customer's business operations and reputation. Therefore, the percentage of system availability is a critical factor for evaluating the effectiveness and efficiency of the data center provider, and should be clearly defined and monitored in the SLA. The other options are not the most important KPIs to establish in the SLA for an outsourced data center, as they do not directly measure the quality or reliability of the service provided. The percentage of systems included in recovery processes is a measure of the scope or coverage of the disaster recovery plan (DRP) of the data center provider, but it does not indicate how well the provider can execute the DRP or restore the systems in the event of a disaster. The number of key systems hosted is a measure of the capacity or utilization of the data center provider, but it does not indicate how efficiently or securely the provider can manage the systems. The average response time to resolve system incidents is a measure of the responsiveness or agility of the data center provider, but it does not indicate how effectively or proactively the provider can prevent or mitigate system incidents. References = Risk and Information Systems Control Study Manual, 7th Edition, Chapter 3, Section
3.2.3.4, Page 140.

Outsourcing IT security operations is a common practice that can provide benefits such as cost savings, access to specialized skills, and improved service quality12. However, outsourcing also introduces risks such as loss of control, dependency, contractual issues, and service failures12.
When an organization outsources its IT security operations to a third party, it does not transfer the accountability for the risk associated with the outsourced operations. Accountability is the obligation to answer for the execution of one's assigned responsibilities34.
The organization's management is ultimately accountable for the risk associated with the outsourced operations, as they are responsible for defining the organization's risk appetite, strategy, and objectives, and for ensuring that the organization's IT security operations are aligned with them34.
The organization's management is also accountable for selecting, contracting, and overseeing the third party, and for ensuring that the third party meets the agreed service levels, standards, and compliance requirements34.
The organization's management is also accountable for monitoring and reporting the risk associated with the outsourced operations, and for taking corrective actions when necessary34.
The other options are not ultimately accountable, but rather have different roles and responsibilities in relation to the outsourced operations. For example:
The third party's management is responsible for delivering the IT security services according to the contract, and for managing the risk within their own organization34. They are accountable to the organization's management, but not to the organization's stakeholders.
The control operators at the third party are responsible for implementing and operating the IT security controls according to the service specifications, and for reporting any issues orincidents to the organization's management34. They are accountable to the third party's management, but not to the organization's management or stakeholders.
The organization's vendor management office is responsible for facilitating the relationship between the organization and the third party, and for supporting the organization's management in the outsourcing process34. They are accountable to the organization's management, but not for the risk associated with the outsourced operations. References =
1: Outsourcing IT Security: A Risk Management Perspective, ISACA Journal, Volume 2, 2019
2: The Cyber Security Risks Of Outsourcing, Cybersecurity Intelligence, January 4, 2022
3: Accountability for Information Security Roles and Responsibilities, Part 1, ISACA Journal, Volume 5, 2019
4: Risk IT Framework, ISACA, 2009

The best course of action when a risk practitioner identifies a database application that has been developed and implemented by the business independently of IT is to include the application in IT risk assessments. IT risk assessments are the process of identifying, analyzing, and evaluating the IT-related risks that could affect the achievement of the enterprise's objectives. By including the application in IT risk assessments, the risk practitioner can identify the potential threats, vulnerabilities, and impacts associated with the application, and recommend the appropriate controls and mitigation strategies to reduce the risk to an acceptable level.
Escalating the concern to senior management, documenting the reasons for the exception, and proposing that the application be transferred to IT are not the best courses of action, as they do not address the risk exposure and impact of the application, and may not be feasible or desirable for the business. References = CRISC Review Manual, 6th Edition, ISACA, 2015, page 47.

The control owner is the person who is accountable for ensuring that a control is designed, implemented, and operated effectively to mitigate risk. The control owner is also responsible for monitoring the performance of the control and reporting any issues or deficiencies. The risk manager is the person who oversees the risk management process and ensures that risks are identified, assessed, and treated appropriately. The control operator is the person who executes the control activities on a day-to-day basis. The risk treatment owner is the person who is accountable for implementing the risk response strategy and ensuring that the residual risk is within the acceptable level. References = Risk and Information Systems Control Study Manual, 7th Edition, Chapter 4, Section 4.2.1, p. 181.