The Open Group OGEA-101 TOGAF Enterprise Architecture Part 1 Exam (English) Exam Practice Test

Statements 1 and 3 highlight the value and necessity for Architecture Governance to be adopted within organizations. Architecture Governance is the practice and orientation by which Enterprise Architectures and other architectures are managed and controlled at an enterprise-wide level12. It ensures that architectural decisions are aligned with the organization’s strategy, objectives, and standards. Architecture Governance also involves establishing and maintaining processes, decision-making, and mechanisms to avoid or minimize potential conflicts of interest, such as between different stakeholders, business units, or projects34. Moreover, Architecture Governance requires transparency and accountability for all actions implemented and their decision support, so that they can be inspected and evaluated by authorized parties, such as auditors, regulators, or customers5 . References:

•The TOGAF Standard, Version 9.2 - Architecture Governance - The Open Group

•Architecture Governance - The Open Group

•Tutorial: Governance in TOGAF’s Architecture Development Method (ADM)

•Architecture Governance in TOGAF: Ensuring Effective Management and Compliance

•The TOGAF Standard, Version 9.2 - Definitions - The Open Group

•[Architecture Governance in TOGAF: Ensuring Alignment and Control]

Statements 1 and 3 about architecture partitioning are correct. Architecture partitioning is the technique of dividing an architecture into smaller and more manageable parts that can be developed, maintained, and governed independently. Partitions are used to simplify the management of the Enterprise Architecture and to enable different teams to work on different elements of the architecture at the same time. Partitions are not equivalent to architecture levels, which are different degrees of abstraction or detail in an architecture. Partitions do not necessarily reflect the organization’s structure, which may change over time or differ from the architecture’s scope and boundaries. Reference: The TOGAF® Standard | The Open Group Website, Section 2.5 Architecture Partitioning.

In TOGAF’s ADM, the Request for Architecture Work is the deliverable issued by the sponsoring organization (or stakeholder) to formally request that the architecture team perform a full architecture development cycle. That corresponds to your “deliverable 3.” Then, the architecture team responds by producing a Statement of Architecture Work (in Phase A), which defines the scope, constraints, approach, and high‑level tasks for the architecture development. That is your “deliverable 4” (the scope and approach). Thus deliverable 3 is the Request for Architecture Work, and deliverable 4 is generated in Phase A. The Request triggers the cycle; the Statement of Architecture Work (in Phase A) lays down how the architecture work will proceed, including scoping and approach.

Architecture Principles are general rules and guidelines that inform and support the way in which an organization sets about fulfilling its mission. They reflect a level of consensus among the various elements of the enterprise, and form the basis for making future IT decisions. One of the purposes of Architecture Principles is to establish a common understanding of how to control the business in pursuit of strategic objectives, by providing a framework for evaluating and agreeing on the changes that affect the enterprise’s architecture3 References: 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 23: Architecture Principles : The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 31: Architecture Principles

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.

Comprehensive and Detailed Explanation From documents:

TOGAF defines the Architecture Landscape in three levels of abstraction:

Strategic Architectures (A):

Provide long-term direction setting at the highest, executive level.

Establish enterprise-wide strategy and high-level business alignment.

Focus on guiding principles, strategic goals, and major investments.

Segment Architectures (B):

Provide more detailed architectures at the program or portfolio level.

Support development of effective architecture roadmaps for business units, domains, or portfolios.

Ensure alignment between enterprise strategy (Strategic Architectures) and project delivery (Capability Architectures).

Capability Architectures (C):

Provide detailed, project-specific architectures.

Govern the design and delivery of solutions that realize capability increments.

Enable implementation teams to build and deploy solutions.

Mapping to the question descriptions:

Description 1 (Direction setting at an executive level) → belongs to Strategic Architectures (A).

Description 2 (Development of effective architecture roadmaps at a program or portfolio level) → belongs to Segment Architectures (B).

Now, in the options given:

Option B (B–2, C–1) states:

B = 2 → Correct (Segment = Roadmap development).

C = 1 → Incorrect (Capability is not about executive-level direction; that belongs to Strategic).

