The correct answer is C, as it aligns with the TOGAF ADM approach and best practices for organizing architecture work in a phased and structured manner.

Analysis of the Correct Answer (Option C):

Identifying Projects, Dependencies, and Synergies

The scenario describes a phased approach to vehicle development over five years.

Identifying dependencies ensures a logical and structured rollout of technology and business capabilities.

Developing High-Level Architecture Descriptions

Since Business Architecture is already defined, it is now time to develop high-level descriptions of Information Systems and Technology Architectures.

TOGAF emphasizes incremental and iterative refinement, meaning that starting with high-level descriptions is a logical first step.

Determining Workload and Resource Allocation

TOGAF ADM Phase B, C, and D involve creating architecture descriptions.

Understanding how much work is required ensures efficient resource planning and allocation.

Identifying Reference Architectures and Building Blocks

Using reference architectures and reusable architecture building blocks (ABBs) is a key best practice in TOGAF.

This enables efficiency and consistency in architecture development.

Evaluating Costs, Risks, and Feasibility

TOGAF emphasizes a risk-aware approach to enterprise architecture.

Documenting options, risks, and control measures ensures feasibility before execution.

Why Other Options Are Incorrect?

Option A: Initiating ADM Phase A Again

Incorrect because the scenario states that the Architecture Vision has already been completed.

Phase A is used for initial vision-setting, but at this point, the focus is on executing defined architectures.

Option B: Researching Data Companies for Target Architecture Development

Incorrect because the focus should be on defining internal architectures rather than external research.

While benchmarking best practices can be useful, it is not the primary activity at this stage.

Option D: Studying Other Companies and Performing Readiness Assessment

Incorrect because the focus should be on leveraging the organization ' s existing architecture and resources.

Solution provider readiness assessments are typically part of procurement, not enterprise architecture development.

Comprehensive and Detailed Step-by-Step Explanation

Context of the Scenario

The agency is initiating a strategic “AI-first” plan to transform processes using AI and improve efficiency while ensuring service improvements for citizens. Several stakeholder concerns have been raised, such as:

Job security for employees.

Skill development for adapting to new technologies.

Cybersecurity and resilience risks due to reliance on digital platforms.

TOGAF emphasizes the importance of stakeholder management, communication, and risk management to ensure successful adoption and implementation of new architecture. These concerns need to be addressed methodically by gathering requirements, analyzing stakeholder positions, and ensuring proper communication of risks and benefits.

Option Analysis

Option A:

Strengths:

Proposes creating an Organization Map to identify the links between different parts of the agency and the impact of the strategic change.

Suggests holding stakeholder meetings to address concerns.

Includes managing risks as part of Security Architecture development.

Weaknesses:

Focusing solely on creating business models and teaching stakeholders how to interpret them does not directly address cultural and positional concerns about job loss, skill development, and security.

Risk management is addressed as part of Security Architecture development but lacks broader integration into stakeholder requirements.

Conclusion: Incorrect, as it fails to systematically document stakeholder concerns and map them into requirements and architecture decisions.

Option B:

Strengths:

Highlights the importance of formal stakeholder identification and creating a Communication Plan.

Suggests addressing stakeholder concerns through communication and risk management.

Weaknesses:

Does not go into detail on analyzing stakeholder concerns, cultural positions, or specific requirements.

Lacks the inclusion of stakeholder feedback in architecture artifacts like the Architecture Vision or Requirements Specification, which are critical TOGAF outputs.

Conclusion: Incorrect, as it does not include a systematic and structured approach for stakeholder analysis and integration into architecture deliverables.

Option C:

Strengths:

Emphasizes conducting a thorough stakeholder analysis to document concerns, positions, and cultural factors, which aligns with TOGAF’s approach in Phase A (Architecture Vision).

Ensures stakeholder views and requirements are recorded in the Architecture Vision document and reflected in the Architecture Requirements Specification.

Includes continuous assessment and feedback, ensuring concerns are addressed and risks managed effectively.

Aligns with TOGAF ' s principle of involving stakeholders in architecture development to ensure alignment and success.

Weaknesses:

Could further detail how risk management is included across all phases, but this is implied through integration into the Architecture Requirements Specification.

Conclusion: Correct, as it provides a structured and detailed approach for addressing stakeholder concerns and managing risks within TOGAF’s framework.

Option D:

Strengths:

Suggests categorizing stakeholders into groups and creating models for each category.

Proposes arranging meetings to verify that concerns have been addressed.

Includes risk management as part of the process.

Weaknesses:

Dividing stakeholders into generic categories (e.g., corporate functions, project team) may not adequately capture specific cultural factors and concerns raised in the scenario.

