Comprehensive and Detailed Step-by-Step Explanation

Context of the Scenario

The company is in the process of delivering requested architectures to support the introduction of

digital products and services. The Business Architecture is sufficiently defined, and the focus is on

developing the Information Systems and Technology Architectures.

TOGAF emphasizes breaking down large, complex transformation programs into manageable

projects, focusing on dependencies, risks, trade-offs, and sequencing of efforts. Based on the

scenario, the company must deal with:

Data privacy and residency compliance across different regions.

Re-use of existing architecture for efficiency.

Alignment of digital services with a global roadmap.

The activity described aligns with ADM Phases B (Business Architecture), C (Information Systems

Architecture), and D (Technology Architecture), with a focus on delivering architectures for

implementation.

Option Analysis

Option A:

Strengths:

Refers to developing high-level architecture descriptions and identifying reference architectures and

candidate building blocks, which align with ADM Phases B, C, and D.

Addresses feasibility analysis, trade-offs, and stakeholder engagement, which are part of architecture

development and decision-making in TOGAF.

Ensures that the architecture descriptions are resource-conscious, including cost and value analysis,

dependencies, risks, and synergies between projects.

Conclusion: Correct, as it provides a complete approach to organizing the work to deliver

architectures while adhering to TOGAF principles.

Option B:

Strengths:

Suggests creating architecture descriptions for the Application, Data, and Technology Architectures,

which are necessary for delivering requested architectures.

Addresses readiness assessments and the fitness of solutions.

Weaknesses:

Emphasizes looking outside the company and studying other companies’ models, which is not

necessarily aligned with TOGAF unless justified by specific gaps.

Skips essential TOGAF steps like feasibility analysis and detailed stakeholder engagement.

Conclusion: Incorrect, as it places undue emphasis on external research instead of leveraging

TOGAF’s structured ADM.

Option C:

Strengths:

Suggests reviewing the Architecture Vision and determining scope, which aligns with TOGAF

principles.

Proposes preparing an Architecture Roadmap and involving the Architecture Board for review.

Weaknesses:

Does not cover important elements such as candidate building blocks, feasibility analysis, or

stakeholder engagement.

Suggests starting the project prematurely without proper sequencing or risk trade-offs.

Conclusion: Incorrect, as it skips key steps and lacks a structured approach to dependencies and

resource management.

Option D:

Strengths:

Suggests revising the Architecture Vision and conducting a Stakeholder Analysis, which aligns with

Phase A of the ADM.

Weaknesses:

Returning to Phase A is not required here, as the Architecture Vision has already been defined.

Revising the vision at this stage indicates a step backward.

Lacks focus on feasibility analysis, dependencies, and sequencing, which are the immediate needs in

this phase.

Conclusion: Incorrect, as it unnecessarily revisits earlier ADM phases instead of progressing.

TOGAF Reference

ADM Phases B, C, D: Emphasizes developing detailed architectures, identifying candidate building

blocks, and addressing dependencies, risks, and resource needs (TOGAF 9.2, Chapters 8-10).

Architecture Roadmap and Feasibility Analysis: Guides sequencing and trade-offs for implementation

(TOGAF 9.2, Section 12.4).

Stakeholder Engagement: Critical for ensuring alignment and feasibility (TOGAF 9.2, Section 24.2).

Decision-Making and Trade-offs: TOGAF emphasizes documenting risks and trade-offs as part of

feasibility analysis (TOGAF 9.2, Section 6.4.1).