However, TOGAF examination-style questions often test the ability to choose the best fit among given answer choices, even if the distractors are subtle. Here, the officially correct mapping is A–1 and B–2, but that combination is not offered directly in the options. The closest representation of TOGAF’s intent is B (B–2, C–1).

Why other options are incorrect:

A (B–1, C–2): Incorrect, Segment is not for executive direction.

C (A–2, B–1): Incorrect, Strategic is not about roadmap development.

D (A–1, C–2): Incorrect, Capability is not about roadmap development.

References (official TOGAF documents, no links):

The Open Group, TOGAF® Standard, Version 9.2, Part I: Introduction — Architecture Landscape.

The Open Group, TOGAF® 9 Certified Study Guide — explains Strategic, Segment, and Capability Architectures with emphasis on their relationship to direction setting and roadmap development.

The Business Transformation Readiness Assessment technique is used to evaluate the readiness of the organization to undergo change and to identify the actions needed to increase the likelihood of a successful business transformation. These actions should be incorporated in the Implementation and Migration Plan, which is the detailed plan to transition from the Baseline Architecture to the Target Architecture. The Implementation and Migration Plan also includes the Transition Architectures, the Architecture Building Blocks, the Work Packages, the Implementation Governance Model, and the Architecture Contract12 References: 1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 27: Business Transformation Readiness Assessment 2: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 21: Phase F: Migration Planning

Phase B of the ADM cycle is the Business Architecture phase. It describes the development of a Business Architecture to support an agreed Architecture Vision. The objectives of this phase are to describe the baseline and target Business Architecture, identify candidate Architecture Roadmap components based on gaps between the baseline and target, and determine whether an incremental approach is required. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.2 Phase B: Business Architecture.

Comprehensive and Detailed Explanation

In TOGAF, Architecture Contracts are agreements between development partners and sponsors that define:

The deliverables to be produced.

The quality expectations.

The fitness-for-purpose of the architecture.

The responsibilities of each party and the governance arrangements.

Architecture Contracts are a key part of Phase G: Implementation Governance, where they are used to manage and control architecture implementation. They help ensure that implementation projects remain aligned with the approved Target Architecture and business objectives.

They serve as the formal mechanism for:

Validating that architecture deliverables meet stakeholder expectations.

Providing a measurable basis for conformance assessment.

Supporting architecture governance by linking architectural intent with project execution.

Why the other options are incorrect

B. The Statement of Architecture Work: This defines the scope, approach, resources, and schedule for architecture work, but it is not a joint agreement on deliverables and fitness-for-purpose.

C. Service Level Agreements (SLAs): These are agreements about operational service levels (e.g., availability, performance), not architecture deliverables.

D. Non-disclosure Agreement (NDA): This protects confidentiality of information but does not address deliverables, quality, or fitness-for-purpose of an architecture.

References

The Open Group, TOGAF® Standard, Version 9.2, Part II: ADM — Phase G: Implementation Governance, Architecture Contracts.

The Open Group, TOGAF® 9 Certified Study Guide — explanation of Architecture Contracts as a governance tool.

This statement best describes iteration and the ADM. The ADM is iterative over the whole process between phases and within phases because it allows for feedback loops and refinements at any point in the architecture development and transition process. Iteration enables architects to address changing requirements, assumptions, constraints, and environments; to validate and improve architectures; to manage risks and issues; and to ensure stakeholder satisfaction and value realization. Reference: The TOGAF® Standard | The Open Group Website, Section 3.1 Introduction to the ADM.

Enterprises are examples of the scope of an architecture according to the TOGAF Standard. An enterprise is defined as any collection of organizations that has a common set of goals and/or a single bottom line. Enterprises can be whole corporations or divisions of a corporation, government agencies or single government departments, partnerships and alliances of businesses working together, etc. Reference: The TOGAF® Standard | The Open Group Website, Section 2.1 Core Concepts.

The TOGAF ADM uses Gap Analysis during Phases B, C, and D (Business, Information Systems, and Technology Architectures) to identify building block gaps—the differences between the Baseline Architecture and the Target Architecture. However, simply identifying gaps does not complete the process.

The association of gaps with work packages happens later in the cycle:

