Practice Free OGEA-10B Exam Online Questions
Question #21
Which of the following describes how the Enterprise Continuum is used when developing an enterprise architecture?
- A . To identify and understand business requirements
- B . To coordinate with the other management frameworks in use
- C . To describe how an architecture addresses stakeholder concerns
- D . To classify architecture and solution assets
Correct Answer: D
D
Explanation
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
References: 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
D
Explanation
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
References: 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
Question #22
Which of the following best describes the purpose of the Architecture Requirements Specification?
- A . It contains an assessment of the current architecture requirements
- B . It provides a set of statements that outline what a project must do to comply with the architecture
- C . It is sent from the sponsor and triggers the start of an architecture development cycle
- D . It defines the scope and approach to complete an architecture project
Correct Answer: B
B
Explanation
The Architecture Requirements Specification is one of the TOGAF deliverables that provides a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture12. It is a companion to the Architecture Definition Document, which provides a qualitative view of the solution and aims to communicate the intent of the architect. The Architecture Requirements
Specification provides a quantitative view of the solution, stating measurable criteria that must be met during the implementation of the architecture3. It typically forms a major component of an implementation contract or contract for more detailed Architecture Definition4.
References:
• Deliverable: Architecture Requirements Specification – The Open Group
• Architecture Requirements Specification – Visual Paradigm Community Circle
• The TOGAF Standard, Version 9.2 – Definitions – The Open Group
• The TOGAF Standard, Version 9.2 – Architecture Requirements Specification – The Open Group
B
Explanation
The Architecture Requirements Specification is one of the TOGAF deliverables that provides a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture12. It is a companion to the Architecture Definition Document, which provides a qualitative view of the solution and aims to communicate the intent of the architect. The Architecture Requirements
Specification provides a quantitative view of the solution, stating measurable criteria that must be met during the implementation of the architecture3. It typically forms a major component of an implementation contract or contract for more detailed Architecture Definition4.
References:
• Deliverable: Architecture Requirements Specification – The Open Group
• Architecture Requirements Specification – Visual Paradigm Community Circle
• The TOGAF Standard, Version 9.2 – Definitions – The Open Group
• The TOGAF Standard, Version 9.2 – Architecture Requirements Specification – The Open Group
Question #23
Which one of the following classes of information within the Architecture Repository would typically contain a list of the applications in use within the enterprise?
- A . Reference Library
- B . Architecture Metamodel
- C . Architecture Landscape
- D . Governance Log
Correct Answer: C
C
Explanation
The Architecture Landscape is a class of information within the Architecture Repository that shows an architectural view of the building blocks that are in use within the organization today (the Baseline Architecture), as well as those that are planned for the future (the Target Architecture). The Architecture Landscape typically contains a list of the applications in use within the enterprise, along with their relationships and dependencies, as well as other relevant architectural information. The Architecture Landscape helps to identify opportunities for re-use, consolidation, or retirement of existing applications, as well as gaps or overlaps in the current or future architecture.
References: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 34: Architecture Landscape: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 47: Architecture Repository
C
Explanation
The Architecture Landscape is a class of information within the Architecture Repository that shows an architectural view of the building blocks that are in use within the organization today (the Baseline Architecture), as well as those that are planned for the future (the Target Architecture). The Architecture Landscape typically contains a list of the applications in use within the enterprise, along with their relationships and dependencies, as well as other relevant architectural information. The Architecture Landscape helps to identify opportunities for re-use, consolidation, or retirement of existing applications, as well as gaps or overlaps in the current or future architecture.
References: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 34: Architecture Landscape: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 47: Architecture Repository
Question #24
Which section of the TOGAF template for Architecture Principles should highlight the business benefits of adhering to the principle?
- A . Rationale
- B . Name
- C . Implications
- D . Statement
Correct Answer: A
A
Explanation
According to the TOGAF Standard, 10th Edition, the rationale section of the architecture principles template should highlight the business benefits of adhering to the principle, as well as the business risks of not adhering to it 1. The rationale section should explain the reasoning behind the principle, and provide evidence or arguments to support it. The rationale section should also link the principle to the business drivers, goals, and objectives of the enterprise, and show how the principle contributes to the value and success of the enterprise. The other options are not correct, as they have different purposes in the architecture principles template. The name section should provide a short and memorable name for the principle, such as “Information is an Asset” or “Business Continuity” 1. The statement section should provide a concise and formal statement of the principle, such as “The enterprise’s information is recognized as a core asset, and is managed accordingly” or “The enterprise’s ability to provide critical services and products must be maintained in the event of a disaster”
A
Explanation
According to the TOGAF Standard, 10th Edition, the rationale section of the architecture principles template should highlight the business benefits of adhering to the principle, as well as the business risks of not adhering to it 1. The rationale section should explain the reasoning behind the principle, and provide evidence or arguments to support it. The rationale section should also link the principle to the business drivers, goals, and objectives of the enterprise, and show how the principle contributes to the value and success of the enterprise. The other options are not correct, as they have different purposes in the architecture principles template. The name section should provide a short and memorable name for the principle, such as “Information is an Asset” or “Business Continuity” 1. The statement section should provide a concise and formal statement of the principle, such as “The enterprise’s information is recognized as a core asset, and is managed accordingly” or “The enterprise’s ability to provide critical services and products must be maintained in the event of a disaster”
Question #25
What are the following activities part of?
• Initial risk assessment
• Risk mitigation and residual risk assessment
• Risk monitoring
- A . Risk Management
- B . Phase A
- C . Security Architecture
- D . Phase C
Correct Answer: A
A
Explanation
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.
A
Explanation
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.
Question #26
Complete the sentence. The key purpose of Gap Analysis is to _____
- A . establish quality parameters for the architecture
- B . identify potential missing or overlapping functions
- C . validate nonfunctional requirements
- D . identify commercial building blocks to be purchased
- E . determine the required service levels for the architecture
Correct Answer: B
B
Explanation
Gap Analysis is a technique that compares the Baseline Architecture and the Target Architecture to identify the differences and gaps between them. The purpose of this technique is to determine the changes and additions that are required to achieve the desired future state of the architecture. One of the main aspects of Gap Analysis is to identify the functions that are missing or overlapping in the current and future architectures, and to plan how to address them. This helps to ensure that the architecture is complete, consistent, and aligned with the business objectives and requirements3
B
Explanation
Gap Analysis is a technique that compares the Baseline Architecture and the Target Architecture to identify the differences and gaps between them. The purpose of this technique is to determine the changes and additions that are required to achieve the desired future state of the architecture. One of the main aspects of Gap Analysis is to identify the functions that are missing or overlapping in the current and future architectures, and to plan how to address them. This helps to ensure that the architecture is complete, consistent, and aligned with the business objectives and requirements3
Question #27
The_________________ensures that a project transitioning into implementation also smoothly transitions into appropriate Architecture Governance.
- A . Migration Plan
- B . Transition Plan
- C . Implementation Governance Model
- D . Implementation Strategy
Correct Answer: C
C
Explanation
The Implementation Governance Model is a framework that defines the roles, responsibilities, processes, and standards for governing the implementation of the target architecture. It ensures that a project transitioning into implementation also smoothly transitions into appropriate Architecture Governance, which is the practice of ensuring compliance with the enterprise architecture and its principles, standards, and goals. The Implementation Governance Model is part of the Implementation and Migration Plan, which is the output of Phase F: Migration Planning of the Architecture Development Method (ADM)12 References: 1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 21: Phase F: Migration Planning 2: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance
C
Explanation
The Implementation Governance Model is a framework that defines the roles, responsibilities, processes, and standards for governing the implementation of the target architecture. It ensures that a project transitioning into implementation also smoothly transitions into appropriate Architecture Governance, which is the practice of ensuring compliance with the enterprise architecture and its principles, standards, and goals. The Implementation Governance Model is part of the Implementation and Migration Plan, which is the output of Phase F: Migration Planning of the Architecture Development Method (ADM)12 References: 1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 21: Phase F: Migration Planning 2: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance
Question #28
Which of the following is a responsibility of an Architecture Board?
- A . Determining the scope of an architecture compliance review
- B . Allocating resources for architecture projects
- C . Conducting assessments of the maturity level of architecture discipline within the organization
- D . Achieving consistency between sub-architectures
Correct Answer: D
D
Explanation
One of the key responsibilities of an Architecture Board within the context of TOGAF is to achieve consistency between sub-architectures. This board is typically responsible for overseeing the development and maintenance of the enterprise architecture, ensuring that it aligns with the organization’s overall strategy and objectives. They play a critical role in ensuring that all sub-architectures (like Business Architecture, Data Architecture, Application Architecture, and Technology Architecture) work together cohesively and support the overall enterprise architecture vision and strategy.
D
Explanation
One of the key responsibilities of an Architecture Board within the context of TOGAF is to achieve consistency between sub-architectures. This board is typically responsible for overseeing the development and maintenance of the enterprise architecture, ensuring that it aligns with the organization’s overall strategy and objectives. They play a critical role in ensuring that all sub-architectures (like Business Architecture, Data Architecture, Application Architecture, and Technology Architecture) work together cohesively and support the overall enterprise architecture vision and strategy.
Question #29
Which of the following statements about architecture partitioning are correct*?
1 Partitions are used to simplify the management of the Enterprise Architecture
2 Partitions are equivalent to architecture levels
3 Partitions enable different teams to work on different element of the architecture at the same time.
4 Partitions reflect the organization’s structure
- A . 2 & 3
- B . 1 & 3
- C . 1 & 4
- D . 2 & 4
Correct Answer: B
B
Explanation
Statements 1 and 3 about architecture partitioning are correct. Architecture partitioning is the technique of dividing an architecture into smaller and more manageable parts that can be developed, maintained, and governed independently. Partitions are used to simplify the management of the Enterprise Architecture and to enable different teams to work on different elements of the architecture at the same time. Partitions are not equivalent to architecture levels, which are different degrees of abstraction or detail in an architecture. Partitions do not necessarily reflect the organization’s structure, which may change over time or differ from the architecture’s scope and boundaries.
Reference: The TOGAF® Standard | The Open Group Website, Section 2.5 Architecture Partitioning.
B
Explanation
Statements 1 and 3 about architecture partitioning are correct. Architecture partitioning is the technique of dividing an architecture into smaller and more manageable parts that can be developed, maintained, and governed independently. Partitions are used to simplify the management of the Enterprise Architecture and to enable different teams to work on different elements of the architecture at the same time. Partitions are not equivalent to architecture levels, which are different degrees of abstraction or detail in an architecture. Partitions do not necessarily reflect the organization’s structure, which may change over time or differ from the architecture’s scope and boundaries.
Reference: The TOGAF® Standard | The Open Group Website, Section 2.5 Architecture Partitioning.
Question #30
Complete the sentence. When considering agile development, Architecture to Support Portfolio will identify what products the Enterprise needs, the boundary of the products, and what constraints a product owner has; this defines the Enterprise’s
- A . risk tolerance
- B . business continuity
- C . backlog
- D . operating model
Correct Answer: C
C
Explanation
When considering agile development, Architecture to Support Portfolio will identify the necessary products for the enterprise, define their boundaries, and outline the constraints for a product owner. This process directly relates to defining the enterprise’s backlog, which in agile methodologies, is a prioritized list of work for the development team that is derived from the roadmap and its requirements.
C
Explanation
When considering agile development, Architecture to Support Portfolio will identify the necessary products for the enterprise, define their boundaries, and outline the constraints for a product owner. This process directly relates to defining the enterprise’s backlog, which in agile methodologies, is a prioritized list of work for the development team that is derived from the roadmap and its requirements.