Free OGEA-101 Exam Questions – 2025 Updated

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."

A. Reference Library: This component stores generic, reusable assets such as reference models, patterns, and templates, not project-specific, agreed-upon requirements.

B. Architecture Capability: This defines the organization's structure, skills, and processes for conducting architecture, not a storage area for artifacts like requirements.

D. Governance Log: This log records governance activities and decisions, such as the act of approving requirements, but it does not store the detailed requirements specifications themselves.

1. The TOGAF® Standard, 10th Edition, Part III: ADM Guidelines and Techniques, Chapter 16: Requirements Management. Section 16.3, "Outputs," identifies the "Architecture Requirements Specification" as a key output. This document contains the quantified requirements that are stored in the Architecture Repository.

2. The TOGAF® Standard, 10th Edition, Part V: Enterprise Repository, Chapter 37: Architecture Repository. This chapter describes the repository's role in holding outputs from ADM cycles. The agreed-upon requirements specification is a primary output stored here to guide the architecture work.

3. The TOGAF® Standard, 10th Edition, Part VI: Architecture Capability Framework, Chapter 41: Architecture Board. Section 41.4, "Responsibilities," outlines that the Architecture Board is responsible for the "approval of the Architecture Requirements Specification". This formal approval makes the requirements official, and they are then managed within the repository.

B. These terms (Capability, Segment, Enterprise, Federated) relate to the scope, partitioning, and governance of an architecture, not its fundamental domains.

C. These terms (Baseline, Transition, Target) describe the different states or versions of an architecture throughout the Architecture Development Method (ADM) lifecycle.

D. This option incorrectly mixes two correct domains (Application, Data) with concepts from the data hierarchy (Information, Knowledge), which are not distinct TOGAF architecture domains.

1. The Open Group. (2022). The TOGAF® Standard, 10th Edition. Van Haren Publishing. Part I, Chapter 3, Section 3.6, "Architecture Domains". This section explicitly states, "The TOGAF standard deals with four architecture domains: Business, Data, Application, Technology".

2. The Open Group. (2022). The TOGAF® Standard, 10th Edition. Van Haren Publishing. Part II, "Architecture Development Method (ADM)". The structure of the ADM directly reflects these domains in its core phases: Phase B (Business Architecture), Phase C (Information Systems Architectures, which includes Data and Application), and Phase D (Technology Architecture).

A. An application: An application is a specific software implementation. While it can be considered a type of Solution Building Block (SBB), the term "building block" is the more general and correct architectural term used by TOGAF for a package of functionality.

B. A deliverable: A deliverable is a work product resulting from a process, such as a document or a model (e.g., an Architecture Definition Document). It is an output of the architectural work, not a functional component of the architecture itself.

C. A solution architecture: A solution architecture is the architectural description of a specific solution. It is composed of building blocks but is not the building block itself; it describes how building blocks are assembled to meet a particular need.

1. The Open Group, "The TOGAF® Standard, Version 10," The TOGAF Standard, Part I: Introduction and Core Concepts, Chapter 3: Definitions. The official definition states: "Building Block: A package of functionality defined to meet the business needs across an organization."

2. The Open Group, "The TOGAF® Standard, Version 10," The TOGAF Standard, Part IV: Architecture Content Framework, Chapter 29: Building Blocks. Section 29.1 states: "This chapter describes the concept of building blocks in the TOGAF framework. Building blocks are a key part of the TOGAF framework and are used throughout the ADM."

3. The Open Group, "The TOGAF® Standard, Version 10," The TOGAF Standard, Part I: Introduction and Core Concepts, Chapter 3: Definitions. The definition for "Deliverable" is provided as: "A work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders." This distinguishes it from a functional component.

A. A-Candidate Architecture, B-Trade-off: Item A represents a person or role, not an architecture. A trade-off is a specific type of concern, but 'Concern' is the more general and correct term.

B. A-User, B-Requirement: A 'User' is a specific type of stakeholder, and a 'Requirement' is a specific way to express a concern. The terms 'Stakeholder' and 'Concern' are more foundational and encompassing.

D. A-Base Architecture, B-Target Architecture: These terms refer to the 'as-is' and 'to-be' states of an architecture, respectively. The diagram does not depict architectural states but rather the people and interests that influence them.

