The Open Group OGEA-101 Exam Questions 2025

B. Describing the target architecture.

This is the primary objective of the core architecture development phases (B: Business, C: Information Systems, and D: Technology), not the preparatory Preliminary Phase.

C. Defining the Enterprise Strategy.

The enterprise strategy is a critical input to the architecture process, but its definition is a business management function that precedes and informs the Preliminary Phase.

D. Identifying the stakeholders and their requirements.

While high-level stakeholders for the EA capability are considered, identifying specific project stakeholders and their requirements is a key objective of Phase A: Architecture Vision.

1. The TOGAF® Standard, 10th Edition, The Open Group. Part II: Architecture Development Method (ADM), Chapter 5: Preliminary Phase, Section 5.2 (Objectives). This section explicitly states the objectives are to "Determine the Architecture Capability desired by the organization" and "Establish the Architecture Capability".

2. The TOGAF® Standard, 10th Edition, The Open Group. Part II: Architecture Development Method (ADM), Chapter 5: Preliminary Phase, Section 5.1 (Phase Overview). This section describes the phase as covering the "preparatory and initiation activities required to create an Architecture Capability".

3. The TOGAF® Standard, 10th Edition, The Open Group. Part II: Architecture Development Method (ADM), Chapter 6: Phase A: Architecture Vision, Section 6.2 (Objectives). This section confirms that identifying "key stakeholders and their concerns/objectives" is a primary goal of Phase A, distinguishing it from the Preliminary Phase.

A: Incorrectly assigns Objective 2 to Phase F and Objective 3 to Phase E. The initial roadmap is a Phase E output, while finalization occurs in Phase F.

B: Incorrectly assigns Objective 1 to Phase G. Phase G is for Implementation Governance, not for determining the migration strategy, which is a Phase E activity.

D: Incorrectly assigns Objective 1 to Phase F and Objective 4 to Phase G. The transition approach is set in Phase E, and stakeholder buy-in on value is secured in Phase F.

1. The Open Group. (2022). The TOGAF® Standard, 10th Edition. Van Haren Publishing.

Chapter 10, Section 10.2, "Objectives": Explicitly lists the objectives for Phase E, including: "Generate the initial complete version of the Architecture Roadmap..." and "Determine whether an incremental approach is required, and if so identify Transition Architectures...". This supports the mapping of objectives 1 and 2 to Phase E.

Chapter 11, Section 11.2, "Objectives": Explicitly lists the objectives for Phase F, including: "Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan" and "Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders". This supports the mapping of objectives 3 and 4 to Phase F.

A. Taking major improvement decisions: EA informs and supports decision-making by providing crucial analysis and context, but the authority to "take" decisions typically lies with executive management and governance bodies, not the EA function itself.

C. Controlling the bigger changes: "Controlling" suggests a rigid, command-based approach. EA's role is more accurately described as governance and guidance, ensuring changes align with the architectural vision, rather than direct, absolute control over their execution.

D. Governing the Stakeholders: EA governs the architecture and manages stakeholder requirements and concerns to ensure alignment. It does not govern the stakeholders themselves; that misrepresents the collaborative nature of the discipline.

1. The Open Group, "The TOGAF® Standard, Version 10," Document No. C220, April 2022. Section 1.2, "What is Enterprise Architecture?", Page 3, states that EA is a "discipline for proactively and holistically leading enterprise responses to disruptive forces by identifying and analyzing the execution of change toward desired business vision and outcomes."

2. The Open Group, "Open Group Enterprise Architecture Practitioner Certification Program: O-GEA 101 Study Guide," Document No. G221, April 2022. Section 2.2, "What is Enterprise Architecture?", Page 8, explicitly states, "The purpose of Enterprise Architecture is to guide effective change."

3. The Open Group, "The TOGAF® Standard, Version 10," Document No. C220, April 2022. Section 2.1, "Enterprise Architecture," Page 7, defines the purpose as optimizing the enterprise "into an integrated environment that is responsive to change and supportive of the delivery of the business strategy."

A. This describes Phase F: Migration Planning (Item 1), which focuses on creating the detailed implementation and migration plan.

B. This describes Phase H: Architecture Change Management (Item 3), which establishes procedures for managing changes to the architecture after it has been implemented.

C. This describes the central Requirements Management process (Item 4), which is a continuous activity that occurs throughout all phases of the ADM.