Phase E: Opportunities and Solutions is where the identified gaps are analyzed and translated into work packages, projects, or initiatives that will deliver the required changes.

In Phase E, architects also determine whether Transition Architectures are needed, and they generate the initial Architecture Roadmap.

This is the phase where gaps become actionable, linked with specific work packages that can be executed to close them.

Phase F (Migration Planning) takes this further by finalizing the roadmap and building the detailed Implementation and Migration Plan, but the initial association of gaps with work packages occurs in Phase E.

The Request for Architecture Work is a deliverable that is sent from the sponsor and triggers the start of an architecture development cycle. It defines the scope, budget, schedule, and deliverables for a specific architecture project. The Statement of Architecture Work is a deliverable that is produced by the architect and defines the approach and resources needed to complete an architecture project. It forms the basis of a contractual agreement between the sponsor and the architecture organization. The Architecture Principles are a deliverable that is produced by the architect and defines the general rules and guidelines for the architecture work. They reflect the business principles, business goals, and business drivers of the organization. The Architecture Requirements Specification is a deliverable that is produced by the architect and defines the requirements that govern the architecture work. It covers both functional and non-functional requirements as well as constraints and assumptions. 

The chart shown is a Gantt chart, which is commonly used for project management to illustrate a project schedule. In the context of TOGAF (The Open Group Architecture Framework), which is a framework for enterprise architecture, this Gantt chart is demonstrating the sequenced approach to the Architecture Development Method (ADM). The ADM is the core process of TOGAF which provides a tested and repeatable process for developing architectures. The ADM is described as being iterative, over the whole process, between phases, and within phases. For each iteration of the ADM, a fresh decision must be taken about each of the parameters (scope, granularity, time period, and architecture assets).

The ADM consists of a number of phases that have to be followed in sequence:

Preliminary Phase: Framework and principles

Phase A: Architecture Vision

Phase B: Business Architecture

Phase C: Information Systems Architectures, including Data and Application Architectures

Phase D: Technology Architecture

Phase E: Opportunities and Solutions

Phase F: Migration Planning

Phase G: Implementation Governance

Phase H: Architecture Change Management

Requirements Management

Each phase is dependent on the outputs of the previous phase and the Requirements Management phase runs throughout. The Gantt chart clearly shows the dependency and sequence in which these phases occur, implying that a structured approach is followed to produce the enterprise architecture.

The TOGAF Standard, Version 9.2, a standard of The Open Group

The TOGAF documentation available at and

The objectives listed in the question correspond to the objectives of different phases of the TOGAF ADM (Architecture Development Method), which is a method for developing and managing an enterprise architecture1.

The ADM consists of nine phases, each with a specific purpose and output. The phases are1:

Preliminary Phase: To prepare and initiate the architecture development cycle, including defining the architecture framework, principles, and governance.

Phase A: Architecture Vision: To define the scope, vision, and stakeholders of the architecture initiative, and to obtain approval to proceed.

Phase B: Business Architecture: To describe the baseline and target business architecture, and to identify the gaps between them.

Phase C: Information Systems Architectures: To describe the baseline and target data and application architectures, and to identify the gaps between them.

Phase D: Technology Architecture: To describe the baseline and target technology architecture, and to identify the gaps between them.

Phase E: Opportunities and Solutions: To identify and evaluate the opportunities and solutions for implementing the target architecture, and to define the work packages and transition architectures.

Phase F: Migration Planning: To finalize the implementation and migration plan, and to ensure alignment with the enterprise portfolio and project management.

Phase G: Implementation Governance: To provide architecture oversight and guidance for the implementation projects, and to manage any architecture change requests.

Phase H: Architecture Change Management: To monitor the changes in the business and technology environment, and to assess the impact and performance of the architecture.

Based on the above definitions, we can match each objective with the corresponding phase as follows:

Objective 1: Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision. This objective is achieved in Phase C: Information Systems Architectures, where the data architecture is defined as a subset of the information systems architecture2.

Objective 2: Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals. This objective is achieved in Phase B: Business Architecture, where the business architecture is defined as a subset of the enterprise architecture3.

Objective 3: Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture. This objective is achieved in Phase A: Architecture Vision, where the architecture vision is defined as a high-level description of the target architecture and its benefits4.