1. The TOGAF® Standard, 10th Edition, Chapter 3: Definitions.

Section 3.89: Defines Stakeholder as: "An individual, team, organization, or class thereof, having an interest in a system."

Section 3.25: Defines Concern as: "An interest in a system relevant to one or more of its stakeholders."

2. ISO/IEC/IEEE 42010:2011, Systems and software engineering — Architecture description.

Section 5.2, Conceptual Model: Figure 1 in this standard presents the conceptual model of an architecture description, which explicitly shows that a "stakeholder" has a "concern" and the "architecture description" addresses that "concern". The exhibit in the question is a direct visual representation of this standardized model.

3. The TOGAF® Standard, 10th Edition, Part III, Chapter 21: Architecture Views and Viewpoints.

Section 21.2, Views, Viewpoints, and Stakeholders: "The stakeholders and their concerns are the starting point for the development of an architecture description." This statement reinforces the relationship depicted in the exhibit.

Statement 2: This describes a desired business outcome of effective Enterprise Architecture and governance, not a core principle or mechanism of the governance function itself.

Statement 4: Similar to statement 2, this is a high-level benefit resulting from a well-executed and well-governed architecture practice, rather than a defining characteristic of governance.

1. The TOGAF® Standard, Version 10, TOGAF® Series Guide: Architecture Governance.

Section 4.1.1, Process: States that the governance process must be "transparent" and "accountable". This directly supports Statement 3, as making actions available for inspection is a key aspect of transparency and accountability.

Section 3.1, Key Concepts of Governance: Discusses governance as a "system of controls" over the architecture. Establishing processes to avoid conflicts of interest (Statement 1) is a fundamental control mechanism to ensure the integrity of decision-making.

2. The Open Group Standard, TOGAF® Version 9.2.

Part VII, Section 50.1, Introduction: Defines Architecture Governance as the practice of managing and controlling architectures. It emphasizes that governance is necessary to "manage risk and ensure compliance," which inherently requires transparent processes (Statement 3) and mechanisms to prevent biased decision-making due to conflicts of interest (Statement 1).

A. Requirements Management: This is a dynamic, continuous process that runs in parallel with all ADM phases to manage architecture requirements, not a specific technique for creating the initial vision document.

B. Architecture Principles: These are foundational rules and guidelines that constrain the architecture. They are a key input to and are often refined during Phase A, but they are not the technique used to develop the vision itself.

C. Gap Analysis: This technique is primarily used in the subsequent Phases B, C, and D to compare the Baseline and Target Architectures to identify what needs to be developed, not for creating the initial vision.

1. The Open Group Standard, TOGAF® Standard, 10th Edition. (2022). Part II: Architecture Development Method (ADM), Chapter 5, Phase A: Architecture Vision, Section 5.2, Approach. This section states, "Business Scenarios are an appropriate and useful technique to discover and document business requirements, and to articulate an Architecture Vision that will respond to those requirements."

2. The Open Group Standard, TOGAF® Standard, 10th Edition. (2022). Part III: ADM Guidelines and Techniques, Chapter 23, Business Scenarios, Section 23.3, Use in the ADM. This section explicitly details the use of Business Scenarios in Phase A for creating the Architecture Vision.

3. The Open Group Standard, TOGAF® Standard, 10th Edition. (2022). Part III: ADM Guidelines and Techniques, Chapter 25, Gap Analysis, Section 25.3, Use in the ADM. This section confirms that Gap Analysis is used in Phases B, C, D, and E, not Phase A.

A. Phase E: This phase, Opportunities and Solutions, focuses on identifying delivery vehicles (projects) and creating the Architecture Roadmap, not on governing the actual implementation.

C. Phase A: This phase, Architecture Vision, is concerned with establishing the project, defining its scope, and securing stakeholder buy-in at the very beginning of the ADM cycle.

D. Phase F: This phase, Migration Planning, focuses on creating a detailed Implementation and Migration Plan. It finalizes the plan before the governance activities described in the table take place.

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

Reference for Correct Answer (B): Part II, Chapter 12, "Phase G: Implementation Governance". The objectives, steps, and outputs listed in the question's table are detailed in Sections 12.2 ("Objectives"), 12.4 ("Steps"), and 12.5 ("Outputs"), respectively.

