Isaca Updated CGEIT Exam Questions and Answers by avery

According to the CGEIT exam content outline1, one of the subtopics under the domain of Governance of Enterprise IT is “Governance Strategy Alignment with Enterprise Objectives”. This subtopic covers the process of ensuring that the IT strategy is aligned with the business strategy and supports the achievement of enterprise goals and objectives. Therefore, the best course of action for the CIO in this situation is to align the business strategy with the IT strategy, which would help the IT team to meet the new demands and deliver value to the enterprise. References: 1: CGEIT Exam Content Outline | ISACA

 The CTO should first understand the enterprise’s risk tolerance before assessing the impact of wearable technology. This will help the CTO to align the assessment with the enterprise’s objectives, culture, and appetite for risk. The other options are important steps in the assessment process, but they are not the first ones. Creating an IT risk scorecard and prioritizing wearable technology risk require a clear understanding of the enterprise’s risk tolerance, which is the basis for defining risk criteria and thresholds. References := ISACA, CGEIT Review Manual, 7th Edition, Chapter 2: Strategic Management, Section 2.3: Risk Optimization, p. 63-64.

 Engaging stakeholders to identify and validate business requirements is the best way to improve the success rate of future IT initiatives. Stakeholders are the individuals or groups who have an interest or influence in the IT initiatives, such as business users, customers, managers, sponsors, etc. Engaging stakeholders can help:

• Understand the needs, expectations, and priorities of the stakeholders, and ensure that they are aligned with the business objectives and strategy
• Define and document the business requirements that specify what the IT initiatives should deliver in terms of functionality, quality, performance, and value
• Validate and verify that the business requirements are clear, complete, consistent, feasible, and testable
• Communicate and manage any changes or issues that may affect the business requirements or the IT initiatives

Engaging stakeholders to identify and validate business requirements can help avoid missing key functionality in the corporate applications, and ensure that they meet the stakeholder’s needs and expectations. This can also reduce the reliance on spreadsheets and databases as alternative software solutions, and increase the user satisfaction and adoption of the enterprise applications.

The other options are not the best way to improve the success rate of future IT initiatives. Engaging the business user community in acceptance testing of acquired applications is a good practice, but it is not sufficient to ensure that the applications have the key functionality that meets the business requirements. Acceptance testing is done at the end of the IT initiative lifecycle, after the applications have been developed or acquired. If the business requirements were not properly identified and validated at the beginning of the IT initiative lifecycle, acceptance testing may reveal significant gaps or defects that may be costly or difficult to fix. Establishing a process for risk and value management is a useful technique, but it does not directly address the issue of missing key functionality in the corporate applications. Risk and value management involves identifying, assessing, prioritizing, and treating the risks and benefits associated with IT initiatives. However, without clear and valid business requirements, risk and value management may not be effective or accurate. Prohibiting the use of non-approved alternate software solutions is a restrictive measure, but it does not solve the problem of missing key functionality in the corporate applications. Prohibiting the use of spreadsheets and databases may force the users to use the enterprise applications, but it may also create dissatisfaction, frustration, or resistance among them. Moreover, it may prevent them from performing their tasks efficiently or effectively if the enterprise applications do not meet their needs.

For more information on engaging stakeholders to identify and validate business requirements, you can refer to these web sources:

• Stakeholder Engagement - ISACA
• Business Requirements - ISACA
• Requirements Validation - ISACA

A vendor risk assessment is the most important consideration when integrating a new vendor with an ERP system, because it helps to identify and evaluate the potential risks or hazards associated with the vendor’s operations and products and their impact on the organization. A vendor risk assessment can cover aspects such as security, compliance, quality, reliability, performance, and contingency plans. By conducting a vendor risk assessment, the organization can mitigate the risks and ensure a smooth and secure integration with the ERP system. The other options are not as important as a vendor risk assessment, because they are either dependent on or secondary to it. IT senior management selects the vendor based on the results of the vendor risk assessment and other criteria. ERP data mapping is approved by the enterprise architect after the vendor risk assessment confirms that the vendor’s data is compatible and consistent with the ERP system. Procurement provides the terms of the contract after the vendor risk assessment validates that the vendor meets the organizational standards and obligations. References := Guide to Vendor Risk Assessment, 10 Risk Assessment Factors for ERP System Integration Projects, Ensuring Vendor Compliance and Third-Party Risk Mitigation