OGEA-101 Exam Dumps - The Open Group Enterprise Architecture Questions and Answers

Comprehensive and Detailed Explanation From documents:

In TOGAF, a Business Scenario is an ADM technique used to capture and structure business requirements in a way that directly informs the development and validation of architectures. It frames a specific business problem (or opportunity) and articulates the desired outcomes/objectives, along with the business and technical context, the involved actors and roles (human and system), and the measures of success. This makes option A correct because it concisely captures the essence of a Business Scenario: a well-defined business problem coupled with the outcomes the business seeks to achieve.

A good Business Scenario typically includes:

The business problem/opportunity and drivers.

The business and technical environment/context in which the problem exists.

The desired outcomes/objectives and measures of success (how success will be recognized).

Actors and roles (both human and system) and their interactions.

Capabilities and high-level requirements implied by the scenario.

Business Scenarios are especially valuable in Phase A: Architecture Vision to validate scope, objectives, and business value, and they continue to be used throughout Phases B–D to test and validate the target architectures and to maintain requirements traceability via Requirements Management. They promote shared understanding among stakeholders and provide a concrete basis for evaluating solution options and assessing architecture fitness-for-purpose.

Why the other options are incorrect:

B. A use-case for developing a business model. While Business Scenarios and use-cases are related, a Business Scenario is broader. It provides context, problem, objectives, and measures of success; use-cases are often derived from or complement Business Scenarios to specify interactions, but a Business Scenario is not merely a use-case.

C. A method to quantify readiness for change. This describes Business Transformation Readiness Assessment, a separate TOGAF technique used to gauge an organization’s readiness to execute change. It is not what TOGAF defines as a Business Scenario.

D. A technique to identify differences between a baseline and a target architecture. That is Gap Analysis, another distinct ADM technique used to determine what needs to change to move from the current state to the desired future state.

References (official TOGAF materials; no links):

The Open Group, TOGAF® Standard, Version 9.2, Part III: ADM Guidelines & Techniques — Business Scenarios; also Requirements Management, and Phase A: Architecture Vision (Part II) for where Business Scenarios are applied.

The Open Group, TOGAF® Series Guide: Business Scenarios — definition, structure, and usage of Business Scenarios across the ADM.

The Open Group, TOGAF® 9 Foundation Study Guide (latest edition) — coverage of Business Scenarios as an ADM technique and their relationship to use-cases.

The Open Group, TOGAF® 9 Certified Study Guide (latest edition) — contrasts with related techniques (Gap Analysis; Business Transformation Readiness Assessment) and explains use within Phase A and Requirements Management. ===========

According to the TOGAF Standard, 10th Edition, risk is present in all phases within the Architecture Development Method (ADM), and it should be identified, classified, and mitigated before starting a transformation effort 1. Risk is defined as “the effect of uncertainty on objectives” 2, and it can have positive or negative impacts on the architecture project. Risk management is a technique that helps to assess and address the potential risks that may affect the achievement of the architecture objectives, and to balance the trade-offs between opportunities and threats. Risk management is applied throughout the ADM cycle, from the Preliminary Phase to the Requirements Management Phase, and it is integrated with other techniques, such as stakeholder management, business transformation readiness assessment, gap analysis, and migration planning 1. The other options are not correct, as they are not present in all phases within the ADM, and they are not necessarily identified, classified, and mitigated before starting a transformation effort. Budgetary constraints are the limitations on the financial resources available for the architecture project, and they are usually considered in Phase E: Opportunities and Solutions, and Phase F: Migration Planning 3. Schedule constraints are the limitations on the time available for the architecture project, and they are also usually considered in Phase E and F 3. Information gaps are the missing or incomplete data or knowledge that may affect the architecture project, and they are usually identified in Phase B: Business Architecture, Phase C: Information Systems Architecture, and Phase D: Technology Architecture . References: 1: TOGAF Standard, 10th Edition, Part III: ADM Guidelines and Techniques, Chapter 32: Risk Management. 2: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions. 3: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 16: Phase E: Opportunities and Solutions, and Chapter 17: Phase F: Migration Planning. : TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 13: Phase B: Business Architecture, Chapter 14: Phase C: Information Systems Architecture, and Chapter 15: Phase D: Technology Architecture.

An Enterprise Architecture Capability is the ability of the organization to perform effective and efficient architecture work, including the definition, governance, and management of its architectures2. The Preliminary Phase involves the following activities1:

