Risk appetite determined by senior management reflects the enterprise's willingness to accept certain levels of risk, including noncompliance. This decision underscores the strategic trade-offs made in risk management, a key element inGovernance and Risk Policy Alignment.

When updating a risk register with the results of an IT risk assessment, the risk practitioner should log the known risk scenarios, because they are the risk scenarios that have been identified and assessed in the IT risk assessment process. The risk register should document and track the known risk scenarios, their characteristics, their status, and their responses. The other options are not the ones that should be logged, because:
* Option A: High impact scenarios are the risk scenarios that have a high potential impact on the business objectives and processes, but they are not the only ones that should be logged. The risk register should include all the known risk scenarios, regardless of their impact level.
* Option B: High likelihood scenarios are the risk scenarios that have a high probability of occurrence, but they are not the only ones that should be logged. The risk register should include all the known risk scenarios, regardless of their likelihood level.
* Option C: Treated risk scenarios are the risk scenarios that have been addressed by the risk response actions, but they are not the only ones that should be logged. The risk register should include all the known risk scenarios, regardless of their treatment status. References = Risk and Information Systems Control Study Manual, 7th Edition, ISACA, 2020, p. 108.

An IT risk register is a document that is used as a risk management tool to identify, analyze, and track the potential risks related to the use of information technology within an organization. An IT risk register helps management to understand the organizational risk profile, which is a comprehensive and structured representation of the risks that the organization faces. The risk profile helps the organization to understand its risk exposure, appetite, and tolerance, and to align its risk management strategy with its business objectives and context. The risk register is an essential input for creating and updating the risk profile, as it provides the data and analysis of the risks that need to be prioritized and addressed12. The other options are not the best answers, as they are either not directly shown or derived from the IT risk register. Aligning IT processes with business objectives is a goal of IT governance, which may be influenced by the IT risk register, but not solely determined by it. Communicating the enterprise risk management policy is a responsibility of the senior management and the board of directors, which may use the IT risk register as a reference, but not as the main source. Staying current with existing control status is a function of IT audit and assurance, which may rely on the IT risk register as a basis, but not as the only evidence. References = Risk Register: A Project Manager's Guide with Examples [2023] * Asana; Complete Guide to IT Risk Management | CompTIA

Risk is inefficiently controlled when the annual cost of the control exceeds the annual loss expectancy (ALE) of the risk, as this means that the organization is spending more on the control than the potential loss that the control is supposed to prevent or reduce. This indicates that the control is not cost-effective or optimal, and that the organization should consider alternative or complementary controls that can lower the cost or increase the benefit of the risk management. Control is ineffective and should be strengthened when the control does not reduce the likelihood or impact of the risk to an acceptable level, regardless of the cost. Risk is efficiently controlled when the annual cost of the control is equal to or less than the annual loss expectancy (ALE) of the risk, as this means that the organization is spending less or equal on the control than the potential loss that the control is supposed to prevent or reduce. Control is weak and should be removed when the control does not provide any benefit or value to the risk management, regardless of the cost. References = CRISC Certified in Risk and Information Systems Control - Question205; ISACA Certified in Risk and Information Systems Control (CRISC) Certification Exam Question and Answers, question 205.