OGEA-103 The Open Group TOGAF Enterprise Architecture Combined Part 1 and Part 2 Exam Free Practice Exam Questions (2026 Updated)

In TOGAF, creating a Business Scenario is a foundational step in defining and understanding the business problem, especially for complex transformations involving multiple stakeholders andsystems, such as in this scenario. This method aligns with Phase A (Architecture Vision) of the TOGAF Architecture Development Method (ADM). Here’s why this approach is the most effective:

Understanding Business Requirements:A Business Scenario provides a structured way to capture and analyze the business requirements, stakeholder concerns, and the contextual elements related to the problem. In this scenario, the company faces challenges in integrating newly acquired companies with existing operations, which includes complex stakeholder concerns across different functional areas. Developing a Business Scenario allows the EA team to break down these complexities into identifiable and manageable parts.

Risk Evaluation and Management:By using the Business Scenario approach, the EA team can not only define the requirements but also assess associated risks systematically. TOGAF emphasizes the importance of risk management through identifying potential risks, evaluating their impact, and defining strategies for handling these risks. The process includes assessing how risks can be avoided, transferred, or reduced—a necessary step in large-scale transformations to ensure that risks are proactively managed.

Residual Risks and Governance:Any risks that cannot be fully resolved should be identified as residual risks and escalated to the Architecture Board, which is aligned with TOGAF’s governance approach. The Architecture Board’s role in TOGAF is to provide oversight and make critical decisions on risks that exceed the control of the EA team. This ensures that unresolved risks are managed at the appropriate level of the organization.

Alignment with TOGAF ADM Phases:The Business Scenario approach directly aligns with the Preliminary and Architecture Vision phases of the TOGAF ADM, which focuses on establishing a baseline understanding of the business context and the strategic transformation required. The detailed understanding of requirements, stakeholder concerns, and risks identified here will guide the subsequent phases of the ADM, including Business Architecture and Information Systems Architecture.

TOGAF Reference (Section 2.6, ADM Techniques):TOGAF provides guidelines on the creation of Business Scenarios as part of ADM Techniques, highlighting the importance of defining a business problem comprehensively to ensure successful transformation. This method includes identification of stakeholders, business requirements, and associated risks, which aligns well with the company ' s need for strategic and systematic integration of new business units.

By utilizing a Business Scenario, the EA team ensures that all aspects of the transformation are well understood, risks are identified early, and residual risks are managed effectively, aligning with the company ' s strategic objectives and the TOGAF framework’s guidance on risk management and stakeholder alignment.

A Request for Architecture Work is a document that describes the scope, approach, and expected outcomes of an architecture project. A Request for Architecture Work is usually initiated by the sponsor or client of the architecture work, and approved by the Architecture Board, which is a governance body that oversees the architecture work and ensures compliance with the architecture principles, standards, and goals. A Request for Architecture Work triggers a new cycle of the Architecture Development Method (ADM), which is the core process of the TOGAF standard that guides the development and management of the enterprise architecture12

An Architecture Vision is a high-level description of the desired outcomes and benefits of the proposed architecture. An Architecture Vision is the output of Phase A: Architecture Vision of the ADM cycle, which is the first phase of the architecture development. An Architecture Vision defines the scope and approach of the architecture work, and establishes the business goals and drivers that motivate the architecture work. An Architecture Vision also involves obtaining the approval and commitment of the sponsors and other key stakeholders, and initiating the Architecture Governance process3

A trade-off analysis is a technique that can be used to evaluate and compare different architecture alternatives and select the most suitable one. A trade-off analysis involves identifying the criteria and factors that are relevant to the decision, such as costs, benefits, risks, and opportunities, and assessing the strengths and weaknesses of each alternative. A trade-off analysis also involves balancing and reconciling the multiple, often conflicting, requirements and concerns of the stakeholders, and ensuring alignment with the Architecture Vision and the Architecture Principles.

Therefore, the best answer is D, because it proposes the best approach for architecture development to realize the CEO’s change in direction for the company. The answer covers the Request for Architecture Work, the Architecture Vision, and the trade-off analysis techniques that are relevant to the scenario.

 1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 7: Request for Architecture Work 2: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance 3: 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 III: ADM Guidelines and Techniques, Chapter 30: Trade-Off Analysis

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. 

Comprehensive and Detailed Explanation From Exact Extract (150–250 words):

Option C is the best answer because it directly aligns with the most critical concerns expressed in the scenario and maps precisely to the example Architecture Principles defined in the TOGAF standard.

The principle Common Vocabulary and Data Definitions is essential in a healthcare environment where standardized medical coding, shared electronic health records, and cross-provider data exchange are core operational requirements. Without consistent data definitions, AI-based solutions would misinterpret clinical information, leading to unsafe or incorrect outcomes.

Data Security is one of the most fundamental principles in regulated industries such as healthcare. The scenario explicitly highlights privacy, prevention of data breaches, system availability, and protection of life-critical systems. This principle ensures confidentiality, integrity, and availability of patient data, all of which are non-negotiable constraints for architecture work in this context.

