Free The Open Group OGEA-103 Exam Dumps May 2026

The four dimensions used to scope an architecture are Breadth, Depth, Time Period, and Architecture Domains1, p. 8.

Breadth refers to the extent of the enterprise covered by the architecture, which can range from a specific business unit to the entire organization1, p. 8.

Depth refers to the level of detail and completeness of the architecture, which can vary depending on the purpose, scope, and stakeholders of the architecture1, p. 8.

Time Period refers to the temporal aspects of the architecture, such as the current state, the target state, and the transition plan1, p. 8.

Architecture Domains refers to the classification of the architecture into four domains: Business, Data, Application, and Technology1, p. 8.

These four dimensions help define the scope and boundaries of the architecture and ensure that it meets the needs and expectations of the stakeholders.

1: The Open Group (2018). The TOGAF Standard, Version 9.2.1

The Chief Engineer is concerned that implementation across multiple plants and mixed teams (internal + contractors) may be inconsistent and of poor quality.

The question asks: How should Architecture Contracts be used to address this concern according to the TOGAF standard?

TOGAF states that an Architecture Contract must:

Define obligations of both architecture and implementation organizations

Specify metrics, measures, acceptance criteria, and success factors

Identify risks and mitigation

Support Architecture Governance through compliance reviews

Apply to BOTH internal teams and external suppliers (external contracts must be legally enforceable)

Option C is the only one that correctly reflects these TOGAF requirements.

Why Option C is correct

1. Architecture Contracts must specify goals, measures, acceptance terms, and risks

TOGAF explicitly states that Architecture Contracts should include:

Statement of Architecture Work

Performance metrics and measures

Acceptance criteria

Risks and issues

Compliance and conformance requirements

Option C includes all of these.

2. Third-party contracts must be legally enforceable

True --- TOGAF states that when external suppliers are involved, Architecture Contracts often take the form of legally binding contracts.

Option C:

''Third-party contracts must be legally enforceable.''

Correct.

3. Compliance reviews must be scheduled

TOGAF's Architecture Governance Framework prescribes scheduled Architecture Compliance Reviews to ensure that implementation conforms to the Architecture Contract.

Option C:

''establish a schedule of compliance reviews at key points''

Correct --- this directly addresses the Chief Engineer's concern about consistency and quality.

4. Deviations must be reviewed by the Architecture Board and any dispensations should be time-bound

TOGAF allows dispensations but requires:

Formal review

Approval by the Architecture Board

Time-bound accommodations rather than permanent exceptions

Option C includes exactly this guidance.

Comprehensive and Detailed In-Depth Explanation from Expert in Enterprise Architecture, guiding in TOGAF and ArchiMate:

In TOGAF, an Enterprise Architecture Capability represents the organizational ability to effectively perform architecture work on an ongoing basis. It encompasses people, processes, governance, tools, and skills required to create and use architecture to guide enterprise change.

This capability enables the enterprise to:

Develop architectures across domains and scopes

Apply architecture consistently to guide strategy and execution

Govern change through architecture principles, standards, and compliance

Sustain architecture practices over time

Why Option C is correct:

Option C accurately reflects TOGAF's definition: the ability to develop, use, and sustain architecture as a means of governing enterprise change.

Why the other options are incorrect:

A describes the Enterprise Continuum, not capability.

B describes Architecture Principles, not the overall capability.

D describes risk management, not architecture capability.

Authoritative TOGAF

TOGAF Architecture Capability Framework

TOGAF Enterprise Architecture Definition

TOGAF Architecture Governance

The phase of the ADM labeled as item 1 is Phase F: Migration Planning. This phase conducts implementation planning for the architecture defined in previous phases by creating an Architecture Roadmap and a detailed Implementation and Migration Plan. This phase also identifies and groups major work packages, transition architectures, projects, and dependencies. Reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap19.html

An Architecture Framework is used to structure architectural information in an orderly way so that it can be processed to meet stakeholder needs. An Architecture Framework provides a common language and taxonomy for describing architectures; a set of tools and techniques for creating architectures; a method for defining views and viewpoints for different stakeholders; a metamodel for representing architecture artifacts; a repository for storing and managing architecture artifacts; and a governance framework for controlling architecture development and evolution. Reference: The TOGAF Standard | The Open Group Website, Section 2 Core Concepts.

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.

1E: To identify delivery vehicles (projects programs portfolios) that will deliver the Target Architecture 2F: To confirm readiness and ability to undergo change 3E: To determine whether an incremental approach is required and if so identify Transition Architectures that will deliver continuous business value 4G: To perform appropriate governance functions while the solution is being implemented

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.