Lacks integration of stakeholder feedback into architecture deliverables such as the Architecture Vision and Architecture Requirements Specification.

Conclusion: Incorrect, as it provides a generalized and less targeted approach to stakeholder concerns compared to Option C.

TOGAF References

Stakeholder Management (Phase A): TOGAF emphasizes analyzing stakeholders’ positions, concerns, and issues to shape architecture development and communication (TOGAF 9.2, Section 24.2).

Architecture Vision: Captures high-level requirements and stakeholder views to ensure alignment with business goals (TOGAF 9.2, Section 6.2).

Architecture Requirements Specification: Records detailed requirements, including those related to risk management, to guide the development of target architectures (TOGAF 9.2, Section 35.5).

Iterative Feedback: Regular assessments and feedback loops are critical to ensure stakeholder concerns are addressed effectively throughout the ADM cycle.

By selecting Option C, the approach adheres to TOGAF ' s principles of stakeholder analysis, communication, and integration of concerns into architecture development.

Option C most accurately reflects the TOGAF standard’s guidance on Architecture Contracts and Architecture Governance during implementation (Phase G).

The Architecture Contract in TOGAF formalizes the agreement between the architecture function and the implementation organization. It must clearly define objectives, performance measures, deliverables, quality criteria, risks, and acceptance terms. This ensures consistent quality and traceability across distributed implementations, which directly addresses the Chief Engineer’s concern about inconsistent deployment across multiple plants.

TOGAF further requires architecture compliance reviews at defined checkpoints to verify conformance to the Architecture Definition. Any deviations must be formally reviewed by the Architecture Board. If justified, a dispensation may be granted; however, this must follow a governed process, not informal adjustment.

For third-party suppliers, TOGAF states that contracts must be legally enforceable to ensure compliance. Additionally, governance frameworks should include a dispute resolution mechanism to manage disagreements not resolved through compliance review.

Options A and B omit structured compliance review scheduling and formal governance rigor. Option D incorrectly suggests modifying the Architecture Definition through a new Request for Architecture Work, which is not required for local dispensations.

Therefore, according to TOGAF Architecture Governance guidance, Option C is the best answer.

The scenario states that:

A strategic architecture and roadmap already exist.

Business Architecture is complete, so the work now shifts to Information Systems and Technology Architectures (ADM Phases B–D).

The CTO requires use of the purpose-based EA Capability model (from the TOGAF Series Guide: A Practitioner’s Approach to Developing Enterprise Architecture Following the TOGAF ADM).

The EA team has to plan, organize, and manage the next stage of architecture development, including re-use of existing hardware/software platform components, candidate solutions, feasibility, risks, and prioritization.

Under the purpose-based EA approach, when moving from strategy into defining the next layers of architecture, TOGAF emphasizes:

Using the superior (already-approved) architecture to guide the next ADM cycles– This corresponds to the strategic architecture that is already completed.

Analyzing project dependencies, overlaps, and sequencing

Defining high-level architecture descriptions for the next iteration

Identifying reference architectures and candidate building blocks (especially when reusing existing platform components)

Assessing feasibility, value, cost, and risk for each project

Preparing for stakeholder trade-offs before formalizing the roadmap

These tasks map directly to Option A.

Why Option A is correct

Option A includes exactly what the purpose-based EA approach prescribes at this stage:

“The superior architecture should be used to guide the approach.”✔ Correct — strategic architecture guides the work.

“Review the identified projects, dependencies, and potential overlaps, then decide the order…”✔ Correct — sequencing and dependency assessment are core early tasks in Phases B–D planning.

“Develop high-level architecture descriptions.”✔ Correct — Business Architecture is done; now high-level IS/Tech Architecture descriptions are needed.

“Identify reference architectures and candidate building blocks.”✔ Correct — aligns with TOGAF building-block approach, and specifically fits the scenario where existing platform components will be reused.

“Identify resource needs, considering cost and value.”✔ Correct — mandatory for feasibility and planning.

“Document options, risks, and ways to control them to enable feasibility analysis and trade-off with stakeholders.”✔ Correct — this matches ADM guidelines for preparing options and addressing complexity before deeper development.

This is precisely how TOGAF expects the architecture team to plan, organize, and manage an ADM cycle after strategy is set.

The correct answer is C, as it aligns with the key TOGAF principles necessary for guiding enterprise architecture in a merger scenario where retail operations and systems are being consolidated.

Analysis of the Principles in Option C:

Common Use Applications

Since the two companies are merging, it is essential to standardize applications across the enterprise.

Using common applications ensures consistency, reduces costs, and improves efficiency.

