The Open Group OGEA-10B TOGAF Enterprise Architecture Bridge Exam Practice Test

Answer : B

According to the TOGAF Standard, 10th Edition, documents which are under development and have not undergone any formal review and approval process are called draft documents, while documents which have been reviewed and approved are called approved documents 1. Draft documents are typically marked with a version number of 0.x, indicating that they are incomplete or provisional. Approved documents are typically marked with a version number of 1.0 or higher, indicating that they have been finalized and authorized. The other options are not correct, as they are not the terms used by the TOGAF Standard to distinguish between documents under development and documents that have been reviewed and approved. The terms ''finalized'', ''concept'', ''deliverable'', and ''Version 0.1'' and ''Version 1.0'' are not specific to the TOGAF Standard, and they may have different meanings or interpretations in different contexts. Reference: 1: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 7: Applying Iteration to the ADM, Section 7.2.3 Document Categorization.

Answer : D

These domains provide a consistent way to describe and understand the architecture from different perspectives, such as business, information, and technology12. Each domain has its own set of concepts, models, views, and artifacts that define the structure and behavior of the architecture within that domain12.

The other options are incorrect because:

* Logical and Physical are not architecture domains, but rather levels of abstraction that can be applied to any domain. Logical architecture describes the functionality and behavior of the system, while physical architecture describes the implementation and deployment of the system3.

* Information and Data are not distinct architecture domains, but rather aspects of the same domain. Information architecture describes the meaning and context of the data, while data architecture describes the structure and format of the data4.

* Capability and Segment are not architecture domains, but rather levels of granularity that can be applied to any domain. Capability architecture describes the current and desired states of a specific business capability, while segment architecture describes a subdivision of the enterprise that has a clear business focus5.

Answer : D

The Enterprise Continuum consists of two complementary concepts: the Architecture Continuum and the Solutions Continuum1. The Architecture Continuum provides a consistent way to describe and understand the generic and reusable architecture building blocks, such as models, patterns, and standards, that can be applied and tailored to specific situations2. The Solutions Continuum provides a consistent way to describe and understand the specific and implemented solution building blocks, such as products, services, and components, that realize the architecture building blocks3. The Enterprise Continuum enables the reuse and integration of architecture and solution assets across different levels of abstraction, scope, and detail, ranging from foundation architectures to organization-specific architectures1.

The Enterprise Continuum is used when developing an enterprise architecture to support the following activities1:

* Selecting relevant architecture and solution assets from the Architecture Repository or other sources, based on the business drivers, goals, and requirements

* Adapting and customizing the architecture and solution assets to suit the specific needs and context of the enterprise

* Defining and developing the target architecture and the architecture roadmap, based on the gaps and opportunities identified between the baseline and the target states

* Defining and developing the implementation and migration plan, based on the architecture roadmap and the solution building blocks

* Governing and managing the architecture and solution assets throughout the architecture lifecycle, ensuring their quality, consistency, and compliance

Answer : D

The Implications section describes the impact of adhering to the principle on the organization, the processes, the information systems, and the technology23. It also identifies the changes, costs, and risks that may result from applying the principle23. The Implications section helps to communicate the benefits and consequences of the principle to the stakeholders and to guide the implementation and governance of the architecture23.

The other sections of the TOGAF template for Architecture Principles are1:

* Name: This section provides a short and memorable name for the principle that represents its essence and purpose23. The name should not mention any specific technology or solution23.

* Statement: This section provides a concise and formal definition of the principle that expresses the fundamental rule or constraint that the principle imposes23. The statement should be clear, unambiguous, and testable23.

* Rationale: This section provides the reasoning and justification for the principle, explaining why it is important and how it supports the business goals and drivers23. The rationale should also link the principle to the higher-level enterprise or IT principles that it elaborates on23.

Answer : C

* Phase A: Architecture Vision

o Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture

o Define the scope and boundaries of the architecture engagement

o Identify the key stakeholders and their concerns and expectations

o Define the Architecture Vision statement and the Architecture Definition Document

o Obtain approval and commitment from the sponsors and stakeholders

* Phase B: Business Architecture

o Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals

o Define the Baseline Business Architecture, if not available

o Perform a gap analysis between the Baseline and Target Business Architectures

o Define candidate roadmap components for the Business Architecture

o Resolve impacts across the Architecture Landscape

* Phase C: Information Systems Architecture

o Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision

o Develop the Target Application Architecture that supports the Business Architecture and the Architecture Vision

o Define the Baseline Data and Application Architectures, if not available

o Perform a gap analysis between the Baseline and Target Data and Application Architectures

o Define candidate roadmap components for the Information Systems Architecture

o Resolve impacts across the Architecture Landscape

* Phase D: Technology Architecture

o Develop the Target Technology Architecture that enables the Information Systems Architecture and the Architecture Vision

o Define the Baseline Technology Architecture, if not available

o Perform a gap analysis between the Baseline and Target Technology Architectures

o Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures

o Resolve impacts across the Architecture Landscape

Therefore, the correct matching of the objectives and the phases is:

* 1C: Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision

* 2B: Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals

* 3A: Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture

* 4D: Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures

Answer : B

Risk is defined as the effect of uncertainty on objectives, according to the ISO 31000 standard, which provides principles and guidelines for risk management1Risk 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 implementation2Reference:1: ISO 31000:2018, Risk management --- Guidelines, Clause 3.12: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 32: Risk Management

Answer : C

The scope of an architecture is the extent and level of detail of the architecture work. The scope of an architecture can be defined along four dimensions: project, breadth, depth, and architecture domains. The project dimension considers the boundaries and objectives of the architecture project, such as the time frame, budget, resources, and deliverables. The breadth dimension considers the coverage and completeness of the architecture across the enterprise, such as the organizational units, business functions, processes, and locations. The depth dimension considers the level of detail and specificity of the architecture, such as the granularity, abstraction, and precision of the architectural elements and relationships. The architecture domains dimension considers the aspects or segments of the architecture, such as the business, data, application, and technology domains.

Therefore, the depth dimension is the one that considers to what level of detail the architecting effort should go.