Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. The Open Group
  5. OGEA-10B

The Open Group OGEA-10B Exam
TOGAF Enterprise Architecture Bridge (Page 3 )

Updated On: 1-Feb-2026
Page 3 of 22
PDF with 104 Questions

What are the four architecture domains that the TOGAF standard deals with?

  1. Business, Data, Application, Technology
  2. Capability, Segment, Enterprise, Federated
  3. Baseline, Candidate, Transition, Target
  4. Application, Data, Information, Knowledge

Answer(s): A

Explanation:

The TOGAF standard divides Enterprise Architecture into four primary architecture domains:
business, data, application, and technology. These domains represent different aspects of an enterprise and how they relate to each other. The business domain defines the business strategy, governance, organization, and key business processes. The data domain describes the structure of the logical and physical data assets and data management resources. The application domain provides a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes. The technology domain describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. Other domains, such as motivation, security, or governance, may span across these four primary domains.


Reference:

The TOGAF Standard, Version 9.2 - Core Concepts
Domains - The Open Group
TOGAF® Standard -- Introduction - Definitions - The Open Group The TOGAF Standard, Version 9.2 - Definitions - The Open Group TOGAF and the history of enterprise architecture | Enable Architect



What component of the Architecture Repository represents architecture requirements agreed with the Architecture Board?

  1. Reference Library
  2. Architecture Capability
  3. Architecture Requirements Repository
  4. Governance Log

Answer(s): C

Explanation:

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 cycle. The Architecture Requirements Repository includes the following types of requirements:
· 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 compliance. 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 process.


Reference:

1: Architecture Requirements Repository
2: Architecture Board



Complete the sentence. The architecture domains that are considered by the TOGAF standard as subsets of an overall enterprise architecture are Business, Technology,

  1. Logical and Physical
  2. Information and Data
  3. Capability and Segment
  4. Application and Data

Answer(s): D

Explanation:

These domains provide a consistent way to describe and understand the architecture from different perspectives, such as business, information, and technology. Each domain has its own set of concepts, models, views, and artifacts that define the structure and behavior of the architecture within that domain.
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 system. · 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 data. · 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 focus.


Reference:

1: The TOGAF Standard, Version 9.2 - Definitions
2: TOGAF® Standard -- Introduction - Definitions
3: [Logical vs Physical Architecture]
4: [Information Architecture vs Data Architecture]
5:
[The TOGAF Standard, Version 9.2 - Applying the ADM Across the Architecture Landscape]



Which of the following describes how the Enterprise Continuum is used when developing an enterprise architecture?

  1. To identify and understand business requirements
  2. To coordinate with the other management frameworks in use
  3. To describe how an architecture addresses stakeholder concerns
  4. To classify architecture and solution assets

Answer(s): D

Explanation:

The Enterprise Continuum consists of two complementary concepts: the Architecture Continuum and the Solutions Continuum. 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 situations. 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 blocks. 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 architectures.
The Enterprise Continuum is used when developing an enterprise architecture to support the following activities:
· 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


Reference:

1: The TOGAF Standard, Version 9.2 - Enterprise Continuum
2: The TOGAF Standard, Version 9.2 - Architecture Continuum
3: The TOGAF Standard, Version 9.2 - Solutions Continuum



Which section of the TOGAF template for Architecture Principles should highlight the requirements for carrying out the principle?

  1. Rationale
  2. Name
  3. Statement
  4. Implications

Answer(s): D

Explanation:

The Implications section describes the impact of adhering to the principle on the organization, the processes, the information systems, and the technology. It also identifies the changes, costs, and risks that may result from applying the principle. 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 architecture.
The other sections of the TOGAF template for Architecture Principles are:
· Name: This section provides a short and memorable name for the principle that represents its essence and purpose. The name should not mention any specific technology or solution. · Statement: This section provides a concise and formal definition of the principle that expresses the fundamental rule or constraint that the principle imposes. The statement should be clear, unambiguous, and testable.
· Rationale: This section provides the reasoning and justification for the principle, explaining why it is important and how it supports the business goals and drivers. The rationale should also link the principle to the higher-level enterprise or IT principles that it elaborates on.


Reference:

2: The TOGAF Standard, Version 9.2 - Architecture Principles
3: TOGAF 8.1.1 Online - Architecture Principles
1: Architecture Principles Template



Viewing page 3 of 22
Viewing questions 11 - 15 out of 104 questions



Post your Comments and Discuss The Open Group OGEA-10B exam prep with other Community members:

Join the OGEA-10B Discussion