The Open Group TOGAF Enterprise Architecture Part 1 OGEA-101 Exam Questions

Answer : A

Answer : D

The purpose of the Architecture Roadmap is to provide a high-level view of how the Baseline Architecture will transition to the Target Architecture over time. It lists work packages on a timeline showing progress towards the Target Architecture, as well as dependencies, risks, and benefits. The Architecture Roadmap forms part of the Implementation and Migration Plan and guides the execution of the architecture projects. Reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap20.html

Answer : C

''In addition to the method itself being iterative, there is also iteration within the ADM cycle, both among the individual phases and among the steps within a phase.'' www.opengroup.org

===========

Answer : C

Phase E: Opportunities & Solutions -- Steps/Outputs emphasize grouping work packages, dependencies, and planning the roadmap/plan that reflect value/effort:

''Identify and group major work packages... Refine and validate dependencies... Create the Architecture Roadmap & Implementation and Migration Plan.'' www.opengroup.org

===========

Answer : C

The Architecture Landscape is divided into levels known as Segment Strategic and Capability Architectures. These levels correspond to different scopes and purposes of architectures within an enterprise. Segment Architectures are architectures that address specific business units, functions, or processes within an enterprise. Strategic Architectures are architectures that provide a high-level view of the enterprise's vision, goals, and direction. Capability Architectures are architectures that address specific business capabilities or services that span multiple segments or domains. Reference: The TOGAF Standard | The Open Group Website, Section 2.4 Architecture Repository.

Answer : C

The illustration shows an architecture development cycle based on the TOGAF ADM (Architecture Development Method), which is a method for developing and managing an enterprise architecture1.

The ADM consists of nine phases, each with a specific purpose and output.The phases are1:

Preliminary Phase: To prepare and initiate the architecture development cycle, including defining the architecture framework, principles, and governance.

Phase A: Architecture Vision: To define the scope, vision, and stakeholders of the architecture initiative, and to obtain approval to proceed.

Phase B: Business Architecture: To describe the baseline and target business architecture, and to identify the gaps between them.

Phase C: Information Systems Architectures: To describe the baseline and target data and application architectures, and to identify the gaps between them.

Phase D: Technology Architecture: To describe the baseline and target technology architecture, and to identify the gaps between them.

Phase E: Opportunities and Solutions: To identify and evaluate the opportunities and solutions for implementing the target architecture, and to define the work packages and transition architectures.

Phase F: Migration Planning: To finalize the implementation and migration plan, and to ensure alignment with the enterprise portfolio and project management.

Phase G: Implementation Governance: To provide architecture oversight and guidance for the implementation projects, and to manage any architecture change requests.

Phase H: Architecture Change Management: To monitor the changes in the business and technology environment, and to assess the impact and performance of the architecture.

In addition to these phases, there is a central process called Requirements Management, which is labeled as item 1 in the illustration.This process operates throughout the ADM cycle, and its purpose is to manage the architecture requirements throughout the architecture development, ensuring that they are aligned with the business requirements and the stakeholder concerns2.

Therefore, the description that matches the phase of the ADM labeled as item 1 is C. Operates the process of managing architecture requirements.

1: The TOGAF Standard, Version 9.2, Chapter 5: Architecture Development Method (ADM)

2: The TOGAF Standard, Version 9.2, Chapter 17: Requirements Management

Answer : B

The graphic represents the Architecture Alternatives and Trade-off technique described in the TOGAF ADM guidelines. This technique evaluates different architecture options against defined criteria derived from the Architecture Vision, Architecture Principles, and Requirements. The purpose of the method is to identify and compare multiple potential architecture approaches before selecting the most appropriate one.

In practice, architects generate several candidate architectures that could meet the enterprise's needs. Each alternative is evaluated against criteria such as business value, risk, cost, compliance with principles, and alignment with requirements. Through structured comparison, stakeholders can understand the strengths and weaknesses of each alternative and select the most suitable architecture direction.

Because the evaluation process focuses on different architectural approaches for achieving the target state, the method is used to identify Alternative Target Architectures. These alternatives represent different ways the enterprise could structure its future architecture before committing to a single preferred solution.

The other options do not match the purpose of the diagram. Business Scenarios are used to understand requirements, Solution Building Blocks are implementation components, and Architecture Solutions represent final implementation outcomes rather than competing architecture options. Therefore, the method illustrated helps identify Alternative Target Architectures, making Option B the correct answer.