Reference for Incorrect Option (A): Part II, Chapter 10, "Phase E: Opportunities & Solutions".

Reference for Incorrect Option (C): Part II, Chapter 6, "Phase A: Architecture Vision".

Reference for Incorrect Option (D): Part II, Chapter 11, "Phase F: Migration Planning".

A. This describes an activity within the requirements management process, such as a gap analysis, rather than the purpose of the specification artifact itself.

C. The document that is sent from a sponsor to trigger an architecture development cycle is the Request for Architecture Work.

D. The document that defines the scope and approach for an architecture project is the Statement of Architecture Work.

1. The Open Group Standard, TOGAF® Standard, 10th Edition (April 2022). Part IV: Architecture Content Framework, Chapter 29, Section 29.4, "Architecture Requirements Specification". The purpose is explicitly stated as: "To provide a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture."

2. The Open Group Standard, TOGAF® Standard, 10th Edition (April 2022). Part IV: Architecture Content Framework, Chapter 29, Section 29.48, "Request for Architecture Work". This section defines the purpose of this artifact as triggering the architecture work.

3. The Open Group Standard, TOGAF® Standard, 10th Edition (April 2022). Part IV: Architecture Content Framework, Chapter 29, Section 29.54, "Statement of Architecture Work". This section defines the purpose of this artifact as defining the scope and approach for the architecture project.

A: This option mislabels all components. B represents a governing body of people, not a "Governance Repository" or "Board Repository".

B: This option incorrectly identifies B as a "Governance Repository". The diagram depicts a governing body, which is a group of stakeholders, not a data store.

D: This option incorrectly labels A as a generic "Enterprise Repository" and B as a "Board repository", which is not a standard TOGAF term for a governing body.

The TOGAF® Standard, 10th Edition, The Open Group, 2022. Part VI, Chapter 45, "Establishing an Architecture Capability", Figure 45-1 "Structure of the Architecture Capability". This figure directly maps to the exhibit, identifying the key components as the Architecture Board (Governing Board) and the Architecture Repository within the overall Architecture Capability.

The TOGAF® Standard, 10th Edition, The Open Group, 2022. Part VI, Section 45.2.2, "Architecture Board". This section details the role of the governing body shown as item B.

The TOGAF® Standard, 10th Edition, The Open Group, 2022. Part VI, Section 45.2.5, "Architecture Repository". This section describes the purpose and structure of the repository shown as item A.

B. Organizations: An organization is typically a single legal entity (e.g., one company, one government agency), whereas the question describes collaborations among multiple organizations.

C. Business Units: Business units are internal divisions or departments within a single organization, not partnerships between separate external entities as described.

D. Architectures Scopes: Architecture scope defines the breadth and depth of the enterprise to be covered by an architecture effort, but it is not the enterprise itself. The scenarios describe the subject of the architecture, which is the enterprise.

1. The Open Group, "TOGAF® Standard, 10th Edition," 2022. In Part I, Chapter 3, Section 3.31 "Enterprise", the standard defines an enterprise as "Any collection of organizations that has a common set of goals" and notes it can be an "extended enterprise, which includes partners, suppliers, and customers".

2. The Open Group, "TOGAF® Version 9.2," 2018. In Part I, Chapter 2, Section 2.5 "What is an enterprise?", it explicitly states, "In addition, the TOGAF framework can be used to architect organizations of organizations, such as a government agency, a consortium, or a supply chain." This directly maps to the examples in the question.

A. The Architecture Vision: This document provides a high-level, aspirational view of the target architecture and its business value; it is not a formal governance agreement for implementation.

B. The Statement of Architecture Work: This document defines the scope and plan for conducting an architecture development project, not for governing the subsequent implementation of that architecture.

D. The Architecture Definition Document: This document formally describes the architecture itself (the "what"), but it is not the mechanism that enforces adherence during implementation (the "how").

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

Section 39.4.1, Architecture Contracts: "The Architecture Contract is the joint agreement between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture... The Architecture Contract is the governing document for all implementation and migration activities."

Section 13.2, Phase G: Implementation Governance, Objectives: "Ensure conformance with the Target Architecture by implementation projects." This is achieved through mechanisms like the Architecture Contract.