1. The Open Group Standard, TOGAF® Standard, 10th Edition. (2022). Part II: Architecture Development Method (ADM), Chapter 12, "Phase G: Implementation Governance", Section 12.1 Objectives. This section states the objective is to "Ensure conformance with the Target Architecture by implementation projects".

2. The Open Group Standard, TOGAF® Standard, 10th Edition. (2022). Part II: Architecture Development Method (ADM), Chapter 4, "The ADM Cycle", Figure 4-1. This figure visually places Implementation Governance as Phase G, following Migration Planning (Phase F) and preceding Architecture Change Management (Phase H).

3. The Open Group Standard, TOGAF® Standard, 10th Edition. (2022). Part II: Architecture Development Method (ADM), Chapter 11, "Phase F: Migration Planning", Section 11.1 Objectives. This section details the creation of the implementation plan, corresponding to option A.

4. The Open Group Standard, TOGAF® Standard, 10th Edition. (2022). Part II: Architecture Development Method (ADM), Chapter 13, "Phase H: Architecture Change Management", Section 13.1 Objectives. This section describes establishing the change management process, corresponding to option B.

A. Security Architecture: Security Architecture is the practice of designing controls and safeguards; it uses the output of risk assessment but is not the assessment process itself.

B. Phase A: While high-level business risks are considered in Phase A (Architecture Vision), these specific, detailed activities are part of the comprehensive Risk Management process that supports all ADM phases.

C. Phase G: This phase (Implementation Governance) deals with managing risks related to the implementation of the architecture, which occurs after the initial identification and assessment are complete.

1. The TOGAF® Standard, 10th Edition, The Open Group Standard (C220), Part III, Chapter 15, "Applying Risk Management in the ADM". Section 15.2 outlines the Risk Management Process, which begins with Risk Identification and Risk Analysis (Assessment).

2. The TOGAF® Series Guide: Integrating Risk and Security within a TOGAF® Enterprise Architecture (G151), Section 4.2, "Risk Management". This section explicitly describes the risk management process, including the steps of "Risk Identification" and "Risk Assessment".

B. Partitions are equivalent to architecture levels.

This is incorrect. Levels (Strategic, Segment, Capability) define the scope and detail of an architecture, whereas partitioning is the technique used to divide the architecture within those levels.

C. Partitions reflect the organization's structure.

This is not always true. While partitions can be based on organizational units, they can also be based on other criteria like business domains, value streams, or time periods.

D. Partitions are defined and assigned to agile Enterprise Architecture teams.

This is incorrect. Partitioning is a methodology-agnostic governance technique. It can be used with any project management or development approach, not exclusively with agile teams.

1. The TOGAF® Standard, 10th Edition, Part IV: Architecture Content Framework, Chapter 39.1 Introduction. This section states: "Partitioning can be done to simplify the development and management of the enterprise's architecture." This directly supports the correct answer (A).

2. The TOGAF® Standard, 10th Edition, Part IV: Architecture Content Framework, Chapter 39.2 Applying Partitioning to the Architecture Landscape. This chapter distinguishes between Architecture Levels (the "three levels of granularity") and the act of partitioning, demonstrating they are not equivalent (refuting B).

3. The TOGAF® Standard, 10th Edition, Part IV: Architecture Content Framework, Chapter 39.2.1 Criteria for Decomposition. This section lists multiple criteria for creating partitions, including "Subject matter (e.g., Business domain, Organizational unit)" and "Time". This shows that organizational structure is only one of several possible criteria, not the sole determinant (refuting C).

A. 1B-2D-3A-4C: Incorrectly maps Data Architecture development to Phase B and Business Architecture to Phase D.

B. 1C-2D-3B-4A: Incorrectly maps Business Architecture development to Phase D and the Architecture Vision to Phase B.

D. 1A-2B-3C-4D: Incorrectly maps Data Architecture development to Phase A and the Architecture Vision to Phase C.

1. The Open Group Standard, TOGAF® Standard, 10th Edition, (April 2022), Part II: Architecture Development Method (ADM).

Reference for 3A: Section 5.3, "Phase A: Architecture Vision - Objectives", states the first objective is to "Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture".

Reference for 2B: Section 6.3, "Phase B: Business Architecture - Objectives", states the first objective is to "Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals...".

Reference for 1C: Section 7.3, "Phase C: Information Systems Architectures - Objectives", states the first objective is to "Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision...".