Requirements-Based Change ensures that architectural decisions are driven by clearly defined business and clinical requirements rather than technology trends alone. This is particularly important for AI initiatives, where stakeholder concerns emphasize patient outcomes, life-critical timing, and minimal disruption. This principle ensures that AI adoption is justified, traceable, and aligned with healthcare priorities.

The other options either focus too broadly on governance, enterprise-wide benefit, or general accessibility, and do not sufficiently address the clinical safety, data integrity, and requirements-driven nature of the project. Therefore, Option C best reflects TOGAF guidance for this scenario.

Item A is an Architecture Viewpoint . In TOGAF, an Architecture Viewpoint defines the conventions for constructing, interpreting, and using an Architecture View. It frames stakeholder concerns and governs the related views and model kinds used to express the architecture.

Item B is an Architecture View . An Architecture View represents a system from the perspective of a related set of concerns. It is created according to an Architecture Viewpoint and is used to communicate architecture information to specific stakeholders.

The diagram shows that concerns are framed by item A, and item A governs item B. It also shows that item B is connected to Architecture Models, which supports the interpretation that B is the Architecture View. This matches the standard TOGAF concept structure: stakeholders have concerns, concerns are framed by viewpoints, viewpoints govern views, and views are made up of architecture models.

Therefore, item A is the Architecture Viewpoint, and item B is the Architecture View. The correct answer is B .

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

Comprehensive and Detailed Explanation

In the TOGAF ADM, deliverables go through a lifecycle of development, review, approval, and usage. TOGAF distinguishes between draft deliverables (work-in-progress) and final deliverables (those that have been formally reviewed and signed off).

Draft deliverables are produced as working versions of the required outputs in each ADM phase. These may carry version labels such as 0.1, 0.5, 0.9, etc., and are subject to stakeholder review and refinement.

Once the document has been reviewed and approved by the relevant stakeholders (e.g., Architecture Board, governance bodies), it becomes a final deliverable.

Final deliverables are baseline-controlled items and are formally stored in the Architecture Repository as an approved architecture artifact.

Thus, the correct term for a deliverable that has completed review and is approved is “final”.

Why the other options are incorrect

B. Approved: While true in general language, TOGAF uses the formal term “final deliverable”, not “approved deliverable.”

C. Ratified: This term is not used in TOGAF to describe the state of a deliverable.

D. Version 0.9: This is a draft numbering convention, not the status of an approved deliverable.

References

The Open Group, TOGAF® Standard, Version 9.2, Part II: ADM — description of deliverables, artifacts, and building blocks.

The Open Group, TOGAF® 9 Certified Study Guide — explanation of draft vs. final deliverables in the ADM lifecycle.

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 https://publications.opengroup.org/standards/architecture and https://publications.opengroup.org/guides/architecture

Comprehensive and Detailed Explanation From Exact Extract (150–250 words):

The graphic illustrates the Architecture Trade-off method , one of the ADM Guidelines and Techniques defined in the TOGAF Standard. The purpose of this method is to evaluate multiple candidate architecture alternatives against a defined set of criteria that are derived from the Architecture Vision , Architecture Principles , and Architecture Requirements . Rather than selecting a solution immediately, architects compare the alternatives, assess their strengths and weaknesses, and identify the option that provides the best overall balance between business value, cost, risk, complexity, stakeholder concerns, and architectural compliance.

The diagram exactly reflects the TOGAF trade-off process. Vision, Principles, and Requirements provide the evaluation context. Multiple alternatives are then assessed using defined criteria before a single preferred alternative is selected. This structured decision-making process helps architects justify architectural decisions and resolve conflicting stakeholder concerns through objective comparison rather than subjective preference.

The other options do not match the diagram. Iteration refers to repeating ADM activities. The Business Scenario method is used to discover and validate business requirements. Architecture Partitioning is used to divide Enterprise Architecture into manageable sections for ownership and governance. None of these techniques involve evaluating competing architecture alternatives against selection criteria.

Therefore, according to the TOGAF Standard, the correct answer is D. The Architecture Trade-off method .

 In Phase E of the ADM cycle, building block gaps become associated with work packages that will address the gaps. This phase involves creating an Implementation and Migration Plan that defines a set of work packages and Transition Architectures that will deliver the Target Architecture. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.5 Phase E: OpportunitiesandSolutions.

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.

According to the TOGAF Standard, 10th Edition, a transformation readiness assessment is a technique that evaluates the preparedness of the organization to undergo a change, and identifies the actions needed to increase the likelihood of a successful outcome. A transformation readiness assessment can be conducted in Phase E: Opportunities and Solutions, and the actions resulting from it can be dealt with in Phase F: Migration Planning 1. In Phase E, the transformation readiness assessment can help to identify the major implementation challenges and risks, and to define the critical success factors and key performance indicators for the architecture project. In Phase F, the actions resulting from the transformation readiness assessment can help to develop a detailed and realistic migration plan, and to address the gaps, issues, and dependencies that may affect the transition to the target architecture 1. References: 1: TOGAF Standard, 10th Edition, Part III: ADM Guidelines and Techniques, Chapter 29: Business Transformation Readiness Assessment.

