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

Gap Analysis in TOGAF is a technique used to compare the baseline architecture (current state) with the target architecture (future desired state). The output is a set of gaps, representing what is missing or what must change to move from baseline to target. These gaps help validate that the target architecture is adequate: by identifying what is not addressed, architects can ensure that all required functionality, constraints, and transformation paths are captured. In effect, Gap Analysis validates the architecture by exposing omissions, inconsistencies, or unmet requirements between what is and what should be. It is not primarily about defining service levels, nonfunctional requirements, or quality metrics (though it helps inform those). Rather, its main role is in validating and guiding closure of architectural gaps.

This statement best supports the need to govern Enterprise Architecture. Best practice governance enables the organization to control value realization by ensuring that architectures are aligned with the enterprise’s strategy and objectives, meet the quality and performance requirements, and deliver the expected benefits and outcomes. The Architecture Project does not mandate the governance of the target architecture, but rather follows the governance framework established by the enterprise. The TOGAF standard can be used without executive governance, but it is recommended that executive sponsorship and support are obtained for successful architecture development and transition. The Stakeholders preferences may go beyond the architecture project scope and need control, but this is not the primary reason for governing Enterprise Architecture. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.6 Architecture Governance.

(Authoritative Open Group guidance distinguishes conceptual, logical, and physical concerns; at the logical level, component types are identified independently of implementation.) For example, the Open Group’s metamodel guidance emphasizes technology-agnostic structure to ensure consistency within an architecture description, which is precisely what the logical level captures before physical realization.

“The Content Metamodel defines a formal structure… to ensure consistency within the architecture description and also to provide guidance for organizations that wish to implement their architecture within an architecture tool.” Open Group Publications

Building blocks are reusable components of business, IT, or architectural capability that can be combined to deliver architectures and solutions. Building blocks can be defined at various levels of detail, depending on the stage of architecture development. In the earlier phases of the ADM cycle (A to D), building blocks are defined in generic terms, such as logical or physical, to provide a high-level view of the architecture. In Phase E: Opportunities and Solutions, building blocks become implementation-specific, meaning that they are linked to specific products, standards, technologies, and vendors that are available in the market. This phase also identifies the delivery vehicles, such as projects, programs, or portfolios, that will realize the building blocks12 References: 1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 23: Phase E: Opportunities and Solutions 2: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 36: Building Blocks

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

In TOGAF, the Architecture Landscape is classified across three levels: Strategic, Segment, and Capability. These levels represent increasing detail and decreasing scope as you move downward through the model.

The top level (C) represents the Enterprise Strategic Architecture. This level provides a broad, long-term view of the enterprise, aligned with business strategy and covering the entire organization. It defines the overall direction, policies, and high-level structure of the enterprise architecture.

The middle level (B) represents the Segment Architecture. This level focuses on specific business segments, divisions, or domains within the enterprise. It translates strategic intent into more detailed architectural guidance relevant to particular areas of the organization.

The bottom level (A) represents the Capability Architecture, which is the most detailed level, focusing on specific capabilities and implementation concerns.

Given this structure:

C corresponds to Enterprise Strategic Architecture (1)

B corresponds to Segment Architecture (2)

Thus, the correct mapping is B-2, C-1, which is Option D.

This reflects TOGAF’s hierarchical approach where strategic architecture guides segment architecture, which in turn guides capability-level implementations.

===========

The illustration shows the relationship between the Enterprise Continuum, the Architecture Continuum, and the Solutions Continuum, which are key concepts in the TOGAF framework. The Enterprise Continuum is a view of the Architecture Repository that shows how generic foundation architectures can be leveraged and specialized to support the requirements of an individual organization. The Architecture Continuum specifies a structured classification for architectural artifacts, such as models, patterns, and descriptions, that can be reused and adapted across different domains and levels of abstraction. The Solutions Continuum identifies implemented solutions that support various stages of business and IT capability evolution, such as common systems, industry solutions, and organization-specific solutions. The illustration also shows how the architecture context and requirements are influenced by external factors, such as business drivers, stakeholders, and standards, and how they shape the generic and specific architectures and solutions. The illustration also shows how the deployed solutions become part of the architecture context for future iterations of the architecture development cycle. References:

•TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 6: Architecture Repository, Section 6.2 Enterprise Continuum.

•TOGAF Standard, 10th Edition, Part IV: Architecture Content Framework, Chapter 35: Enterprise Continuum and Tools, Section 35.1 Introduction.

Statements 1 and 3 highlight the value and necessity for Architecture Governance to be adopted within organizations. Architecture Governance is the practice and orientation by which Enterprise Architectures and other architectures are managed and controlled at an enterprise-wide level12. It ensures that architectural decisions are aligned with the organization’s strategy, objectives, and standards. Architecture Governance also involves establishing and maintaining processes, decision-making, and mechanisms to avoid or minimize potential conflicts of interest, such as between different stakeholders, business units, or projects34. Moreover, Architecture Governance requires transparency and accountability for all actions implemented and their decision support, so that they can be inspected and evaluated by authorized parties, such as auditors, regulators, or customers5 . References:

•The TOGAF Standard, Version 9.2 - Architecture Governance - The Open Group

•Architecture Governance - The Open Group

•Tutorial: Governance in TOGAF’s Architecture Development Method (ADM)

•Architecture Governance in TOGAF: Ensuring Effective Management and Compliance

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

•[Architecture Governance in TOGAF: Ensuring Alignment and Control]

The statement illustrates iteration and the ADM. Iteration is the technique of repeating a process or a phase with the aim of improving or refining the outcome. Iteration allows for feedback loops and adaptations at any point in the architecture development and transition process. Separate projects may operate their own ADM cycles concurrently, with relationships between the different projects, to address different aspects or levels of the architecture in an iterative manner. Reference: The TOGAF® Standard | The Open Group Website, Section 3.1 Introduction to the ADM.

In TOGAF, each ADM phase has a specific purpose and associated objectives. Objective 1 refers to development of the Target Data Architecture, which belongs to Phase C: Information Systems Architectures. Therefore, 1 matches C. Objective 2 refers to development of the Target Business Architecture, which is the purpose of Phase B: Business Architecture. Therefore, 2 matches B.

Objective 3 describes creation of a high-level aspirational vision of capabilities and business value. That is the defining purpose of Phase A: Architecture Vision. Therefore, 3 matches A. Objective 4 refers to identifying candidate Architecture Roadmap components based on the gaps between Baseline and Target Technology Architectures. This is associated with Phase D: Technology Architecture, where the target technology state is defined and gaps are used to identify roadmap components. Therefore, 4 matches D.

Putting these together gives the sequence 1C-2B-3A-4D, which corresponds to Option A. This mapping reflects the standard TOGAF ADM flow from vision, to business, to information systems, and then to technology architecture development.

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.