The correct answer is A .

The statement illustrates iteration within the TOGAF ADM. TOGAF 9.2 explains that the ADM is iterative, both across the whole ADM cycle and between individual phases. Architecture work is not always a single linear sequence from Phase A through Phase H. Instead, architecture projects may move through repeated cycles to refine architecture content, address stakeholder concerns, mature the architecture, and respond to changing requirements.

The specific phrase “projects may cycle between ADM phases, in planned cycles covering multiple phases” describes an iterative approach. This means that selected ADM phases can be revisited as part of planned architecture development cycles.

Option A , Iteration , is correct because cycling between ADM phases is an example of iterative architecture development.

Option B , Requirements Management , is incorrect because Requirements Management is a central ADM activity that manages architecture requirements throughout the ADM cycle. However, the phrase “cycle between ADM phases” specifically refers to iteration, not requirements handling.

Option C , Implementation Governance , is incorrect because Implementation Governance is Phase G of the ADM. It ensures implementation projects conform to the Target Architecture, but it does not describe the general cycling between ADM phases.

Option D , Enterprise Architecture , is incorrect because Enterprise Architecture is the broader discipline and subject area. The specific concept illustrated by planned cycling between ADM phases is iteration .

The correct answer is B .

In TOGAF 9.2, risks may be identified while developing Business Scenarios because Business Scenarios are used to identify and understand the business requirements that the architecture must address. A good Business Scenario captures the business process, the business and technology environment, the actors, the desired outcome, and the implications of the problem being addressed. In doing so, risks, constraints, and assumptions can be identified as part of understanding the business requirements.

Option A is incorrect because the Business Transformation Readiness Assessment is a technique used to evaluate the organization’s readiness to undergo change. It is relevant to risk and implementation planning, but the wording “risks are identified as part of” most directly aligns with the Business Scenario technique and its use in understanding business requirements.

Option B is correct because TOGAF positions Business Scenarios as a technique for understanding business requirements. As part of that understanding, the architect identifies the relevant business drivers, actors, processes, constraints, and risks associated with the business need.

Option C is incorrect because Phase B is the Business Architecture phase. Although business change considerations can arise in Phase B, “assessing readiness for change” is specifically associated with the Business Transformation Readiness Assessment technique, not the main TOGAF statement about identifying risks through Business Scenarios.

Option D is incorrect because Gap Analysis is not a Preliminary Phase technique only. Gap Analysis is applied across ADM phases to identify differences between Baseline and Target Architectures. It is not the best match for the statement about identifying risks as part of understanding business requirements.

Therefore, the correct answer is B .

The correct answer is C .

Description 1 matches Architecture Principles . TOGAF 9.2 defines principles as general rules and guidelines that are intended to be enduring and seldom amended, and that inform and support how an organization sets about fulfilling its mission. Therefore, item 1 is Architecture Principles .

Description 2 matches Architecture Contracts . TOGAF defines Architecture Contracts as joint agreements between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture. They support effective Architecture Governance and help ensure that implementation activity conforms to the agreed architecture.

Description 3 matches Request for Architecture Work . This is the document sent from the sponsoring organization to the architecture organization to trigger the start of an architecture development cycle. It provides the business imperative and initiates architecture work.

Description 4 matches Architecture Requirements Specification . TOGAF defines the Architecture Requirements Specification as a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture.

Therefore, the correct mapping is:

1 = Architecture Principles

2 = Architecture Contracts

3 = Request for Architecture Work

4 = Architecture Requirements Specification

So the correct option is C .

The correct answer is A .

TOGAF 9.2 identifies four dimensions that are typically used to define and limit the scope of an architecture: Breadth , Depth , Time Period , and Architecture Domains . The dimension that asks, “To what level of detail should the architecting effort go?” is Depth . This dimension determines how much architectural detail is enough and where the boundary should be drawn between architecture work and related downstream activities such as system design, system engineering, and system development.

Option A , Depth , is correct because it directly concerns the level of detail required in the architecture effort.

Option B , Architecture Domains , is incorrect because it concerns which architecture domains are included, such as Business, Data, Application, and Technology Architecture.

Option C , Breadth , is incorrect because it concerns the extent of the enterprise covered by the architecture effort.

Option D , Project , is incorrect because TOGAF 9.2 does not list “Project” as one of the four standard architecture scope dimensions. The relevant TOGAF dimensions are Breadth, Depth, Time Period, and Architecture Domains.