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

Explanation:
Strategy Portfolio Project Solution Delivery are the four purposes that typically frame the planning horizon, depth and breadth of an Architecture Project, and the contents of the EA Repository. They correspond to different levels of abstraction and granularity in the architecture development process.
Reference: The TOGAF® Standard, Version 9.2 - The Open Group, Section 2.4 Architecture Repository.

Explanation:
Comprehensive and Detailed Explanation
When defining the scope of an architecture, TOGAF identifies four dimensions that need to be considered:
Breadth C This dimension addresses the extent of the enterprise that will be impacted by the architecture. It answers the
question: How much
of the enterprise is covered? For example, does the scope include the entire enterprise, a business unit, a division, or just a single organizational function?
Depth C This refers to the level of detail to be covered. For instance, will the architecture describe high-level capabilities, or will it go into detailed system design?
Time Period C This defines the planning horizon of the architecture. It could be short-term (tactical), medium-term, or long-term (strategic).
Architecture Domains C This refers to which domains are covered: Business, Data, Application, and Technology. The scope may include all or just a subset of these domains.
Project Scope (sometimes discussed separately) C Focuses on which specific programs, portfolios, or projects will be impacted.
Among these, the dimension that specifically relates to the extent of the enterprise is Breadth.
Why the other options are incorrect
A. Architecture Domains: Refers to the domains covered (Business, Data, Application, Technology), not the extent of the enterprise.
B. Depth: Refers to the level of detail, not the enterprise extent.
C. Project: Refers to the program or initiative focus, not enterprise coverage.
Reference
The Open Group, TOGAF® Standard, Version 9.2, Part II: ADM ― Preliminary Phase (scope considerations).
The Open Group, TOGAF® 9 Certified Study Guide ― discussion of the dimensions of architecture scope (Breadth, Depth, Time Period, Architecture Domains).

Explanation:
The illustration shows the relationship between the Enterprise Continuum, the Architecture Continuum, and the Solutions Continuum, which are key concepts in the TOGAF framework. The Enterprise Continuum is a view of the Architecture Repository that shows how generic foundation architectures can be leveraged and specialized to support the requirements of an individual organization. The Architecture Continuum specifies a structured classification for architectural artifacts, such as models, patterns, and descriptions, that can be reused and adapted across different domains and levels of abstraction. The Solutions Continuum identifies implemented solutions that support various stages of business and IT capability evolution, such as common systems, industry solutions, and organization-specific solutions. The illustration also shows how the architecture context and requirements are influenced by external factors, such as business drivers, stakeholders, and standards, and how they shape the generic and specific architectures and solutions. The illustration also shows how the deployed solutions become part of the architecture context for future iterations of the architecture development cycle.
Reference: • TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 6: Architecture Repository, Section 6.2 Enterprise Continuum.
• TOGAF Standard, 10th Edition, Part IV: Architecture Content Framework, Chapter 35: Enterprise Continuum and Tools, Section 35.1 Introduction.

Explanation:
• Architecture partitioning is not the same as architecture levels (so 1 is incorrect).
• It allows different teams of architects to work on different parts of the architecture in parallel (2 is correct).
• TOGAF does not prescribe a fixed partitioning model; it provides guidance (so 3 is incorrect).
• Partitioning is used to simplify management of Enterprise Architecture in large or complex organizations (4 is correct).
Reference: TOGAF® Standard, Version 9.2, Part III: ADM Guidelines and Techniques ― Architecture Partitioning.