The Open Group OGEA-101 Practice Test - Questions Answers, Page 9

According to the TOGAF Standard, 10th Edition, a stakeholder is ''an individual with an interest in a system'' 1. A stakeholder can be anyone who is affected by the system, or who can influence or be influenced by the system. Stakeholders can have different roles, perspectives, and concerns regarding the system, and they can be internal or external to the organization. Stakeholder management is a technique that helps to identify, analyze, and engage the stakeholders of an architecture project, and to address their needs and expectations 2. The other options are not correct, as they are not the term used by the TOGAF Standard to describe an individual with an interest in a system. A consumer is ''an individual or group that uses a product or service'' 1. A lead architect is ''an individual who is responsible for leading the development of an architecture'' 1. A sponsor is ''an individual who provides funding and support for an architecture project'' 1.

Reference: 1: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions. 2: TOGAF Standard, 10th Edition, Part III: ADM Guidelines and Techniques, Chapter 24: Stakeholder Management.

According to the TOGAF Standard, 10th Edition, architecture governance is ''the practice by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level'' 1. Architecture governance ensures that the architecture development and implementation are aligned with the strategic objectives, principles, standards, and requirements of the enterprise, and that they deliver the expected value and outcomes. Architecture governance also involves establishing and maintaining the architecture framework, repository, board, contracts, and compliance reviews 1. The other options are not correct, as they are not the term used by the TOGAF Standard to describe the practice by which the enterprise architecture is managed and controlled at an enterprise-wide level. Corporate governance is ''the system by which an organization is directed and controlled'' 2, and it covers aspects such as leadership, strategy, performance, accountability, and ethics. IT governance is ''the system by which the current and future use of IT is directed and controlled'' 2, and it covers aspects such as IT strategy, policies, standards, and services. Technology governance is ''the system by which the technology decisions and investments are directed and controlled'' 3, and it covers aspects such as technology selection, acquisition, deployment, and maintenance.

Reference: 1: TOGAF Standard, 10th Edition, Part VI: Architecture Governance, Chapter 44: Introduction. 2: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions. 3: TOGAF Series Guide: Using the TOGAF Framework to Define and Govern Service-Oriented Architectures, Part II: Using the TOGAF Framework to Define and Govern Service-Oriented Architectures, Chapter 5: Technology Governance.

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.

The illustration shows an architecture development cycle based on the TOGAF ADM (Architecture Development Method), which is a method for developing and managing an enterprise architecture1.

The ADM consists of nine phases, each with a specific purpose and output.The phases are1:

oPreliminary Phase: To prepare and initiate the architecture development cycle, including defining the architecture framework, principles, and governance.

oPhase A: Architecture Vision: To define the scope, vision, and stakeholders of the architecture initiative, and to obtain approval to proceed.

oPhase B: Business Architecture: To describe the baseline and target business architecture, and to identify the gaps between them.

oPhase C: Information Systems Architectures: To describe the baseline and target data and application architectures, and to identify the gaps between them.

oPhase D: Technology Architecture: To describe the baseline and target technology architecture, and to identify the gaps between them.

oPhase 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.

oPhase F: Migration Planning: To finalize the implementation and migration plan, and to ensure alignment with the enterprise portfolio and project management.

oPhase G: Implementation Governance: To provide architecture oversight and guidance for the implementation projects, and to manage any architecture change requests.

oPhase H: Architecture Change Management: To monitor the changes in the business and technology environment, and to assess the impact and performance of the architecture.

In addition to these phases, there is a central process called Requirements Management, which is labeled as item 1 in the illustration.This process operates throughout the ADM cycle, and its purpose is to manage the architecture requirements throughout the architecture development, ensuring that they are aligned with the business requirements and the stakeholder concerns2.

Therefore, the description that matches the phase of the ADM labeled as item 1 is C. Operates the process of managing architecture requirements.

1: The TOGAF Standard, Version 9.2, Chapter 5: Architecture Development Method (ADM)

2: The TOGAF Standard, Version 9.2, Chapter 17: Requirements Management

