Exactprep CGEIT Questions

An exception management process is a method for documenting and approving an exception to compliance with established IT governance policies, standards, and practices. An exception management process can accommodate the need for autonomy over technology choices by allowing a functional group to request and justify a deviation from the IT governance requirements, based on the business needs, risks, costs, and benefits. An exception management process can also help to ensure that the exceptions are reviewed and approved by the appropriate authorities, that the exceptions are monitored and reported, and that the exceptions are aligned with the IT strategy and objectives123. References: Exception Management Process Flow. IT/Information Security Exception Request Process. Strategies, Governance, Policies, Standards and Resources.

A responsive risk awareness culture is the best reflection of mature risk management in an enterprise, because it implies that the organization has a high level of risk maturity that enables it to reduce noise and focus more effectively on truly high-risk concerns, choose cost-effective solutions for the risk management priorities, and execute reliably1. A responsive risk awareness culture also means that the organization has a clear and consistent risk appetite and tolerance, and that the employees are cognizant of the relevant risks as part of their actions2. A responsive risk awareness culture also fosters trust, collaboration, and innovation among the stakeholders, and helps the organization to adapt to changing business environments and emerging risks3.

The other options are not as indicative of mature risk management in an enterprise, because they are either too narrow or too reactive. A regularly updated risk register is a useful tool for cataloguing, tracking, and mitigating risks, but it does not necessarily reflect the strategic alignment, integration, or performance of the risk management process4. Ongoing risk assessment is an essential activity for identifying and evaluating risks, but it does not guarantee that the risks are prioritized, communicated, or managed effectively5. Ongoing investment in risk mitigation is a sign of commitment to risk management, but it does not ensure that the investment is aligned with the risk appetite and tolerance, or that it delivers value to the organization5.

Understanding the enterprise’s risk tolerance is the most important step for the CTO to create the appropriate risk policies for IT, as it would help to define the acceptable level of risk exposure and the risk appetite for mobile applications. Risk tolerance is the degree of uncertainty that an enterprise is willing to accept in pursuit of its objectives, and it reflects the enterprise’s culture, strategy, and stakeholder expectations. Risk policies for IT should be aligned with the enterprise’s risk tolerance, as well as its mission, vision, and goals. The other options are not as important, as they are more related to the implementation or measurement of risk management, rather than the establishment of risk policies. References: : CGEIT Review Manual (Digital Version), Chapter 4: Risk Optimization, Section 4.3: IT Risk Management, Subsection 4.3.1: IT Risk Management Overview, Page 153 : CGEIT Review Manual (Digital Version), Chapter 4: Risk Optimization, Section 4.3: IT Risk Management, Subsection 4.3.2: IT Risk Management Process, Page 156 : Proactive IT Risk Management in an Era of Emerging Technologies

The IT program manager should first obtain confirmation from the business and a decision by the steering committee before proceeding with the requirement change request. This is because the requirement change request is a major scope change that will affect the program budget, schedule, quality, and risk. The IT program manager needs to ensure that the business owner and the steering committee are aware of the implications and benefits of the change, and that they approve it formally. The IT program manager also needs to follow the established change management process and document the change request and its approval.

Requesting additional funding from the business owner to cover the additional scope is not the first step, as it assumes that the change request is already approved and justified. The IT program manager should first seek confirmation and approval from the business owner and the steering committee before asking for more resources.

Reporting the matter to internal audit as a program deviation to be reviewed is not the first step, as it implies that the change request is a violation or a problem. The IT program manager should first communicate with the business owner and the steering committee to understand their rationale and expectations for the change request, and to present the impact analysis and alternatives.

Aligning IT with the business and agreeing to the business request is not the first step, as it disregards the role and authority of the steering committee. The IT program manager should not accept or reject the change request without consulting with the steering committee, which is responsible for overseeing and governing the program.

References := Program Management Best Practices | Smartsheet, Best Practices for Running an Ongoing Program section. Program Management: 8 Tips & Tricks for Success (Update 2023), Tip 2: Defining the control processes section. Program Management Best Practices - Project Management Institute, Comprehend the differences between programs and projects section.