Free Practice Questions for The Open Group OGEA-101 Exam

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.

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.

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

According to the TOGAF standard, the need for the ADM process to be governed is to ensure that the architecture development and implementation activities are conducted in a consistent, coherent, and compliant manner1. Governance provides the means to verify that the method is being applied correctly and effectively, and that the architecture deliverables and artifacts meet the quality and standards criteria1. Governance also enables the management of risks, issues, changes, and dependencies that may arise during the ADM process1.

Some of the benefits of governing the ADM process are2:

•Improved alignment of the architecture with the business strategy and objectives

•Enhanced stakeholder engagement and communication

•Increased reuse and integration of architecture assets and resources

•Reduced complexity and duplication of architecture efforts

•Increased agility and adaptability of the architecture to changing needs and requirements

•Improved compliance and auditability of the architecture outcomes and outputs

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.

According to the TOGAF Standard, 10th Edition, documents which are under development and have not undergone any formal review and approval process are called draft documents, while documents which have been reviewed and approved are called approved documents 1. Draft documents are typically marked with a version number of 0.x, indicating that they are incomplete or provisional. Approved documents are typically marked with a version number of 1.0 or higher, indicating that they have been finalized and authorized. The other options are not correct, as they are not the terms used by the TOGAF Standard to distinguish between documents under development and documents that have been reviewed and approved. The terms “finalized”, “concept”, “deliverable”, and “Version 0.1” and “Version 1.0” are not specific to the TOGAF Standard, and they may have different meanings or interpretations in different contexts. References: 1: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 7: Applying Iteration to the ADM, Section 7.2.3 Document Categorization.

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.

The TOGAF ADM uses Gap Analysis during Phases B, C, and D (Business, Information Systems, and Technology Architectures) to identify building block gaps—the differences between the Baseline Architecture and the Target Architecture. However, simply identifying gaps does not complete the process.

The association of gaps with work packages happens later in the cycle:

Phase E: Opportunities and Solutions is where the identified gaps are analyzed and translated into work packages, projects, or initiatives that will deliver the required changes.

In Phase E, architects also determine whether Transition Architectures are needed, and they generate the initial Architecture Roadmap.

This is the phase where gaps become actionable, linked with specific work packages that can be executed to close them.

Phase F (Migration Planning) takes this further by finalizing the roadmap and building the detailed Implementation and Migration Plan, but the initial association of gaps with work packages occurs in Phase E.

Based on the illustration, the phase of the ADM labeled as item 2 is the Implementation Governance phase. This phase provides architectural oversight for the implementation. It ensures that the implementation project conforms to the architecture. It also provides a framework for monitoring and managing the implementation.

The Implementation Governance phase involves the following activities:

Finalizing the Architecture Roadmap and the supporting Implementation and Migration Plan

Assigning an Architecture Board to oversee the implementation

Establishing Architecture Contracts with the implementation partners

Reviewing and approving the implementation project plans and deliverables

Performing Architecture Compliance reviews to ensure alignment with the architecture

Performing Architecture Audit reviews to ensure quality and performance of the architecture

Resolving any architecture issues or change requests that arise during the implementation

Maintaining the architecture lifecycle and ensuring its continuity

The Implementation Governance phase is essential for ensuring that the architecture is realized as intended and that it delivers the expected business value and outcomes.

Implementation Governance