Comprehensive and Detailed Explanation:
The CGEIT Review Manual 8th Edition, in its Governance of Enterprise IT domain, emphasizes the role of enterprise architecture (EA) in ensuring IT investments align with business strategies. If EA is not being leveraged, governance processes must enforce its use during project execution.
Option B: Require EA review at key milestones is the best approach. Integrating EA reviews into project stage gates (e.g., design, implementation) ensures that IT investments adhere to the EA’s standards, principles, and roadmap. For example, a review might confirm that a new system aligns with the EA’s technology stack. The manual likely references COBIT 2019’s APO03-Managed Enterprise Architecture, which advocates for EA integration in project governance.
Option A: Form a team to update EA regularly is proactive but doesn’t enforce EA use in projects.
Option C: Publish and train on the EA document raises awareness but lacks enforcement.
Option D: Adopt a globally recognized EA framework is unnecessary if an EA exists, as the issue is leverage, not framework choice.
Double Verification: The answer aligns with COBIT’s EA governance processes and the CGEIT domain’s focus on project alignment. Milestone reviews are a standard ISACA practice for EA enforcement.
ISACA CGEIT Review Manual 8th Edition, Domain 1: Governance of Enterprise IT (focus on enterprise architecture).
COBIT 2019, APO03-Managed Enterprise Architecture.
ISACA Glossary (for definitions of EA), available at https://www.isaca.org/resources/glossary.
