OGEA-101 Exam Questions 2026 – Practice Test with Verified Answers

Explanation:
“Other potential sources of gaps: People gaps (e.g., cross-training requirements); Process gaps… Tools gaps… Financial gaps…” Open Group Publications
Reference: The Open Group/OMG/Integration Consortium White Paper, TOGAF/MDA Mapping―Gap Analysis discussion and examples.

Explanation:
This description matches Phase B: Business Architecture. In TOGAF, Phase B is the phase in which the architect develops the target Business Architecture and identifies the gaps between the baseline and target states. The phase is not limited to producing models only; it also ensures that the resulting domain architecture is reviewed and approved by stakeholders and that the implications of the gaps are understood. The wording in the question is characteristic of the domain architecture phases, and among the options provided, Phase B is the only domain architecture phase listed.
Phase A is concerned with developing the Architecture Vision, scope, constraints, and stakeholder consensus at a high level. The Preliminary Phase establishes the architecture capability and governance framework. Phase E is focused on Opportunities and Solutions, where solution building blocks, work packages, and transition approaches are identified. None of those primarily describe development of a domain architecture with stakeholder approval and identified gaps.
Because the question refers to a domain architecture, stakeholder approval, and a defined set of gaps to be addressed, the best answer is Phase B. It represents the ADM phase where the Business Architecture is formally developed and agreed.

Explanation:
Business scenarios are a technique for capturing, clarifying, and communicating the functional and non-functional requirements of a system. Business scenarios describe the business environment, the actors involved, the desired outcomes, and the processes or rules that govern the behavior of the system. Business scenarios are useful for ensuring that the architecture addresses the real needs and concerns of the stakeholders, and for validating and testing the architecture against expected situations. Business scenarios are developed in Phase A: Architecture Vision of the ADM cycle, and refined and updated throughout the other phases3
Reference: 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 26: Business Scenarios: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision

Explanation:
Risk Management is the process of identifying, assessing, and responding to risks that may affect the achievement of the enterprise’s objectives. Risk Management involves balancing positive and negative outcomes resulting from the realization of either opportunities or threats.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.3 Risk Management.

Explanation:
In TOGAF, deliverable 2 is correctly identified as Architecture Contracts. These are the formal joint agreements between development partners, sponsors, and in some cases implementation organizations, covering the expected deliverables, quality measures, and fitness-for-purpose of the architecture. Their role is to ensure that architecture intent is translated into governed and measurable commitments. Architecture Contracts are especially important in implementation governance because they define expectations, conformance requirements, and accountability between parties involved in the architecture and delivery process.
Deliverable 3 is the Request for Architecture Work. This is the formal initiating document sent from the sponsoring organization to the architecture function to trigger the start of a new architecture development cycle. It provides the initial authorization to begin the architecture effort and acts as a formal signal that architecture work is needed. It is one of the recognized inputs used to begin structured ADM activity.
The other options do not match the definitions given. The Architecture Definition Document describes the architecture itself, not joint agreements. A Change Request is used later to propose modifications. Architecture Vision and Architecture Requirements Specification are different ADM outputs with different purposes.
Therefore, the correct mapping for labels 2 and 3 is Architecture Contracts and Request for Architecture Work, which is Option B.