OGEA-103 Exam Dumps - TOGAF Enterprise Architecture Combined Part 1 and Part 2 Exam

Phase A: Architecture Vision identifies stakeholders, their concerns, and defines the scope and objectives of the architecture engagement.

Defining enterprise strategy is outside ADM (it is a business planning activity).

Describing the target architecture happens in Phases B, C, and D.

Developing an EA Capability is done in the Preliminary Phase, not Phase A.

According to the TOGAF standard, the deliverables that match the descriptions are as follows:

1 Architecture Principles: These are general rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organization sets about fulfilling its mission1. They reflect a level of consensus among the various elements of the enterprise, and form the basis for making future IT decisions1.

2 Architecture Contracts: These are the joint agreements between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture2. They are used to ensure that the architecture is implemented and governed according to the agreed-upon specifications and standards2.

3 Request for Architecture Work: This is a document that is sent from the sponsoring organization to the architecture organization to trigger the start of an architecture development cycle3. It defines the scope, schedule, budget, deliverables, and stakeholders of the architecture project3.

4 Architecture Requirements Specification: This is a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture4. It defines the requirements for each architecture domain, as well as the relationships and dependencies among them4.

 1: Architecture Principles 2: Architecture Contracts 3: Request for Architecture Work 4: Architecture Requirements Specification

Business scenarios are a technique recommended by the TOGAF ADM for use in developing an Architecture Vision document12. Business scenarios are a means of capturing the business requirements and drivers, the processes and actors involved, and the desired outcomes and measures of success34. Business scenarios help to create a common vision and understanding among the stakeholders, and to identify and validate the architecture requirements . Business scenarios also provide a basis for analyzing the impact and value of the proposed architecture. References:

•The TOGAF Standard, Version 9.2 - Phase A: Architecture Vision - The Open Group

•TOGAF® Standard — Introduction - Phase A: Architecture Vision

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

•Business Scenarios - The Open Group

•[The TOGAF Standard, Version 9.2 - Architecture Requirements Specification - The Open Group]

•[The TOGAF Standard, Version 9.2 - Architecture Vision - The Open Group]

•[The TOGAF Standard, Version 9.2 - Business Transformation Readiness Assessment - The Open Group]

An Architecture Board is an executive-level group responsible for the review and maintenance of the strategic architecture and all of its sub-architectures1. It is a key element in a successful Architecture Governance strategy2.

An Architecture Board is typically made responsible, and accountable, for achieving some or all of the following goals2:

Providing the basis for all decision-making with regard to the architectures

Consistency between sub-architectures

Establishing targets for re-use of components

Flexibility of the Enterprise Architecture: To meet changing business needs To leverage new technologies

Enforcement of Architecture Compliance

Improving the maturity level of architecture discipline within the organization

Ensuring that the discipline of architecture-based development is adopted

Supporting a visible escalation capability for out-of-bounds decisions

Therefore, the correct answer is option D, which captures one of the goals of an Architecture Board as stated in the TOGAF Standard, Version 9.22.

Option A is incorrect, because conducting assessments of the maturity level of architecture discipline within the organization is not a direct responsibility of an Architecture Board, but rather a part of the Architecture Capability Framework3.

Option B is incorrect, because allocating resources for architecture projects is not a direct responsibility of an Architecture Board, but rather a part of the Architecture Governance Framework4.

Option C is incorrect, because creating the Statement of Architecture Work is not a direct responsibility of an Architecture Board, but rather a part of the Architecture Development Method5. References:

1: Architecture Board - The Open Group3

2: TOGAF Standard, Version 9.2 - Part VI: Architecture Governance Framework - Architecture Board

3: TOGAF Standard, Version 9.2 - Part VI: Architecture Governance Framework - Architecture Capability Framework

4: TOGAF Standard, Version 9.2 - Part VI: Architecture Governance Framework - Architecture Governance Framework

5: TOGAF Standard, Version 9.2 - Part II: Architecture Development Method - Phase A: Architecture Vision

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

A-Architecture Repository: This is a part of the Architecture Metamodel that contains artifacts structured according to the metamodel. It includes the Architecture Landscape which is adopted by the enterprise and governed by certain standards and practices.

B-Governing Board: The Governing Board ensures visibility and escalation, meaning it oversees and manages the capability of the architecture landscape. It plays a crucial role in governance.

C-Enterprise Capability: This refers to how well an enterprise can execute its mission, meet business objectives or satisfy its stakeholders’ needs and expectations. It’s influenced by both internal factors (like resources, processes) and external ones (like market trends).

TOGAF Version 9.1, Chapter 34: 1

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.

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.