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

This description matches Phase B: Business Architecture. In TOGAF, Phase B is the phase in which the architect develops the target Business Architecture and identifies the gaps between the baseline and target states. The phase is not limited to producing models only; it also ensures that the resulting domain architecture is reviewed and approved by stakeholders and that the implications of the gaps are understood. The wording in the question is characteristic of the domain architecture phases, and among the options provided, Phase B is the only domain architecture phase listed.

Phase A is concerned with developing the Architecture Vision, scope, constraints, and stakeholder consensus at a high level. The Preliminary Phase establishes the architecture capability and governance framework. Phase E is focused on Opportunities and Solutions, where solution building blocks, work packages, and transition approaches are identified. None of those primarily describe development of a domain architecture with stakeholder approval and identified gaps.

Because the question refers to a domain architecture, stakeholder approval, and a defined set of gaps to be addressed, the best answer is Phase B. It represents the ADM phase where the Business Architecture is formally developed and agreed.

===========

Gap analysis is a technique that is used to validate an architecture by highlighting the shortfall between the Baseline Architecture and the Target Architecture. One of the purposes of gap analysis is to identify missing functions that are either deliberately omitted, accidentally left out, or not yet defined in the Target Architecture. Missing functions are marked as gaps that need to be filled by developing or procuring the building blocks. 

“TOGAF defines **‘enterprise’ as any collection of organizations that has a common set of goals. For example, an enterprise could be a government agency, a whole corporation, a division of a corporation, a single department, or a chain of geographically distant organizations linked together by common ownership.” www.opengroup.org

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

This aligns with the TOGAF Architecture Repository model where:

A (Architecture Requirements Repository) contains requirements that drive architecture work.

B (Solutions Repository) stores the building blocks or solutions that support the architecture.

C (Architecture Landscape) represents the architecture assets that depict the current, transition, and target architecture states across the enterprise

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.

In TOGAF, the Standards Library is the part of the Architecture Repository that contains the standards, specifications, and reference materials with which architectures must comply. Its role is to provide the authoritative set of technical, operational, and architectural standards that guide architecture development and governance. Therefore, the correct answer is B.

Option A refers more closely to the Architecture Capability, where the organization’s framework, governance approach, structures, and methods are defined. Option C also belongs to the governance and capability side of the repository, not to the Standards Library itself. Option D is closer to what would be found in a Reference Library or reusable architecture support materials, such as guidelines, patterns, and templates, rather than the Standards Library.

The Standards Library is important because it provides the compliance basis for new architectures and implementation work. Architects use it to ensure that designs align with approved enterprise, industry, legal, and technical standards. This supports consistency, interoperability, governance, and reusability across architecture efforts. Since the question asks specifically what the Standards Library does within the Architecture Repository, the most accurate completion is that it lists the set of specifications to which architectures must comply. Hence, Option B is the correct answer.

An Enterprise Architecture Capability is the ability of the organization to perform effective and efficient architecture work, including the definition, governance, and management of its architectures2. The Preliminary Phase involves the following activities1:

•Reviewing the organizational context, scope, and drivers for conducting Enterprise Architecture

•Establishing the Architecture Capability desired by the organization, including the maturity level, roles, responsibilities, processes, and tools

•Defining and establishing the Organizational Model for Enterprise Architecture, which describes how the architecture function is organized and integrated within the enterprise

•Defining and establishing the Architecture Governance framework, which provides the mechanisms for ensuring the quality, consistency, and compliance of the architecture work

•Selecting and implementing the tools that support the Architecture Capability, such as repositories, modeling tools, and communication tools

•Defining the Architecture Principles that will guide and constrain the architecture work, based on the business principles, goals, and drivers of the organization

•Defining the Organization-Specific Architecture Framework, which is an adaptation of the generic TOGAF ADM to suit the specific requirements, standards, and practices of the organization

The Preliminary Phase is essential for preparing the organization for the successful development and implementation of its architectures, as well as for ensuring the alignment of the architecture work with the business strategy and objectives1.

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.