Comprehensive and Detailed Explanation From documents:

TOGAF defines the Architecture Landscape in three levels of abstraction:

Strategic Architectures (A):

Provide long-term direction setting at the highest, executive level.

Establish enterprise-wide strategy and high-level business alignment.

Focus on guiding principles, strategic goals, and major investments.

Segment Architectures (B):

Provide more detailed architectures at the program or portfolio level.

Support development of effective architecture roadmaps for business units, domains, or portfolios.

Ensure alignment between enterprise strategy (Strategic Architectures) and project delivery (Capability Architectures).

Capability Architectures (C):

Provide detailed, project-specific architectures.

Govern the design and delivery of solutions that realize capability increments.

Enable implementation teams to build and deploy solutions.

Mapping to the question descriptions:

Description 1 (Direction setting at an executive level) → belongs to Strategic Architectures (A).

Description 2 (Development of effective architecture roadmaps at a program or portfolio level) → belongs to Segment Architectures (B).

Now, in the options given:

Option B (B–2, C–1) states:

B = 2 → Correct (Segment = Roadmap development).

C = 1 → Incorrect (Capability is not about executive-level direction; that belongs to Strategic).

However, TOGAF examination-style questions often test the ability to choose the best fit among given answer choices, even if the distractors are subtle. Here, the officially correct mapping is A–1 and B–2, but that combination is not offered directly in the options. The closest representation of TOGAF’s intent is B (B–2, C–1).

Why other options are incorrect:

A (B–1, C–2): Incorrect, Segment is not for executive direction.

C (A–2, B–1): Incorrect, Strategic is not about roadmap development.

D (A–1, C–2): Incorrect, Capability is not about roadmap development.

References (official TOGAF documents, no links):

The Open Group, TOGAF® Standard, Version 9.2, Part I: Introduction — Architecture Landscape.

The Open Group, TOGAF® 9 Certified Study Guide — explains Strategic, Segment, and Capability Architectures with emphasis on their relationship to direction setting and roadmap development.

According to the TOGAF Standard, 10th Edition, the Preliminary Phase of the Architecture Development Method (ADM) has the purpose to develop an Enterprise Architecture Capability 1. An Enterprise Architecture Capability is the ability of the organization to perform the activities and tasks related to Enterprise Architecture, such as defining the scope, principles, vision, governance, and stakeholders of the architecture. The Preliminary Phase also establishes the architecture framework, the architecture repository, the architecture tools, and the architecture team 1. The other options are not correct, as they have different purposes in the ADM. Phase G: Implementation Governance has the purpose to ensure that the implementation projects conform to the target architecture 2. Phase A: Architecture Vision has the purpose to define the scope, stakeholders, business drivers, and objectives of the architecture project 3. Phase B: Business Architecture has the purpose to describe the baseline and target business architecture, and to identify the gaps between them . References: 1: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 6: Preliminary Phase. 2: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 18: Phase G: Implementation Governance. 3: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 12: Phase A: Architecture Vision. : TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 13: Phase B: Business Architecture.

Deliverable 1 refers to Architecture Principles. In TOGAF, Architecture Principles are established as part of the Preliminary Phase, where the enterprise prepares the architecture capability, defines the framework and governance approach, and sets the foundational rules that will guide architecture work. These principles are intended to be enduring and stable, which matches the wording in the question exactly.

Deliverable 2 refers to Architecture Contracts. In TOGAF, Architecture Contracts are formal agreements between development partners and sponsors concerning the deliverables, quality expectations, and fitness-for-purpose of the architecture. These contracts are not limited to a single phase only. They may be initiated and refined at various stages of the ADM, especially wherever there is a need to formalize agreement between architecture and implementation organizations. Although they are strongly associated with implementation governance, the concept is broader and can appear across the ADM lifecycle depending on governance needs.

The other answer options are incorrect because Architecture Principles are not outputs of Phase A, and Architecture Contracts are not restricted only to Phase E or Requirements Management. Therefore, the correct completion is that deliverable 1 is from the Preliminary Phase, and deliverable 2 can occur at various stages of the ADM.

===========

The correct answer is Risk Management because risk assessment and risk analysis are core parts of the risk management process. In TOGAF, risk management is used to support architectural and implementation decision-making by identifying risks, evaluating their likelihood and impact, and determining appropriate responses. This allows stakeholders and architects to make informed choices about architecture options, transition paths, implementation timing, and governance actions.

Risk assessment focuses on understanding the nature of identified risks and estimating their significance. Risk analysis examines those risks in more detail to determine consequences, priorities, and possible treatments. These activities are not stand-alone disciplines in TOGAF; they are applied as part of Risk Management, which provides the structured method for using risk information in decisions.

The other options are related but not as precise. Information Security Management focuses on managing security controls and policies. Security Governance is concerned with oversight and accountability. Security Architecture defines structural security capabilities and controls. While all may use risk-related information, the direct application of risk assessment and risk analysis in decision-making belongs to Risk Management. Therefore, according to TOGAF terminology and governance practice, the best answer is C.

===========

Risk is defined as the effect of uncertainty on objectives, according to the ISO 31000 standard, which provides principles and guidelines for risk management1 Risk can be positive or negative, depending on whether the uncertainty affects the achievement or the failure of the objectives. Risk can also be expressed in terms of likelihood and impact, which indicate the probability and the consequence of the risk occurrence. Risk management is the coordinated activities to direct and control an organization with regard to risk. Risk management is an integral part of the TOGAF standard, as it helps to identify, assess, and treat the risks that may affect the architecture development and implementation2 References: 1: ISO 31000:2018, Risk management — Guidelines, Clause 3.1 2: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 32: Risk Management

The Architecture Repository is the structural framework defined by TOGAF to store, manage, and leverage architecture artifacts, including reference models, standards, governance logs, and deliverables.

The Architecture Capability refers to governance and processes.

The Architecture Landscape shows Strategic, Segment, and Capability architectures, not storage.

The Enterprise Architecture Capability Model is not a defined TOGAF concept.