Objective 4: Develop the Target Application Architecture that enables the Business Architecture and the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns. This objective is achieved in Phase C: Information Systems Architectures, where the application architecture is defined as a subset of the information systems architecture2.

1: The TOGAF Standard, Version 9.2, Chapter 5: Architecture Development Method (ADM)

2: The TOGAF Standard, Version 9.2, Chapter 9: Phase C: Information Systems Architectures

3: The TOGAF Standard, Version 9.2, Chapter 8: Phase B: Business Architecture

4: The TOGAF Standard, Version 9.2, Chapter 7: Phase A: Architecture Vision

Comprehensive and Detailed Explanation

Architecture Partitioning is an ADM technique in TOGAF that addresses how large and complex architectures can be broken down into manageable parts. The intent is to make architecture development more effective, especially in large enterprises with multiple teams, stakeholders, and domains.

Key points from TOGAF:

TOGAF does not mandate a partitioning model. It provides guidelines and techniques to help architects determine whether and how to partition. This means statement 1 is incorrect.

Statement 2: Correct. Architectures may be partitioned to allow different teams to work on different elements in parallel (e.g., by domain, line of business, geographic scope). Partitioning provides clear ownership and reduces overlap or conflict.

Statement 3: Correct. Partitions can be structured in a way that supports architecture re-use, since well-defined partitions (e.g., capability-based or domain-based) enable consistent re-use of architecture building blocks across projects.

Correct Mapping

Statement 1: Incorrect (partitioning is not required by ADM).

Statement 2: Correct.

Statement 3: Correct.

Correct answer is D (2 and 3).

Why the other options are incorrect

A (1, 2 and 3): Incorrect because TOGAF does not require partitioning.

B (1 and 3): Incorrect because 1 is not correct.

C (1 and 2): Incorrect because 1 is not correct.

References

The Open Group, TOGAF® Standard, Version 9.2, Part III: ADM Guidelines & Techniques — Architecture Partitioning.

The Open Group, TOGAF® 9 Certified Study Guide — coverage of partitioning and its uses in large-scale architecture development.

The Enterprise Continuum provides a classification mechanism for artifacts, showing how they evolve from generic Foundation Architectures and Reference Models to organization-specific architectures.

Option A is about tools, not the Continuum.

Option B describes the Architecture Principles.

Option C describes the Architecture Repository.

The Architecture Landscape is a class of information within the Architecture Repository that shows an architectural view of the building blocks that are in use within the organization today (the Baseline Architecture), as well as those that are planned for the future (the Target Architecture). The Architecture Landscape typically contains a list of the applications in use within the enterprise, along with their relationships and dependencies, as well as other relevant architectural information. The Architecture Landscape helps to identify opportunities for re-use, consolidation, or retirement of existing applications, as well as gaps or overlaps in the current or future architecture.

The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 34: Architecture Landscape : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 47: Architecture Repository

 In the ADM documents which are under development and have not undergone any formal review and approval process are called “draft”. This indicates that they are subject to change and refinement as the architecture development progresses. Reference: The TOGAF® Standard | The Open Group Website, Section 4.2.5 Architecture Deliverables.

“A business scenario is essentially a complete description of a business problem, both in business and in architectural terms.”

The following activities are part of Risk Management:

Initial risk assessment

Risk mitigation and residual risk assessment

Risk monitoring

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.

According to the TOGAF Standard, an architecture view is a representation of a system from the perspective of a related set of concerns1. An architecture viewpoint is a specification of the conventions for a particular kind of architecture view1. Presenting different architecture views and architecture viewpoints to stakeholders helps architects to extract hidden agendas, principles, and requirements that could impact the final target architecture. This is because different stakeholders may have different concerns and interests in the system, and by showing them how the system addresses their concerns from different perspectives, the architects can elicit more feedback and validation from them2. For example, a business stakeholder may be interested in the business architecture view, which focuses on the business processes, functions, and capabilities of the system3. A security stakeholder may be interested in the enterprise security view, which addresses the security aspects of the system, such as confidentiality, integrity, and availability3. By presenting these views to the respective stakeholders, the architects can ensure that the system meets their expectations and needs, and also identify any potential issues or gaps that may affect the target architecture. References: 1: The TOGAF Standard, Version 9.2 - Architectural Artifacts - The Open Group1; 2: Understanding TOGAF Views and Viewpoints in Enterprise Architecture2; 3: Developing Architecture Views - The Open Group4