Section 13.5.2, Phase G: Implementation Governance, Outputs: Lists "Architecture Contract (signed)" as a key output, confirming its role in this phase.

A. risk tolerance: This defines the level of risk an organization is willing to accept to achieve its objectives, which is a separate governance concern, not the list of work items.

B. business continuity: This refers to the plans and strategies for ensuring an organization can operate during and after a disruptive event, which is unrelated to defining product scope.

D. operating model: This is a much broader concept describing how an organization delivers value, including its structure, processes, and technology; the backlog is an input to, not the definition of, the entire model.

1. The Open Group. (2021). Open Agile Architecture™ Standard, Version 1.0 (C212). The Open Group. Section 4.3.3, "Architecture to Support Portfolio", Page 16. The document states, "The Architecture to Support Portfolio will identify what products the Enterprise needs, the boundary of the products, and what constraints a product owner has. This defines the Enterprise’s backlog."

B. Subordinate, and Superior Architecture: These terms describe hierarchical relationships between architectures, not the distinct purposes or types of architecture themselves.

C. Discreet, and Cohesive: These are qualitative attributes of an architecture, not standard categories that define its scope or planning horizon within the TOGAF framework.

D. Segment, and End-to-end Target Architecture: While "Segment" architecture is a valid TOGAF concept, this specific four-part framework is explicitly defined in the TOGAF Leader's Guide, and "End-to-end Target Architecture" is not a standard category.

1. The Open Group, "The TOGAF® Standard — The TOGAF® Leader’s Guide to Establishing and Evolving an EA Capability", Version 10, 2022. Section 3.4, "What is the Relationship between Enterprise Architecture and Other Disciplines?", and specifically Figure 3.2, "Positioning Enterprise Architecture". This source directly presents and explains the relationship between EA and Strategy, Portfolio, Project, and Solution Delivery as the framing context.

B. A-Enterprise Architecture, B-Architecture Building Blocks, C-Solutions Building Blocks: This is incorrect because the diagram depicts the continua that contain building blocks, not the building blocks or the overall Enterprise Architecture itself.

C. A-Architecture Vision, B-Business Architecture, C-Information Systems Architecture: These are distinct domains or phases within the Architecture Development Method (ADM), not the components of the Enterprise Continuum.

D. A-Enterprise Strategic Architecture, B-Segment Architecture, C-Solutions Architecture: This describes levels of architecture partitioning or scope (strategic, segment, capability), which is a different concept from the asset classification model of the Enterprise Continuum.

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

Section 35.1, Introduction: "The Enterprise Continuum is a view of the Architecture Repository that provides methods for classifying architecture and solution artifacts... It is composed of the Architecture Continuum and the Solutions Continuum."

Figure 35-1, The Enterprise Continuum: This figure is the exact diagram shown in the question, explicitly labeling the outer box as "Enterprise Continuum", the middle box as "Architecture Continuum", and the inner box as "Solutions Continuum".

Section 35.2, Enterprise Continuum Components: This section details the structure, stating, "The Enterprise Continuum consists of the Architecture Continuum and the Solutions Continuum."

B. Name: This is simply the unique title used to identify the principle and does not contain any descriptive content about its benefits.

C. Implications: This section describes the consequences of adopting the principle, including required resources, costs, and impacts on projects and processes, not the benefits.

D. Statement: This is the formal, unambiguous declaration of the principle itself, stating the fundamental rule without providing the justification or business value.

1. The Open Group. (2018). The TOGAF® Standard, Version 9.2 (The Open Group Standard No. C182). Van Haren Publishing. Section 20.3, "Template for Architecture Principles". The official standard explicitly states that the Rationale should highlight "the business benefits of adhering to the principle" and "the relationship to other principles".

2. The Open Group. (2018). TOGAF® 9 Foundation Study Guide, 4th Edition (The Open Group Guide No. G189). Van Haren Publishing. Chapter 13, "Architecture Principles". This study guide reinforces that the Rationale explains the business value and benefits of the principle.

3. Purdue University. (n.d.). Enterprise Architecture Principles. Purdue University IT Architecture. The university's documentation on EA principles, which aligns with TOGAF, defines the 'Rationale' as the section that "explains why the principle is needed" and includes the "business benefits".