OGEA-101 Exam Dumps - TOGAF Enterprise Architecture Part 1 Exam (English)

“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

“The Content Metamodel defines a formal structure for these terms to ensure consistency within the architecture description…” A metamodel used across the enterprise enables consistency and completeness checking of the architecture description against the defined structure. Open Group Publications

Comprehensive and Detailed Explanation

The question is about a deliverable that:

Is first created in Phase A: Architecture Vision.

Is updated in Phase E: Opportunities and Solutions.

Helps the architect understand both the baseline and the target for the enterprise.

Let’s review each option:

A. Architecture Contracts

These are created in Phase G: Implementation Governance.

They formalize agreements between architecture and implementation teams, but are not produced in Phase A.

Incorrect.

B. Capability Assessment

In Phase A, the Capability Assessment is produced to assess the organization’s current capability maturity and to identify strengths and weaknesses (baseline).

In Phase E, it is updated to reflect the required target capability and to inform planning of the work packages and Transition Architectures.

This deliverable helps architects understand both baseline and target capability for the enterprise.

Correct.

C. Consolidated Gaps, Solutions, and Dependencies Matrix

This is produced in Phase E to consolidate results from Gap Analysis across Phases B, C, and D.

It is not started in Phase A, so it does not meet the condition.

Incorrect.

D. Stakeholder Map

This is produced in Phase A as part of stakeholder management.

It is not updated in Phase E, and it does not directly address baseline vs. target capability.

Incorrect.

Correct Mapping

The deliverable that fits all three conditions is the Capability Assessment (B).

References

The Open Group, TOGAF® Standard, Version 9.2, Part II: ADM — Phase A (Capability Assessment as an input to the Architecture Vision) and Phase E (updated Capability Assessment to guide Opportunities and Solutions).

The Open Group, TOGAF® 9 Certified Study Guide — description of Capability Assessment as a baseline/target capability comparison tool.

The Architecture Repository is the structural framework defined by TOGAF to store, manage, and leverage architecture artifacts, including reference models, standards, governance logs, and deliverables.

The Architecture Capability refers to governance and processes.

The Architecture Landscape shows Strategic, Segment, and Capability architectures, not storage.

The Enterprise Architecture Capability Model is not a defined TOGAF concept.

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 Implications section describes the impact of adhering to the principle on the organization, the processes, the information systems, and the technology23. It also identifies the changes, costs, and risks that may result from applying the principle23. The Implications section helps to communicate the benefits and consequences of the principle to the stakeholders and to guide the implementation and governance of the architecture23.

The other sections of the TOGAF template for Architecture Principles are1:

•Name: This section provides a short and memorable name for the principle that represents its essence and purpose23. The name should not mention any specific technology or solution23.

•Statement: This section provides a concise and formal definition of the principle that expresses the fundamental rule or constraint that the principle imposes23. The statement should be clear, unambiguous, and testable23.

•Rationale: This section provides the reasoning and justification for the principle, explaining why it is important and how it supports the business goals and drivers23. The rationale should also link the principle to the higher-level enterprise or IT principles that it elaborates on23.