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

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.

In TOGAF, draft deliverables are those that are not yet finished or approved. They are work-in-progress versions that may have version numbers like 0.1, 0.5, or 0.9.

Once reviewed and approved, they become final deliverables.

Strategy Portfolio Project Solution Delivery are the four purposes that typically frame the planning horizon, depth and breadth of an Architecture Project, and the contents of the EA Repository. They correspond to different levels of abstraction and granularity in the architecture development process. Reference: The TOGAF® Standard, Version 9.2 - The Open Group, Section 2.4 Architecture Repository.

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, 10th Edition, an architecture contract is “a formal agreement between a service provider and a service consumer that defines the mutual commitments and expectations for the delivery of an architecture” 1. An architecture contract is a governed approach of a particular deliverable that will ensure adherence to the principles, standards, and requirements of the existing or developing architectures, as it specifies the roles, responsibilities, deliverables, quality criteria, and acceptance criteria for the architecture work 1. The other options are not correct, as they are not governed approaches of a particular deliverable, but rather different types of deliverables within the architecture development process. An architecture vision is “a high-level, aspirational view of the target architecture” 1. A statement of architecture work is “a document that defines the scope and approach that will be used to complete an architecture project” 1. An architecture definition document is “a document that describes the baseline and target architectures for one or more domains” 1. References: 1: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions.

Ensuring compliance with internal and external standards and regulatory obligations is one of the activities included as part of Architecture Governance. Architecture Governance is the practice and orientation by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level. It involves establishing processes, roles, responsibilities, policies, and standards to ensure that architectures are aligned with the enterprise’s strategy and objectives, and meet the quality and performance requirements. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.6 Architecture Governance.

Comprehensive and Detailed Explanation

TOGAF defines an Architecture Principle as a qualitative statement of intent that should be met by the architecture. To ensure clarity and consistent application, TOGAF provides a standard template for documenting each principle. The template includes four parts:

Name – A clear, precise, and easy-to-remember name for the principle.

Answers the question: What is this principle called?

Statement – A short, unambiguous sentence that communicates the essence of the principle.

Answers the question: What does this principle mean?

Rationale – Explains why the principle is important, the benefits of adopting it, and how it supports the enterprise’s goals.

Answers the question: Why should we adopt this principle?

Implications – Highlights the consequences of adopting the principle, including the impact on business processes, technology, governance, and resources.

Answers the question: How does this affect me?

Therefore, the correct section where the reader would find the answer to “How does this affect me?” is Implications.

Why the other options are incorrect

A. Statement: Defines the essence of the principle but does not address consequences.

B. Rationale: Explains the reasoning and justification for the principle but not its practical effects.

C. Name: Only provides the identifier or title of the principle.

References

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

The Open Group, TOGAF® 9 Certified Study Guide — description of the Architecture Principles template and the purpose of each section.

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

The Preliminary Phase is the phase in TOGAF where an organization establishes or enhances its Enterprise Architecture Capability. This includes defining governance structures, roles, responsibilities, processes, tools, and architectural principles. The objective is to prepare the organization to successfully execute the ADM.

Phase A focuses on Architecture Vision for a specific initiative, not on creating the overall EA capability. Phase G deals with implementation governance, and Phase H focuses on architecture change management. None of these phases are responsible for establishing the EA practice itself.

The Preliminary Phase answers foundational questions such as how architecture will be governed, who owns architecture decisions, how compliance will be enforced, and how architecture work will be integrated with other organizational processes. Therefore, creation of an Enterprise Architecture Capability clearly belongs to the Preliminary Phase.