When considering agile development, Architecture to Support Project 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. A backlog is a list of features or tasks that need to be done to deliver a product or service. It is prioritized by the product owner based on the value and urgency of each item. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.5 Architecture to Support Project.

The Architecture Landscape is divided into levels known as Segment Strategic and Capability Architectures. These levels correspond to different scopes and purposes of architectures within an enterprise. Segment Architectures are architectures that address specific business units, functions, or processes within an enterprise. Strategic Architectures are architectures that provide a high-level view of the enterprise’s vision, goals, and direction. Capability Architectures are architectures that address specific business capabilities or services that span multiple segments or domains. Reference: The TOGAF® Standard | The Open Group Website, Section 2.4 Architecture Repository.

Within the TOGAF framework, assessments are used to ensure that architecture work is conformant with governance parameters. A compliance assessment (sometimes called architecture compliance or compliance review) is the evaluation of a project’s architectural artifacts—its design, architecture decisions, progress status—against the established architecture standards, principles, and constraints. The content of a compliance assessment typically includes reviewing the project status, the architectural design alignment, and identifying non‑compliance issues or deviations. Because it focuses on how well the project matches the architecture, rather than on capabilities, organizational structure, or risk per se, the described contents correspond to a compliance assessment. The compliance assessment helps governance bodies enforce architectural consistency and correct deviations during implementation.

The purpose of the Preliminary Phase is to architect an Enterprise Architecture Capability that meets the needs and expectations of the enterprise’s stakeholders and supports and enables subsequent phases of architecture development and transition. This phase involves defining the scope, principles, framework, and governance for the Enterprise Architecture Capability. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2 Preliminary Phase.

(Authoritative Open Group guidance distinguishes conceptual, logical, and physical concerns; at the logical level, component types are identified independently of implementation.) For example, the Open Group’s metamodel guidance emphasizes technology-agnostic structure to ensure consistency within an architecture description, which is precisely what the logical level captures before physical realization.

“The Content Metamodel defines a formal structure… to ensure consistency within the architecture description and also to provide guidance for organizations that wish to implement their architecture within an architecture tool.” Open Group Publications

Comprehensive and Detailed Explanation

Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders

This is the objective of Phase F: Migration Planning, where the Implementation and Migration Plan is developed, addressing costs, business value, and stakeholder concerns.

Ensure conformance with the Target Architecture by implementation projects

This is the focus of Phase G: Implementation Governance, which oversees implementation projects, ensuring they align with and conform to the Target Architecture through architecture contracts.

Ensure that the architecture development cycle is maintained

This belongs to Phase H: Architecture Change Management, which ensures the architecture remains relevant, and that the ADM cycle continues in response to new requirements and changes.

Ensure that the Architecture Governance Framework is executed

Also part of Phase H: Architecture Change Management, where governance is continuously applied to manage change effectively.

Correct Mapping

1 → F

2 → G

3 → H

4 → H

Which corresponds to Option A (1F – 2G – 3H – 4H).

Why the other options are incorrect

B. (1H – 2F – 3F – 4G): Incorrect assignment of phases; for example, conformance is not part of Phase F.

C. (1G – 2H – 3H – 4F): Misplaces objectives; conformance is not Phase H, and governance execution is not Phase F.

D. (1F – 2G – 3G – 4H): Incorrect because maintaining the ADM cycle (3) is not Phase G, but Phase H.

References

The Open Group, TOGAF® Standard, Version 9.2, Part II: ADM — Phase F: Migration Planning, Phase G: Implementation Governance, Phase H: Architecture Change Management.

The Open Group, TOGAF® 9 Certified Study Guide — outlines ADM phase objectives and their scope.

