The Open Group Updated OGEA-101 Exam Questions and Answers by dolcie

This statement best describes iteration and the ADM. The ADM is iterative over the whole process between phases and within phases because it allows for feedback loops and refinements at any point in the architecture development and transition process. Iteration enables architects to address changing requirements, assumptions, constraints, and environments; to validate and improve architectures; to manage risks and issues; and to ensure stakeholder satisfaction and value realization. Reference: The TOGAF® Standard | The Open Group Website, Section 3.1 Introduction to the ADM.

The objectives listed in the question correspond to the objectives of different phases of 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.

Based on the above definitions, we can match each objective with the corresponding phase as follows:

Objective 1: Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision. This objective is achieved in Phase C: Information Systems Architectures, where the data architecture is defined as a subset of the information systems architecture2.

Objective 2: Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals. This objective is achieved in Phase B: Business Architecture, where the business architecture is defined as a subset of the enterprise architecture3.

Objective 3: Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture. This objective is achieved in Phase A: Architecture Vision, where the architecture vision is defined as a high-level description of the target architecture and its benefits4.

Objective 4: Develop the Target Application Architecture that enables the Business Architecture and the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns. This objective is achieved in Phase C: Information Systems Architectures, where the application architecture is defined as a subset of the information systems architecture2.

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

2: The TOGAF Standard, Version 9.2, Chapter 9: Phase C: Information Systems Architectures

3: The TOGAF Standard, Version 9.2, Chapter 8: Phase B: Business Architecture

4: The TOGAF Standard, Version 9.2, Chapter 7: Phase A: Architecture Vision

In TOGAF, an Architecture View is defined as the representation of a system from the perspective of a related set of concerns. This means a view is created to address the interests of specific stakeholders by focusing on those aspects of the architecture that matter to them. For example, business stakeholders may need a view centered on processes and capabilities, while technical stakeholders may need a view showing applications, interfaces, or technology infrastructure.

The other options are not correct because they refer to specific forms of architectural content rather than the broader concept of stakeholder-oriented representation. A Catalog is a list of architectural elements. A Matrix shows relationships between items. A Diagram presents information graphically. All of these may be used to help construct or express an architecture view, but they are not themselves the formal TOGAF concept being asked about in the question.

The key phrase in the question is “from the perspective of a related set of concerns.” That wording matches the TOGAF definition of an Architecture View. It is specifically intended to communicate architecture in a way that is meaningful to stakeholders and their concerns. Therefore, the correct answer is Architecture View.

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.