ScenarioCert
TOGAF 10 ยท Architecture Vision and architecture development (Phases A to D) (30-30%)

How to implement the Architecture Development Method (ADM) Phases B, C, and D to develop an architecture, together with the applicable techniques

Practice questions and explanations for the "How to implement the Architecture Development Method (ADM) Phases B, C, and D to develop an architecture, together with the applicable techniques" objective of the TOGAF Enterprise Architecture Practitioner (scenario questions) exam. Skills measured as of 2026-10-22.

Skills in this objective

  • Developing the Business Architecture with capabilities and value streams
  • Developing the Data and Application Architectures
  • Developing the Technology Architecture
  • Performing gap analysis between Baseline and Target Architectures
  • Defining candidate roadmap components and resolving impacts

Test yourself on this domain

Take the free 15-question test, or unlock all 150 questions and practice this domain on its own.

Sample questions

4 of the 25 questions we have for this objective, shown with the answer and the reasoning.

How to implement the Architecture Development Method (ADM) Phases B, C, and D to develop an architecture, together with the applicable techniques

Gorsefield Retail's Target Data Architecture consolidates customer data from three baseline databases into one customer data store. The migration team needs to see which baseline sources feed the target and what transformations happen on the way, so that it can plan data cleansing.

Which Phase C artifact should the architect produce?

  1. AA data entity/business function matrixThis matrix relates data entities to the business functions that use them. It does not show data moving from baseline to target.
  2. BA data migration diagramThe data migration diagram shows the flow of data from baseline sources to target, including the transformations applied, which is what the migration team needs.
  3. CAn application/technology matrixThis Phase D matrix maps applications to technology components. It does not describe data migration.
  4. DA business footprint diagramA Business Footprint diagram is a Business Architecture artifact that links business goals, organization units, functions and services to the technical components that deliver them. It is not a migration view.
Why: The Data Architecture in Phase C of the TOGAF Standard includes the data migration diagram, which shows the flow of data from source to target applications and data stores and the transformations along the way. It helps plan cleansing, quality checks and the order of migration. The scenario asks for exactly that baseline-to-target view. The distractors are real artifacts that relate data, applications or goals to something else.
How to implement the Architecture Development Method (ADM) Phases B, C, and D to develop an architecture, together with the applicable techniques

Kestrel Logistics is completing gap analysis in Phase C. The Application Architecture gap matrix lists Baseline building blocks as rows and Target building blocks as columns, with a final 'New' row on the Baseline axis and a final 'Eliminated' column on the Target axis. The baseline 'Fax Order Intake' application has no matching Target column and is marked in the Eliminated column. The 'Partner API Gateway' appears only in the New row.

Which two conclusions should the architect draw from the matrix? Each correct answer presents part of the solution.

  1. AFax Order Intake must be checked to confirm whether it was intentionally eliminated or accidentally omitted from the Target ArchitectureA baseline building block missing from the target is a gap that must be reviewed. If its function is still needed, the omission must be corrected in the target.
  2. BThe Partner API Gateway is a gap that must be filled by developing or procuring the building blockItems in the New row are target building blocks with no baseline counterpart. They represent capability that must be built or bought.
  3. CEvery cell marked 'Included' means the building block must be rebuilt for the target'Included' means the building block carries forward from baseline to target. It is not a gap and does not imply rebuilding.
  4. DFax Order Intake should be deleted from the Architecture Repository now that the matrix shows it as eliminatedThe repository keeps baseline descriptions; elimination is a planned change carried into the roadmap, not an immediate deletion of the record.
  5. EThe gaps should be left unrecorded until Phase E consolidates themEach of Phases B, C and D performs and records its own gap analysis. Phase E consolidates the gaps that those phases have already identified.
Why: The Gap Analysis technique (ADM Techniques, Chapter 5) uses a matrix with Baseline building blocks on the vertical axis and Target building blocks on the horizontal axis, a final row labeled New and a final column labeled Eliminated. A new item in the target is a gap to be filled by development or procurement. An item eliminated from the baseline must be checked: if the elimination was deliberate it is recorded as such, and if it was accidental the target must be corrected. The distractors misread 'Included', treat the repository as a list of current systems only, or push gap recording to Phase E.
How to implement the Architecture Development Method (ADM) Phases B, C, and D to develop an architecture, together with the applicable techniques

Larkspur Retail is in Phase C. The integration team must understand which applications exchange information with which others, and how, before the Target Application Architecture can be agreed. The architect is choosing artifacts from the Architecture Content Framework.

Which two artifacts should the architect produce? Each correct answer presents part of the solution.

  1. AAn application interaction matrixThe application interaction matrix shows which applications communicate with which others, giving a complete view of dependencies.
  2. BAn application communication diagramThe application communication diagram depicts the applications and the information flows and interfaces between them.
  3. CA platform decomposition diagramThe platform decomposition diagram is a Phase D artifact that breaks the technology platform into components. It does not show application exchanges.
  4. DA business capability mapA capability map shows business capabilities in Phase B. It does not show interfaces between applications.
  5. EA data lifecycle diagramA data lifecycle diagram shows the states a data entity passes through. It does not show which applications exchange information.
Why: The Application Architecture in Phase C of the TOGAF Standard uses the application interaction matrix to record the communication relationships between applications and the application communication diagram to depict those applications, their interfaces and the information that flows between them. Together they give the integration team the dependency view the scenario asks for. The distractors are real artifacts from Phase B, Phase D and the Data Architecture that answer other questions.
How to implement the Architecture Development Method (ADM) Phases B, C, and D to develop an architecture, together with the applicable techniques

Corriston Energy has finished gap analysis in Phase D for a grid analytics platform. Phases B and C each produced their own candidate roadmap components. The sponsor asks the architect to hand over a single, dated roadmap at the end of Phase D so that procurement can start, but several technology gaps depend on business and application changes that have not yet been sequenced together.

What should the architect do?

  1. ADefine the Technology Architecture candidate roadmap components from the Phase D gaps, then pass them with the Phase B and C components to Phase E for consolidation into the Architecture Roadmap, and explain this sequence to the sponsorEach of Phases B, C and D produces candidate roadmap components. Phase E consolidates them into an Architecture Roadmap with dependencies resolved, which is needed because the technology gaps depend on business and application changes.
  2. BProduce the Implementation and Migration Plan at the end of Phase D so procurement has datesThe Implementation and Migration Plan is finalized in Phase F after work packages and Transition Architectures are defined. Producing it in Phase D skips the consolidation and dependency analysis.
  3. CDefine work packages for the technology gaps in Phase D and let the business and application teams define their own laterWork packages are identified in Phase E across all domains. Defining technology packages in isolation ignores the cross-domain dependencies in the scenario.
  4. DSkip candidate roadmap components in Phase D because the roadmap is created only in Phase EPhase D includes a step to define candidate roadmap components. Phase E relies on these inputs from every domain to build the consolidated roadmap.
Why: The TOGAF Standard, 10th Edition has each architecture domain phase (Step 8 of Phases B, C and D, Define Candidate Roadmap Components) define candidate roadmap components: an initial, high-level view of the work needed to move from baseline to target in that domain. Phase E then consolidates the gaps and candidate components from Phases B, C and D, resolves dependencies, groups work into work packages and Transition Architectures, and produces the Architecture Roadmap; Phase F turns this into the Implementation and Migration Plan. The scenario's decisive fact is that technology gaps depend on unsequenced business and application changes, which is exactly what Phase E consolidation resolves. The distractors either jump ahead to Phase E or F outputs or drop the Phase D step altogether.

Written from the public documentation. Not affiliated with The Open Group. Official study guide.