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

Answer : C

The Architecture Requirements Repository stores all the requirements that are output of the architecture development cycle, as well as the requirements that are input to the architecture development cycle1. The Architecture Requirements Repository includes the following types of requirements1:

* Stakeholder Requirements: These are the high-level requirements and expectations of the stakeholders, derived from the business drivers, goals, and objectives. They are captured and refined in the Architecture Vision phase and the Requirements Management phase.

* Architecture Requirements: These are the detailed requirements that specify what the architecture must do or deliver to meet the stakeholder requirements. They are derived and refined in the Business, Information Systems, and Technology Architecture phases.

* Implementation and Migration Requirements: These are the detailed requirements that specify what the implementation and migration projects must do or deliver to realize the architecture. They are derived and refined in the Opportunities and Solutions and Migration Planning phases.

The Architecture Requirements Repository is used to manage the architecture requirements throughout the architecture lifecycle, ensuring their traceability, consistency, and compliance1. The Architecture Board is the authority that reviews and approves the architecture requirements, as well as the architecture deliverables and artifacts, as part of the architecture governance process2.

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 : A

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.

Answer : B

According to the TOGAF standard, the need for the ADM process to be governed is to ensure that the architecture development and implementation activities are conducted in a consistent, coherent, and compliant manner1. Governance provides the means to verify that the method is being applied correctly and effectively, and that the architecture deliverables and artifacts meet the quality and standards criteria1. Governance also enables the management of risks, issues, changes, and dependencies that may arise during the ADM process1.

Some of the benefits of governing the ADM process are2:

* Improved alignment of the architecture with the business strategy and objectives

* Enhanced stakeholder engagement and communication

* Increased reuse and integration of architecture assets and resources

* Reduced complexity and duplication of architecture efforts

* Increased agility and adaptability of the architecture to changing needs and requirements

* Improved compliance and auditability of the architecture outcomes and outputs