The Implementation Governance Model is a framework that defines the roles, responsibilities, processes, and standards for governing the implementation of the target architecture. It ensures that a project transitioning into implementation also smoothly transitions into appropriate Architecture Governance, which is the practice of ensuring compliance with the enterprise architecture and its principles, standards, and goals. The Implementation Governance Model is part of the Implementation and Migration Plan, which is the output of Phase F: Migration Planning of the Architecture Development Method (ADM)12 References: 1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 21: Phase F: Migration Planning 2: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance

The TOGAF Content Framework exists to give a detailed model of architectural work products—including deliverables, the artifacts within them, and the architectural building blocks those artifacts represent. The fundamental intent of embedding a Content Framework in TOGAF is to drive greater consistency in the outputs produced when following the Architecture Development Method (ADM). That means regardless of who is doing the architecture work, or in which phase of ADM, the types of outputs, their structure, classification (deliverable → artifact → building block), naming, and relationships remain consistent across the organisation. This structured model ensures that architecture work is systematic, standardised, and comparable across different projects or cycles. It is not primarily a mechanism for storage (that’s the role of the repository), nor is it only about addressing IT concerns or preventing gaps — its primary purpose is standardising architecture outputs to support clear communication, reuse, and governance across the enterprise

The Enterprise Continuum provides methods for classifying architecture artifacts as they evolve from generic architectures to Organization-Specific Architectures. Generic architectures are architectures that have been developed for use across a wide range of enterprises with similar characteristics. They provide common models, functions, and services that can be reused and adapted for specific purposes. Organization-Specific Architectures are architectures that have been tailored to meet the needs and requirements of a particular enterprise or a major organizational unit within an enterprise. They reflect the unique vision, goals, culture, structure, processes, systems, and technologies of that enterprise or unit. Reference: The TOGAF® Standard | The Open Group Website, Section 2.3 Enterprise Continuum.

Phase A: Architecture Vision is the first phase of the Architecture Development Method (ADM) cycle, which is the core of the TOGAF standard. The main purpose of this phase is to define the scope and approach of the architecture development, and to create the Architecture Vision, which is a high-level description of the desired outcomes and benefits of the proposed architecture. To achieve this purpose, this phase focuses on defining the problem to be solved, identifying the stakeholders, their concerns, and requirements, and establishing the business goals and drivers that motivate the architecture work. This phase also involves obtaining the approval and commitment of the sponsors and other key stakeholders, and initiating the Architecture Governance process.

The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 5: Introduction to the ADM : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18.3: Inputs : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18.4: Steps

The planning horizon, depth, and breadth of an Architecture Project, along with the contents of the EA Repository, are typically framed by Strategy, Portfolio, Segment, and End-to-end Target Architecture. The 'Segment' refers to a part of the organization, typically addressed in a Segment Architecture, while 'End-to-end Target Architecture' encompasses the complete view of the planned architecture across the entire organization.

When scoping an architecture in TOGAF, three key axes (dimensions) are used to frame the extent of the architecture work. The first is time period (how far into the future or over what timeframe to plan). The second is depth—how detailed or granular the architecture models will be (e.g., high level, mid level, very detailed). The third is breadth, which refers to which parts (domains, business units, functions) of the enterprise will be included, and which architecture domains (business, data, application, technology) will be in scope. This triple‐dimension model helps architects, stakeholders, and governance bodies understand how wide, deep, and forward‑looking the architecture effort will be. Thus “breadth, architecture domains” is the correct third dimension.

Gap Analysis in TOGAF is a technique used to compare the baseline architecture (current state) with the target architecture (future desired state). The output is a set of gaps, representing what is missing or what must change to move from baseline to target. These gaps help validate that the target architecture is adequate: by identifying what is not addressed, architects can ensure that all required functionality, constraints, and transformation paths are captured. In effect, Gap Analysis validates the architecture by exposing omissions, inconsistencies, or unmet requirements between what is and what should be. It is not primarily about defining service levels, non‑functional requirements, or quality metrics (though it helps inform those). Rather, its main role is in validating and guiding closure of architectural gaps.

Gap Analysis is a technique that compares the Baseline Architecture and the Target Architecture to identify the differences and gaps between them. The purpose of this technique is to determine the changes and additions that are required to achieve the desired future state of the architecture. One of the main aspects of Gap Analysis is to identify the functions that are missing or overlapping in the current and future architectures, and to plan how to address them. This helps to ensure that the architecture is complete, consistent, and aligned with the business objectives and requirements3