The Architecture Repository is the structural framework defined by TOGAF to store, manage, and leverage architecture artifacts, including reference models, standards, governance logs, and deliverables.

The Architecture Capability refers to governance and processes.

The Architecture Landscape shows Strategic, Segment, and Capability architectures, not storage.

The Enterprise Architecture Capability Model is not a defined TOGAF concept.

•Phase A: Architecture Vision

oDevelop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture

oDefine the scope and boundaries of the architecture engagement

oIdentify the key stakeholders and their concerns and expectations

oDefine the Architecture Vision statement and the Architecture Definition Document

oObtain approval and commitment from the sponsors and stakeholders

•Phase B: Business Architecture

oDevelop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals

oDefine the Baseline Business Architecture, if not available

oPerform a gap analysis between the Baseline and Target Business Architectures

oDefine candidate roadmap components for the Business Architecture

oResolve impacts across the Architecture Landscape

•Phase C: Information Systems Architecture

oDevelop the Target Data Architecture that enables the Business Architecture and the Architecture Vision

oDevelop the Target Application Architecture that supports the Business Architecture and the Architecture Vision

oDefine the Baseline Data and Application Architectures, if not available

oPerform a gap analysis between the Baseline and Target Data and Application Architectures

oDefine candidate roadmap components for the Information Systems Architecture

oResolve impacts across the Architecture Landscape

•Phase D: Technology Architecture

oDevelop the Target Technology Architecture that enables the Information Systems Architecture and the Architecture Vision

oDefine the Baseline Technology Architecture, if not available

oPerform a gap analysis between the Baseline and Target Technology Architectures

oIdentify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures

oResolve impacts across the Architecture Landscape

Therefore, the correct matching of the objectives and the phases is:

•1C: Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision

•2B: Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals

•3A: Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture

•4D: Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures

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.

The Architecture Development Method (ADM) is the core of the TOGAF Standard. It provides a repeatable, iterative, and adaptable process for developing, maintaining, governing, and managing Enterprise Architectures. The ADM consists of a series of phases beginning with the Preliminary Phase and continuing through Architecture Vision, Business Architecture, Information Systems Architectures, Technology Architecture, Opportunities and Solutions, Migration Planning, Implementation Governance, and Architecture Change Management.

The ADM is intended to be tailored to the needs of individual enterprises while maintaining a consistent architecture development approach. It supports continuous architecture evolution through iteration, stakeholder engagement, requirements management, governance, and change management.

Option A describes the Enterprise Continuum. Option B refers only to the Requirements Management function, which supports the ADM but does not define it. Option C describes one of several TOGAF techniques rather than the ADM itself.

Therefore, the best description of the TOGAF ADM is a repeatable process for developing architectures , making Option D correct.

===========

Comprehensive and Detailed Explanation From documents:

The Architecture Repository in TOGAF provides a structured model for storing architectural output. It contains six classes of architectural information:

Architecture Metamodel – defines the structure of architectural content and relationships.

Architecture Capability – contains parameters, structures, and processes supporting the governance of the repository and the Architecture Board.

Architecture Landscape – architectural views at different levels (Strategic, Segment, Capability).

Standards Information Base (SIB) – standards to guide architecture development and solution building.

Reference Library – reference materials such as patterns, templates, guidelines.

Governance Log – record of governance activity, compliance assessments, waivers, and approvals.

Focusing on Architecture Capability:

Defined by TOGAF as: “The parameters, structures, and processes that support governance of the Architecture Repository.”

It provides the framework for ensuring that the repository is managed, controlled, and aligned with the enterprise’s architecture governance practices.

It includes organizational roles, responsibilities, and processes that ensure architecture practices are sustainable and repeatable.

Why the other options are incorrect:

B. This describes the Architecture Metamodel, not Architecture Capability.

C. This describes the Governance Log, which holds the record of governance activity.

D. This describes the Reference Library, which contains patterns, templates, and guidelines.

References (official TOGAF materials, no links):

The Open Group, TOGAF® Standard, Version 9.2, Part V: Enterprise Continuum and Tools — Architecture Repository.

The Open Group, TOGAF® 9 Certified Study Guide — detailed breakdown of the six classes in the Architecture Repository and their purpose.

EA applies architecture principles and practices to analyze, design, plan, and implement enterprise analysis that supports digital transformation, IT growth, and the modernization of IT2. EA also helps organizations improve the efficiency, timeliness, and reliability of business information, as well as the alignment, agility, and adaptability of the architecture to the changing needs and requirements3. Therefore, the best summary of the purpose of EA is to guide effective change.

The Preliminary Phase is the preparatory phase of the Architecture Development Method (ADM) cycle, which sets the context and direction for the architecture work. One of the objectives of this phase is to select and implement tools to support the Architecture Capability, which is the ability of an organization to perform enterprise architecture effectively and efficiently. Tools can include software applications, methods, techniques, standards, and frameworks that assist the architecture development and governance processes. The selection and implementation of tools should be based on the requirements and constraints of the organization, and the alignment with the Architecture Principles and the Architecture Vision3 References: 3: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 6: Preliminary Phase : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 45: Establishing and Maintaining an Enterprise Architecture Capability : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 46: Tools for Architecture Development