Practice Free OGEA-10B Exam Online Questions
Question #31
Consider the following descriptions of deliverables consumed and produced across the TOGAF ADM cycle.
– General rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organization sets about fulfilling its mission
– The joint agreements between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture.
– A document that is sent from the sponsoring organization to the architecture organization to trigger the start of an architecture development cycle
– A set of quantitative statements that outline what an implementation project must do in order to comply with the architecture.
Which deliverables match these descriptions?
- A . 1 Architecture Principles -2 Architecture Contracts – 3 Request for Architecture Work – 4 Architecture Requirements Specification
- B . 1 Architecture Contracts – 2 Architecture Requirements Specification – 3 Architecture Vision – 4 Architecture Principles
- C . 1 Architecture Requirements Specification -2 Architecture Principles – 3 Architecture Vision – 4 Architecture Contracts
- D . 1 Architecture Principles -2 Architecture Contracts – 3 Architecture Requirements Specification-4 Request for Architecture Work
Correct Answer: A
A
Explanation
According to the TOGAF standard, the deliverables that match the descriptions are as follows:
1 Architecture Principles: These are general rules and guidelines, intended to be enduring and seldom
amended, that inform and support the way in which an organization sets about fulfilling its
mission1. They reflect a level of consensus among the various elements of the enterprise, and form the
basis for making future IT decisions1.
2 Architecture Contracts: These are the joint agreements between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture2. They are used to ensure that the architecture is implemented and governed according to the agreed-upon specifications and standards2.
3 Request for Architecture Work: This is a document that is sent from the sponsoring organization to the architecture organization to trigger the start of an architecture development cycle3. It defines the scope, schedule, budget, deliverables, and stakeholders of the architecture project3.
4 Architecture Requirements Specification: This is a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture4. It defines the requirements for each architecture domain, as well as the relationships and dependencies among them4.
References: 1: Architecture Principles 2: Architecture Contracts 3: Request for Architecture Work 4: Architecture Requirements Specification
A
Explanation
According to the TOGAF standard, the deliverables that match the descriptions are as follows:
1 Architecture Principles: These are general rules and guidelines, intended to be enduring and seldom
amended, that inform and support the way in which an organization sets about fulfilling its
mission1. They reflect a level of consensus among the various elements of the enterprise, and form the
basis for making future IT decisions1.
2 Architecture Contracts: These are the joint agreements between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture2. They are used to ensure that the architecture is implemented and governed according to the agreed-upon specifications and standards2.
3 Request for Architecture Work: This is a document that is sent from the sponsoring organization to the architecture organization to trigger the start of an architecture development cycle3. It defines the scope, schedule, budget, deliverables, and stakeholders of the architecture project3.
4 Architecture Requirements Specification: This is a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture4. It defines the requirements for each architecture domain, as well as the relationships and dependencies among them4.
References: 1: Architecture Principles 2: Architecture Contracts 3: Request for Architecture Work 4: Architecture Requirements Specification
Question #32
Digital Transformation and operations will be more effective and efficient.
Which statements highlight the value and necessity for Architecture Governance to be adopted within organizations?
- A . 1 & 4
- B . 1 & 3
- C . 2 & 4
- D . 2& 3
Correct Answer: B
B
Explanation
Statements 1 and 3 highlight the value and necessity for Architecture Governance to be adopted within organizations. Architecture Governance is the practice and orientation by which Enterprise Architectures and other architectures are managed and controlled at an enterprise-wide level12. It ensures that architectural decisions are aligned with the organization’s strategy, objectives, and standards. Architecture Governance also involves establishing and maintaining processes, decision-making, and mechanisms to avoid or minimize potential conflicts of interest, such as between different stakeholders, business units, or projects34. Moreover, Architecture Governance requires transparency and accountability for all actions implemented and their decision support, so that they can be inspected and evaluated by authorized parties, such as auditors, regulators, or customers5.
References:
• The TOGAF Standard, Version 9.2 – Architecture Governance – The Open Group
• Architecture Governance – The Open Group
• Tutorial: Governance in TOGAF’s Architecture Development Method (ADM)
• Architecture Governance in TOGAF: Ensuring Effective Management and Compliance
• The TOGAF Standard, Version 9.2 – Definitions – The Open Group
• [Architecture Governance in TOGAF: Ensuring Alignment and Control]
B
Explanation
Statements 1 and 3 highlight the value and necessity for Architecture Governance to be adopted within organizations. Architecture Governance is the practice and orientation by which Enterprise Architectures and other architectures are managed and controlled at an enterprise-wide level12. It ensures that architectural decisions are aligned with the organization’s strategy, objectives, and standards. Architecture Governance also involves establishing and maintaining processes, decision-making, and mechanisms to avoid or minimize potential conflicts of interest, such as between different stakeholders, business units, or projects34. Moreover, Architecture Governance requires transparency and accountability for all actions implemented and their decision support, so that they can be inspected and evaluated by authorized parties, such as auditors, regulators, or customers5.
References:
• The TOGAF Standard, Version 9.2 – Architecture Governance – The Open Group
• Architecture Governance – The Open Group
• Tutorial: Governance in TOGAF’s Architecture Development Method (ADM)
• Architecture Governance in TOGAF: Ensuring Effective Management and Compliance
• The TOGAF Standard, Version 9.2 – Definitions – The Open Group
• [Architecture Governance in TOGAF: Ensuring Alignment and Control]
Question #33
Which of the following best describes a purpose of the Gap Analysis technique?
- A . To validate non-functional requirements
- B . To establish quality metrics for the architecture
- C . To determine service levels for the architecture
- D . To identify missing functions
Correct Answer: D
D
Explanation
Gap analysis is a technique that is used to validate an architecture by highlighting the shortfall between the Baseline Architecture and the Target Architecture. One of the purposes of gap analysis is to identify missing functions that are either deliberately omitted, accidentally left out, or not yet defined in the Target Architecture. Missing functions are marked as gaps that need to be filled by developing or procuring the building blocks.
D
Explanation
Gap analysis is a technique that is used to validate an architecture by highlighting the shortfall between the Baseline Architecture and the Target Architecture. One of the purposes of gap analysis is to identify missing functions that are either deliberately omitted, accidentally left out, or not yet defined in the Target Architecture. Missing functions are marked as gaps that need to be filled by developing or procuring the building blocks.
Question #33
Which of the following best describes a purpose of the Gap Analysis technique?
- A . To validate non-functional requirements
- B . To establish quality metrics for the architecture
- C . To determine service levels for the architecture
- D . To identify missing functions
Correct Answer: D
D
Explanation
Gap analysis is a technique that is used to validate an architecture by highlighting the shortfall between the Baseline Architecture and the Target Architecture. One of the purposes of gap analysis is to identify missing functions that are either deliberately omitted, accidentally left out, or not yet defined in the Target Architecture. Missing functions are marked as gaps that need to be filled by developing or procuring the building blocks.
D
Explanation
Gap analysis is a technique that is used to validate an architecture by highlighting the shortfall between the Baseline Architecture and the Target Architecture. One of the purposes of gap analysis is to identify missing functions that are either deliberately omitted, accidentally left out, or not yet defined in the Target Architecture. Missing functions are marked as gaps that need to be filled by developing or procuring the building blocks.
Question #35
Consider the following ADM phases objectives.
Which phase does each objective match?
- A . 1F-2G-3G-4H
- B . 1H-2F-3F-4G
- C . 1F-2G-3H-4H
- D . 1G-2H-3H-4F
Correct Answer: B
B
Explanation
According to the TOGAF Standard, Version 9.2, the ADM phases and their objectives are as follows1:
Preliminary Phase: To prepare and initiate the architecture development cycle, including defining the architecture framework, principles, and governance.
Phase A: Architecture Vision: To define the scope, vision, and stakeholders of the architecture initiative, and to obtain approval to proceed.
Phase B: Business Architecture: To describe the baseline and target business architecture, and to identify the gaps between them.
Phase C: Information Systems Architectures: To describe the baseline and target data and application architectures, and to identify the gaps between them.
Phase D: Technology Architecture: To describe the baseline and target technology architecture, and to identify the gaps between them.
Phase E: Opportunities and Solutions: To identify and evaluate the opportunities and solutions for implementing the target architecture, and to define the work packages and transition architectures.
Phase F: Migration Planning: To finalize the implementation and migration plan, and to ensure alignment with the enterprise portfolio and project management.
Phase G: Implementation Governance: To provide architecture oversight and guidance for the implementation projects, and to manage any architecture change requests.
Phase H: Architecture Change Management: To monitor the changes in the business and technology environment, and to assess the impact and performance of the architecture.
Requirements Management: To manage the architecture requirements throughout the ADM cycle, and to ensure alignment with the business requirements.
Based on the above definitions, we can match each objective with the corresponding phase as follows:
Objective 1: Ensure that the business value and cost of work packages and transition architectures
is understood by key stakeholders. This objective is achieved in Phase H: Architecture Change Management, where the value realization and cost-benefit analysis of the architecture are performed2.
Objective 2: Ensure conformance with the Target Architecture by implementation projects. This objective is achieved in Phase F: Migration Planning, where the conformance requirements and criteria for the implementation projects are defined3.
Objective 3: Ensure that the architecture development cycle is maintained. This objective is achieved in Phase F: Migration Planning, where the architecture roadmap and iteration cycle are maintained3.
Objective 4: Ensure that the Architecture Governance Framework is executed. This objective is achieved in Phase G: Implementation Governance, where the architecture governance processes and procedures are applied to the implementation projects4.
References:
1: The TOGAF Standard, Version 9.2, Chapter 5: Architecture Development Method (ADM)
2: The TOGAF Standard, Version 9.2, Chapter 21: Architecture Change Management
3: The TOGAF Standard, Version 9.2, Chapter 20: Migration Planning
4: The TOGAF Standard, Version 9.2, Chapter 19: Implementation Governance
B
Explanation
According to the TOGAF Standard, Version 9.2, the ADM phases and their objectives are as follows1:
Preliminary Phase: To prepare and initiate the architecture development cycle, including defining the architecture framework, principles, and governance.
Phase A: Architecture Vision: To define the scope, vision, and stakeholders of the architecture initiative, and to obtain approval to proceed.
Phase B: Business Architecture: To describe the baseline and target business architecture, and to identify the gaps between them.
Phase C: Information Systems Architectures: To describe the baseline and target data and application architectures, and to identify the gaps between them.
Phase D: Technology Architecture: To describe the baseline and target technology architecture, and to identify the gaps between them.
Phase E: Opportunities and Solutions: To identify and evaluate the opportunities and solutions for implementing the target architecture, and to define the work packages and transition architectures.
Phase F: Migration Planning: To finalize the implementation and migration plan, and to ensure alignment with the enterprise portfolio and project management.
Phase G: Implementation Governance: To provide architecture oversight and guidance for the implementation projects, and to manage any architecture change requests.
Phase H: Architecture Change Management: To monitor the changes in the business and technology environment, and to assess the impact and performance of the architecture.
Requirements Management: To manage the architecture requirements throughout the ADM cycle, and to ensure alignment with the business requirements.
Based on the above definitions, we can match each objective with the corresponding phase as follows:
Objective 1: Ensure that the business value and cost of work packages and transition architectures
is understood by key stakeholders. This objective is achieved in Phase H: Architecture Change Management, where the value realization and cost-benefit analysis of the architecture are performed2.
Objective 2: Ensure conformance with the Target Architecture by implementation projects. This objective is achieved in Phase F: Migration Planning, where the conformance requirements and criteria for the implementation projects are defined3.
Objective 3: Ensure that the architecture development cycle is maintained. This objective is achieved in Phase F: Migration Planning, where the architecture roadmap and iteration cycle are maintained3.
Objective 4: Ensure that the Architecture Governance Framework is executed. This objective is achieved in Phase G: Implementation Governance, where the architecture governance processes and procedures are applied to the implementation projects4.
References:
1: The TOGAF Standard, Version 9.2, Chapter 5: Architecture Development Method (ADM)
2: The TOGAF Standard, Version 9.2, Chapter 21: Architecture Change Management
3: The TOGAF Standard, Version 9.2, Chapter 20: Migration Planning
4: The TOGAF Standard, Version 9.2, Chapter 19: Implementation Governance
Question #36
Partnerships and alliances of businesses working together, such as a consortium or supply chain
What are those examples of according to the TOGAF Standard?
- A . Enterprises
- B . Organizations
- C . Business Units
- D . Architectures Scopes
Correct Answer: D
D
Explanation
According to the TOGAF standard, the two statements provided refer to different scopes within which architecture can be developed:
– Groups of countries, governments, or governmental organizations working together typically align with broader, often international, scopes of architecture that transcend individual enterprise boundaries.
– Partnerships and alliances of businesses working together, such as a consortium or supply chain, refer to collaborative efforts that can define architecture at a scope involving multiple enterprises.
In both cases, the term "Architectures Scopes" is appropriate because it reflects the varying levels and contexts in which architectures can be defined, ranging from single business units to collaborative inter-organizational efforts.
D
Explanation
According to the TOGAF standard, the two statements provided refer to different scopes within which architecture can be developed:
– Groups of countries, governments, or governmental organizations working together typically align with broader, often international, scopes of architecture that transcend individual enterprise boundaries.
– Partnerships and alliances of businesses working together, such as a consortium or supply chain, refer to collaborative efforts that can define architecture at a scope involving multiple enterprises.
In both cases, the term "Architectures Scopes" is appropriate because it reflects the varying levels and contexts in which architectures can be defined, ranging from single business units to collaborative inter-organizational efforts.
Question #36
Partnerships and alliances of businesses working together, such as a consortium or supply chain
What are those examples of according to the TOGAF Standard?
- A . Enterprises
- B . Organizations
- C . Business Units
- D . Architectures Scopes
Correct Answer: D
D
Explanation
According to the TOGAF standard, the two statements provided refer to different scopes within which architecture can be developed:
– Groups of countries, governments, or governmental organizations working together typically align with broader, often international, scopes of architecture that transcend individual enterprise boundaries.
– Partnerships and alliances of businesses working together, such as a consortium or supply chain, refer to collaborative efforts that can define architecture at a scope involving multiple enterprises.
In both cases, the term "Architectures Scopes" is appropriate because it reflects the varying levels and contexts in which architectures can be defined, ranging from single business units to collaborative inter-organizational efforts.
D
Explanation
According to the TOGAF standard, the two statements provided refer to different scopes within which architecture can be developed:
– Groups of countries, governments, or governmental organizations working together typically align with broader, often international, scopes of architecture that transcend individual enterprise boundaries.
– Partnerships and alliances of businesses working together, such as a consortium or supply chain, refer to collaborative efforts that can define architecture at a scope involving multiple enterprises.
In both cases, the term "Architectures Scopes" is appropriate because it reflects the varying levels and contexts in which architectures can be defined, ranging from single business units to collaborative inter-organizational efforts.