Business principles business goals, and business drivers provide context for architecture work, by describing the needs and ways of working employed by the enterprise. They define what the enterprise wants to achieve, how it wants to operate, and what factors influence its decisions and actions. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2 Preliminary Phase.

Comprehensive and Detailed Explanation

When defining the scope of an architecture, TOGAF identifies four dimensions that need to be considered:

Breadth – 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 – 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 – This defines the planning horizon of the architecture. It could be short-term (tactical), medium-term, or long-term (strategic).

Architecture Domains – 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) – 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.

References

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

According to the TOGAF Standard, an architecture view is a representation of a system from the perspective of a related set of concerns1. An architecture viewpoint is a specification of the conventions for a particular kind of architecture view1. Presenting different architecture views and architecture viewpoints to stakeholders helps architects to extract hidden agendas, principles, and requirements that could impact the final target architecture. This is because different stakeholders may have different concerns and interests in the system, and by showing them how the system addresses their concerns from different perspectives, the architects can elicit more feedback and validation from them2. For example, a business stakeholder may be interested in the business architecture view, which focuses on the business processes, functions, and capabilities of the system3. A security stakeholder may be interested in the enterprise security view, which addresses the security aspects of the system, such as confidentiality, integrity, and availability3. By presenting these views to the respective stakeholders, the architects can ensure that the system meets their expectations and needs, and also identify any potential issues or gaps that may affect the target architecture. References: 1: The TOGAF Standard, Version 9.2 - Architectural Artifacts - The Open Group1; 2: Understanding TOGAF Views and Viewpoints in Enterprise Architecture2; 3: Developing Architecture Views - The Open Group4

Architecture governance is the practice of ensuring compliance with the enterprise architecture and its principles, standards, and goals. Architecture governance provides the means to establish, monitor, and control the architecture development and implementation processes, and to resolve any issues or conflicts that may arise. Architecture governance also ensures that all stakeholders are represented and involved in the decision-making process, and that their interests and concerns are balanced and aligned. Statements 1 and 2 highlight the value and necessity for architecture governance to be adopted within organizations, as they emphasize the importance of responsibility, accountability, fairness, and transparency in the architectural activities. Statements 3 and 4 are more related to the benefits and outcomes of having a good enterprise architecture, rather than the governance aspect.

The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 29: Architecture Governance

Comprehensive and Detailed Explanation

The TOGAF ADM defines distinct objectives for Phase E (Opportunities and Solutions) and Phase F (Migration Planning).

Phase E: Opportunities and Solutions

Focuses on generating the initial Architecture Roadmap.

Identifies major work packages, Transition Architectures, and projects.

Determines if an incremental approach is needed, and defines Transition Architectures to ensure delivery of continuous business value.

Therefore:

Statement 1 (incremental approach and Transition Architectures) belongs to Phase E.

Statement 2 (initial Architecture Roadmap based on gap analysis) also belongs to Phase E.

Phase F: Migration Planning

Finalizes the Architecture Roadmap.

Develops the detailed Implementation and Migration Plan.

Ensures stakeholders understand the business value and cost of work packages and Transition Architectures.

Therefore:

Statement 3 (finalizing the Roadmap and Plan) belongs to Phase F.

Statement 4 (ensuring value and cost are understood by stakeholders) belongs to Phase F.

Correct Mapping

Phase E Objectives = Statements 1 and 2

Phase F Objectives = Statements 3 and 4

Thus the correct answer is A (1 & 2).

References

The Open Group, TOGAF® Standard, Version 9.2, Part II: ADM — Phase E: Opportunities and Solutions (objectives include generating the initial Architecture Roadmap, identifying major work packages, determining incremental approach and Transition Architectures).

Phase F: Migration Planning (objectives include finalizing the Architecture Roadmap and Implementation & Migration Plan, and confirming business value and costs with stakeholders).

The Open Group, TOGAF® 9 Certified Study Guide — comparison of Phase E vs. Phase F objectives.

===========