•Reviewing the organizational context, scope, and drivers for conducting Enterprise Architecture

•Establishing the Architecture Capability desired by the organization, including the maturity level, roles, responsibilities, processes, and tools

•Defining and establishing the Organizational Model for Enterprise Architecture, which describes how the architecture function is organized and integrated within the enterprise

•Defining and establishing the Architecture Governance framework, which provides the mechanisms for ensuring the quality, consistency, and compliance of the architecture work

•Selecting and implementing the tools that support the Architecture Capability, such as repositories, modeling tools, and communication tools

•Defining the Architecture Principles that will guide and constrain the architecture work, based on the business principles, goals, and drivers of the organization

•Defining the Organization-Specific Architecture Framework, which is an adaptation of the generic TOGAF ADM to suit the specific requirements, standards, and practices of the organization

The Preliminary Phase is essential for preparing the organization for the successful development and implementation of its architectures, as well as for ensuring the alignment of the architecture work with the business strategy and objectives1.

Architecture Principles are general rules and guidelines that inform and support the way in which an organization sets about fulfilling its mission. They reflect a level of consensus among the various elements of the enterprise, and form the basis for making future IT decisions. One of the purposes of Architecture Principles is to establish a common understanding of how to control the business in pursuit of strategic objectives, by providing a framework for evaluating and agreeing on the changes that affect the enterprise’s architecture3 References: 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 23: Architecture Principles : The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 31: Architecture Principles

The Enterprise Continuum provides a classification mechanism for artifacts, showing how they evolve from generic Foundation Architectures and Reference Models to organization-specific architectures.

Option A is about tools, not the Continuum.

Option B describes the Architecture Principles.

Option C describes the Architecture Repository.

In the context of TOGAF, a stakeholder is any individual, team, or organization who has interests in, or concerns relative to, the outcome of the architecture. Concerns are those interests which pertain to any aspect of the system’s functioning, development or operation, including considerations such as performance, reliability, and security1. References:

•The TOGAF Standard, Version 9.2 - Definitions - The Open Group

The chart illustrates an important TOGAF concept: ADM phases can operate concurrently or iteratively rather than strictly sequentially. The diagram shows Phase A activities occurring first, after which the architecture development phases (Business, Data, Application, and Technology Architectures) overlap in time. This overlap demonstrates how architecture development work may proceed in parallel as information becomes available, allowing architects to refine and coordinate the candidate architecture more efficiently.

TOGAF explicitly supports iteration and concurrency across ADM phases. While the phases are presented in a logical order, they are not intended to be executed in a rigid step-by-step sequence in all situations. Instead, architects may work across several phases simultaneously to address dependencies, refine requirements, and accelerate the development of the candidate architecture and roadmap.

Option A best reflects this principle because it acknowledges that phases may run together as part of an iterative architecture development process until a coherent candidate architecture is produced and validated. Option B is incorrect because TOGAF does not mandate the use of specific project management tools such as Gantt charts. Option C is incorrect because the ADM is not strictly sequential. Option D is incorrect because the duration of phases is not fixed in TOGAF.

Therefore, the chart illustrates the concept that ADM phases may be executed concurrently to develop and validate the candidate 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

Gap Analysis is an ADM technique used in Phases B, C, and D of the TOGAF ADM (Business, Information Systems, and Technology Architectures).

Its main purpose is to validate the target architecture by comparing the Baseline Architecture with the Target Architecture and identifying:

Gaps (building blocks or capabilities present in the target but missing in the baseline).

Overlaps (building blocks duplicated across architectures).

Conflicts (inconsistencies between baseline and target).

The output of Gap Analysis provides:

A validated Target Architecture.

A set of identified gaps that must be addressed by future work packages in Phase E: Opportunities and Solutions.

Therefore, the purpose of Gap Analysis is best expressed as to validate the architecture (Answer D).

Why the other options are incorrect

A. Establish quality metrics for the architecture: This is part of performance management and governance, not Gap Analysis.

B. Identify non-functional requirements: Non-functional requirements are captured through requirements management and stakeholder analysis, not Gap Analysis.

C. Determine service levels: Service levels are typically defined in SLAs and operational models, not through Gap Analysis.

References

The Open Group, TOGAF® Standard, Version 9.2, Part III: ADM Guidelines & Techniques — Gap Analysis.

The Open Group, TOGAF® 9 Certified Study Guide — explains the role of Gap Analysis in validating architectures and identifying work package inputs.