TOGAF emphasizes this principle to prevent duplicate or redundant systems, which aligns with the CIO’s goal of reducing the number of applications used.

Data is an Asset

In the scenario, a central inventory management system is a core business function.

Treating data as an asset ensures it is managed properly, shared efficiently, and used strategically across the merged organization.

This principle supports the company’s ability to predict demand, adjust stock levels, and automate reordering.

Common Vocabulary and Data Definitions

The merger requires integrating different systems and data structures.

Having a common vocabulary ensures that all stakeholders (stores, fulfillment centers, and digital platforms) use consistent terminology and data definitions.

This minimizes confusion and ensures interoperability across business functions.

Maximize Benefit to the Enterprise

Every architectural decision should focus on the overall benefit to the business.

By consolidating IT systems and reducing redundancies, the company achieves cost savings, which directly supports this principle.

Business Continuity

The stores operate seven days a week, so system changes must ensure uninterrupted service.

Business continuity ensures that customers are not affected during the transition and that critical retail operations (sales, inventory tracking, and fulfillment) remain functional.

Why Other Options Are Incorrect?

Option A: Control Technical Diversity, Interoperability, Data is an Asset, Data is Shared, Business Continuity

Control Technical Diversity is not the primary concern here. The focus is on system consolidation, not necessarily on limiting technology diversity.

Interoperability is important but not as critical as defining a common system and data structure.

Option B: Service Orientation, Compliance with the Law, Requirements-Based Change, Responsive Change Management, Data Security

While service orientation and compliance are valuable, they are not the most relevant to this specific business transition.

Change management and data security are important but do not address the primary enterprise-wide architectural concerns of system consolidation.

Option D: Ease of Use, Common Use Applications, Data is an Asset, Technology Independence, Business Continuity

Ease of Use is beneficial but is not a core architecture principle in this case.

Technology Independence is useful but does not align directly with the scenario’s priority, which is consolidating applications and data structures.

Option D most precisely reflects the TOGAF example Architecture Principles and aligns directly with the explicit constraints described in the scenario.

The healthcare environment described is highly regulated, data-sensitive, and operationally life-critical. The principle Common Vocabulary and Data Definitions is fundamental because the organization shares electronic health records across providers and relies on standardized medical coding. For AI-based systems to function correctly and safely, consistent interpretation of clinical data across divisions is mandatory.

The principle Data Security directly addresses the requirements for privacy, prevention of breaches, regulatory compliance, integrity of patient records, and continuous availability of systems that support life-critical operations. In healthcare, availability is not merely operational—it is safety-related.

The principle Requirements-Based Change ensures that architecture decisions are driven by validated business and clinical requirements. The scenario clearly emphasizes patient outcomes, life-critical timing, and minimal disruption. This principle ensures AI adoption is justified by measurable clinical and business needs rather than by competitive pressure alone.

The other options contain partially relevant principles but do not collectively address clinical data consistency, regulatory protection, safety, and requirement traceability as comprehensively as Option D.

Therefore, according to TOGAF Architecture Principles guidance, Option D is the best answer.

An Enterprise Architecture Capability is the ability of the organization to perform effective and efficient architecture work, including the definition, governance, and management of its architectures2. The Preliminary Phase involves the following activities1:

•Reviewing the organizational context, scope, and drivers for conducting Enterprise Architecture

•Establishing the Architecture Capability desired by the organization, including the maturity level, roles, responsibilities, processes, and tools

•Defining and establishing the Organizational Model for Enterprise Architecture, which describes how the architecture function is organized and integrated within the enterprise

•Defining and establishing the Architecture Governance framework, which provides the mechanisms for ensuring the quality, consistency, and compliance of the architecture work

•Selecting and implementing the tools that support the Architecture Capability, such as repositories, modeling tools, and communication tools

•Defining the Architecture Principles that will guide and constrain the architecture work, based on the business principles, goals, and drivers of the organization

•Defining the Organization-Specific Architecture Framework, which is an adaptation of the generic TOGAF ADM to suit the specific requirements, standards, and practices of the organization

The Preliminary Phase is essential for preparing the organization for the successful development and implementation of its architectures, as well as for ensuring the alignment of the architecture work with the business strategy and objectives1.

The class of information known as the Reference Library within the Architecture Repository contains guidelines and templates used to create new architectures. The Reference Library provides a set of resources that can be leveraged or customized for specific architecture development purposes. It includes generic building blocks, patterns, models, standards,frameworks, methods, techniques, best practices, etc. Reference: The TOGAF® Standard | The Open Group Website, Section 2.4 Architecture Repository.