ADM Techniques

Key techniques applied throughout the ADM, including architecture principles, stakeholder management, gap analysis, business scenarios, and risk management.

5 minutes 5 Questions

ADM Techniques in TOGAF 10 Foundation refer to the specific methods, tools, and practices used to execute the Architecture Development Method (ADM) cycles effectively. These techniques enable architects to gather information, analyze requirements, design solutions, and manage transitions throughout…

Concepts covered
Stakeholder Management TechniqueGap Analysis TechniqueBusiness Transformation Readiness AssessmentCapability-Based PlanningArchitecture Views and ViewpointsArchitecture PrinciplesArchitecture PatternsBusiness ScenariosRisk ManagementInteroperability Requirements
Test mode:
Start practice test

TOGAF Foundation - ADM Techniques Example Questions

Test your knowledge of ADM Techniques

Question 1

An enterprise architect discovers that two key stakeholders — the CTO and the head of operations — have conflicting views on architecture priorities. Both hold high power and high interest. The architect has already completed stakeholder identification and created a power/interest grid. When applying the TOGAF Stakeholder Management Technique, what should the architect focus on next to resolve this conflict effectively?

Correct Answer: Determine each stakeholder's specific concerns and viewpoints to tailor appropriate engagement and communication approaches for both parties

The TOGAF Stakeholder Management Technique follows a defined sequence: after identifying stakeholders and classifying them on a power/interest grid, the next step is to understand each stakeholder's specific concerns, viewpoints, and key issues so that tailored engagement and communication strategies can be developed for each.

Reassessing their classification is inappropriate because both stakeholders genuinely hold high power and high interest, and artificially repositioning one would be dishonest and counterproductive. Using a single unified communication plan ignores the fact that different stakeholders have different concerns requiring tailored approaches. Escalating to the Architecture Board prematurely bypasses the architect's responsibility to first understand and reconcile stakeholder concerns through proper engagement.

Key concept tested: the sequential steps of the TOGAF Stakeholder Management Technique, specifically understanding stakeholder concerns after classification.

Question 2

In TOGAF, what does interoperability requirements define for an architecture?

Correct Answer: The ability of systems or components to exchange and use information across organizational boundaries

In TOGAF, interoperability requirements define the ability of systems or components to exchange and use information across organizational boundaries, which is essential for ensuring that different systems can work together effectively within and between enterprises.

The other options are incorrect because maintaining consistent performance across platforms relates to portability or performance requirements, not interoperability. Stakeholder collaboration on deliverables through governance describes architecture governance processes, not interoperability. Scaling processing capacity based on workload demands refers to scalability requirements.

The key concept tested is the TOGAF definition of interoperability, which focuses on information exchange and usage between systems across boundaries.

Question 3

A company has two departments that each use their own email and calendar tools. Employees struggle to schedule meetings across departments. A new architect is asked to fix this. What type of requirement should the architect define first to address this problem?

Correct Answer: Interoperability requirements that specify how the two systems should exchange scheduling data

The correct answer defines interoperability requirements that focus on how the two separate systems should exchange scheduling data, which directly addresses the cross-department scheduling problem by enabling communication between existing systems without mandating a single solution.

Defining individual functional requirements for each tool does not solve the cross-department integration problem. Specifying a single vendor platform is a solution constraint, not a proper interoperability requirement, as interoperability should be vendor-neutral and focus on data exchange standards. Performance benchmarks for email systems are unrelated to the scheduling interoperability issue.

The key concept tested is understanding interoperability requirements in TOGAF, which define how systems interact and exchange information across organizational boundaries.

More ADM Techniques questions
295 questions (total)
Practice 100 questions
One session at a time, always new questions