Reference for 4D: Section 8.3, "Phase D: Technology Architecture - Objectives", includes developing the Target Technology Architecture. Section 8.6.3, "Perform Gap Analysis", and Section 8.7, "Outputs", confirm that the gap analysis results, which form the basis for roadmap components, are a key output of this phase.

A. Rationale: This section explains the business justification and benefits of the principle, answering why it is important, not what is required to implement it.

B. Name: The name is simply a unique, memorable identifier for the principle and contains no detail about its implementation requirements.

C. Statement: The statement is a concise declaration of the principle itself, defining the fundamental rule, not the practical steps or requirements for its execution.

1. The Open Group. (2022). The TOGAF® Standard, 10th Edition, Series Guide: The TOGAF Leader’s Guide to Establishing and Evolving an EA Capability. Van Haren Publishing. Section 10.3, "Developing Architecture Principles", describes the template. The entry for "Implications" states: "Should highlight the requirements for carrying out the principle, in terms of resources, costs, and activities/tasks."

2. The Open Group. (2018). The TOGAF® Standard, Version 9.2. Van Haren Publishing. Chapter 23, "Architecture Principles", Section 23.3, "Template for Architecture Principles". The description for "Implications" reads: "Should highlight the requirements for carrying out the principle... This will spell out the impact of adopting the principle, both in the short and long term..."

A. To identify and understand business requirements: This is incorrect. While assets from the Continuum may inform the process, techniques like Business Scenarios are specifically used in ADM Phase B to identify and understand business requirements.

B. To coordinate with the other management frameworks in use: This is incorrect. Coordinating with other frameworks (e.g., ITIL, COBIT) is a key activity of the Preliminary Phase, where the architecture practice is established and tailored to the enterprise.

C. To describe how an architecture addresses stakeholder concerns: This is incorrect. Architecture Views and Viewpoints are the specific TOGAF concepts used to frame, present, and communicate the architecture in a way that addresses specific stakeholder concerns.

1. The Open Group, TOGAF® Standard, 10th Edition, TOGAF Fundamental Content (2022).

Section 16.1, Introduction: "The Enterprise Continuum is a model for classifying architecture and solution artifacts, both internal and external to the Architecture Repository, as they evolve from generic to specific." This directly supports the correct answer (D).

Section 16.2, Enterprise Continuum: "The Enterprise Continuum provides a consistent language to communicate the differences between architectures so that architectures and their components can be re-used." This reinforces the classification and reuse purpose.

2. The Open Group, TOGAF® Standard, 10th Edition, The ADM (2022).

Section 4.3, Phase A: Architecture Vision: This section details stakeholder management and the creation of Architecture Views to address their concerns, showing why option (C) is incorrect.

Section 5.4.2, Business Scenarios: This section describes the Business Scenarios technique as a primary method "to identify and understand business requirements", which refutes option (A).

Section 3.1, Preliminary Phase: This section explains that a key objective is to "Define the relationships between management frameworks", which shows why option (B) describes a different part of the TOGAF framework.

A. Logical and Physical: These describe levels of abstraction or views within an architecture domain (e.g., Logical Data Model), not the primary domains themselves.

B. Information and Data: The TOGAF standard specifically designates "Data Architecture" as the domain name, and this option is incomplete as it omits "Application".

C. Capability and Segment: A "Capability" is a key artifact within Business Architecture, while a "Segment" is a partition of the enterprise, not a core domain.

1. The Open Group. (2022). TOGAF® Standard, 10th Edition. Van Haren Publishing. Part I, Chapter 3, Definitions. The definition for "Architecture" explicitly states: "The TOGAF framework is based on four architecture domains: Business, Data, Application, and Technology."

2. The Open Group. (2022). TOGAF® Standard, 10th Edition. Van Haren Publishing. Part II, Chapter 5, Introduction to the ADM, Figure 5-1. The graphic of the ADM cycle clearly labels the phases corresponding to the four domains: Phase B: Business Architecture, Phase C: Information Systems Architectures (Data and Application), and Phase D: Technology Architecture.

3. The Open Group. (2022). TOGAF® Standard, 10th Edition. Van Haren Publishing. Part II, Chapter 8, Phase C: Information Systems Architectures — Introduction. This section states, "Phase C involves the development of the Data and Application Architectures that will form the basis of the Information Systems Architectures for the enterprise."