Pass the The Open Group Enterprise Architecture OGEA-101 Questions and answers with CertsForce

The graphic represents the Architecture Alternatives and Trade-off technique described in the TOGAF ADM guidelines. This technique evaluates different architecture options against defined criteria derived from the Architecture Vision, Architecture Principles, and Requirements. The purpose of the method is to identify and compare multiple potential architecture approaches before selecting the most appropriate one.

In practice, architects generate several candidate architectures that could meet the enterprise’s needs. Each alternative is evaluated against criteria such as business value, risk, cost, compliance with principles, and alignment with requirements. Through structured comparison, stakeholders can understand the strengths and weaknesses of each alternative and select the most suitable architecture direction.

Because the evaluation process focuses on different architectural approaches for achieving the target state, the method is used to identify Alternative Target Architectures. These alternatives represent different ways the enterprise could structure its future architecture before committing to a single preferred solution.

The other options do not match the purpose of the diagram. Business Scenarios are used to understand requirements, Solution Building Blocks are implementation components, and Architecture Solutions represent final implementation outcomes rather than competing architecture options. Therefore, the method illustrated helps identify Alternative Target Architectures, making Option B the correct answer.

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.

The following activities are part of Risk Management:

Initial risk assessment

Risk mitigation and residual risk assessment

Risk monitoring

Risk Management is the process of identifying, assessing, and responding to risks that may affect the achievement of the enterprise’s objectives. Risk Management involves balancing positive and negative outcomes resulting from the realization of either opportunities or threats. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.3 Risk Management.

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.

The statement illustrates iteration and the ADM. Iteration is the technique of repeating a process or a phase with the aim of improving or refining the outcome. Iteration allows for feedback loops and adaptations at any point in the architecture development and transition process. Separate projects may operate their own ADM cycles concurrently, with relationships between the different projects, to address different aspects or levels of the architecture in an iterative manner. Reference: The TOGAF® Standard | The Open Group Website, Section 3.1 Introduction to the ADM.

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.

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.

===========

The Preliminary Phase is the phase in TOGAF where an organization establishes or enhances its Enterprise Architecture Capability. This includes defining governance structures, roles, responsibilities, processes, tools, and architectural principles. The objective is to prepare the organization to successfully execute the ADM.

Phase A focuses on Architecture Vision for a specific initiative, not on creating the overall EA capability. Phase G deals with implementation governance, and Phase H focuses on architecture change management. None of these phases are responsible for establishing the EA practice itself.

The Preliminary Phase answers foundational questions such as how architecture will be governed, who owns architecture decisions, how compliance will be enforced, and how architecture work will be integrated with other organizational processes. Therefore, creation of an Enterprise Architecture Capability clearly belongs to the Preliminary Phase.

In TOGAF, presenting alternatives and trade-offs to stakeholders is an important technique used during architecture development. Different architecture alternatives allow stakeholders to compare possible approaches, while trade-off analysis helps identify the advantages, disadvantages, risks, costs, and consequences of each option. This often exposes hidden concerns, unstated requirements, conflicting priorities, and principles that may not appear during normal requirements gathering.

This is especially useful when developing a Target Architecture because stakeholders may have different expectations or hidden agendas that only become clear when they must choose between competing options. By reviewing alternatives and trade-offs, architects can test assumptions, clarify constraints, and ensure that the selected Target Architecture reflects real enterprise needs. Architecture Views and Viewpoints are communication mechanisms, while Business Scenarios help discover requirements, but the wording “extract hidden agendas, principles, and requirements” most closely aligns with the use of alternatives and trade-offs .

Therefore, the correct answer is D .

===========