The purpose of the Architecture Roadmap is to provide a high-level view of how the Baseline Architecture will transition to the Target Architecture over time. It lists work packages on a timeline showing progress towards the Target Architecture, as well as dependencies, risks, and benefits. The Architecture Roadmap forms part of the Implementation and Migration Plan and guides the execution of the architecture projects.

Reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap20.html

The Request for Architecture Work is a deliverable that is sent from the sponsor and triggers the start of an architecture development cycle. It defines the scope, budget, schedule, and deliverables for a specific architecture project. The Statement of Architecture Work is a deliverable that is produced by the architect and defines the approach and resources needed to complete an architecture project. It forms the basis of a contractual agreement between the sponsor and the architecture organization. The Architecture Principles are a deliverable that is produced by the architect and defines the general rules and guidelines for the architecture work. They reflect the business principles, business goals, and business drivers of the organization. The Architecture Requirements Specification is a deliverable that is produced by the architect and defines the requirements that govern the architecture work.It covers both functional and non-functional requirements as well as constraints and assumptions.

An Architecture Board is an executive-level group responsible for the review and maintenance of the strategic architecture and all of its sub-architectures1.It is a key element in a successful Architecture Governance strategy2.

An Architecture Board is typically made responsible, and accountable, for achieving some or all of the following goals2:

oProviding the basis for all decision-making with regard to the architectures

oConsistency between sub-architectures

oEstablishing targets for re-use of components

oFlexibility of the Enterprise Architecture: To meet changing business needs To leverage new technologies

oEnforcement of Architecture Compliance

oImproving the maturity level of architecture discipline within the organization

oEnsuring that the discipline of architecture-based development is adopted

oSupporting a visible escalation capability for out-of-bounds decisions

Therefore, the correct answer is option D, which captures one of the goals of an Architecture Board as stated in the TOGAF Standard, Version 9.22.

Option A is incorrect, because conducting assessments of the maturity level of architecture discipline within the organization is not a direct responsibility of an Architecture Board, but rather a part of the Architecture Capability Framework3.

Option B is incorrect, because allocating resources for architecture projects is not a direct responsibility of an Architecture Board, but rather a part of the Architecture Governance Framework4.

Option C is incorrect, because creating the Statement of Architecture Work is not a direct responsibility of an Architecture Board, but rather a part of the Architecture Development Method5.Reference:

1: Architecture Board - The Open Group3

2: TOGAF Standard, Version 9.2 - Part VI: Architecture Governance Framework - Architecture Board

3: TOGAF Standard, Version 9.2 - Part VI: Architecture Governance Framework - Architecture Capability Framework

4: TOGAF Standard, Version 9.2 - Part VI: Architecture Governance Framework - Architecture Governance Framework

5: TOGAF Standard, Version 9.2 - Part II: Architecture Development Method - Phase A: Architecture Vision

Building blocks are reusable components of business, IT, or architectural capability that can be combined to deliver architectures and solutions. Building blocks can be defined at various levels of detail, depending on the stage of architecture development. In the earlier phases of the ADM cycle (A to D), building blocks are defined in generic terms, such as logical or physical, to provide a high-level view of the architecture. In Phase E: Opportunities and Solutions, building blocks become implementation-specific, meaning that they are linked to specific products, standards, technologies, and vendors that are available in the market.This phase also identifies the delivery vehicles, such as projects, programs, or portfolios, that will realize the building blocks12Reference:1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 23: Phase E: Opportunities and Solutions2: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 36: Building Blocks

Business scenarios are a technique for capturing, clarifying, and communicating the functional and non-functional requirements of a system. Business scenarios describe the business environment, the actors involved, the desired outcomes, and the processes or rules that govern the behavior of the system. Business scenarios are useful for ensuring that the architecture addresses the real needs and concerns of the stakeholders, and for validating and testing the architecture against expected situations.Business scenarios are developed in Phase A: Architecture Vision of the ADM cycle, and refined and updated throughout the other phases3Reference:3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 26: Business Scenarios : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision