The Open Group OGEA-10B Online Practice Questions and Exam Preparation

The Open Group OGEA-10B Online Questions & Answers

• Question 81:

  Which of the following statements about architecture partitioning is correct?

  A. Partitions are used to simplify the management of the Enterprise Architecture.
  B. Partitions are equivalent to architecture levels.
  C. Partitions reflect the organization's structure.
  D. Partitions are defined and assigned to agile Enterprise Architecture teams.
  A. Partitions are used to simplify the management of the Enterprise Architecture.

  ---

  Explanation

  Based on the web search results, architecture partitioning is a technique that divides the Enterprise Architecture into smaller and manageable segments or groups, based on various classification criteria, such as subject matter, time, maturity,

  volatility, etc.12 Architecture partitioning is used to simplify the development and management of the Enterprise Architecture, by reducing complexity, improving governance, enhancing reusability, and increasing alignment and agility12. Therefore, the statement that partitions are used to simplify the management of the Enterprise Architecture is correct.

  The other statements are incorrect because:

  -

  Partitions are not equivalent to architecture levels. Architecture levels are different layers of abstraction that describe the Enterprise Architecture from different perspectives, such as strategic, segment, and capability3. Partitions are subsets of architectures that are defined within or across the levels, based on specific criteria1. - Partitions do not necessarily reflect the organization's structure. The organization's structure is one possible criterion for partitioning the architecture, but it is not the only one. Other criteria, such as business function, product, service, geography, etc., can also be used to partition the architecture12.

  -

  Partitions are not defined and assigned to agile Enterprise Architecture teams. Agile Enterprise Architecture is an approach that applies agile principles and practices to the architecture work, such as iterative development, frequent feedback, adaptive planning, and continuous delivery4. Partitions are not a specific feature of agile Enterprise Architecture, but a general technique that can be applied to any architecture method or framework, including TOGAF12.

  References: 1: The TOGAF Standard, Version 9.2 - Architecture Partitioning 2: TOGAF?Standard -- Introduction - Architecture Partitioning 3: [The TOGAF Standard, Version 9.2 - Applying the ADM Across the Architecture Landscape] 4: TOGAF?Standard -- Introduction - Definitions - The Open Group

• Question 82:

  Complete the sentence The Architecture Landscape is divided into levels known as__________________________.

  A. Gaps Plateaus, and Target Architectures
  B. Baseline. Transition and To Be Architectures
  C. Segment Strategic and Capability Architectures
  D. Transitional Complete and incremental Architectures
  C. Segment Strategic and Capability Architectures

  ---

  Explanation

  The Architecture Landscape is divided into levels known as Segment Strategic and Capability Architectures. These levels correspond to different scopes and purposes of architectures within an enterprise. Segment Architectures are

  architectures that address specific business units, functions, or processes within an enterprise. Strategic Architectures are architectures that provide a high-level view of the enterprise's vision, goals, and direction. Capability Architectures are

  architectures that address specific business capabilities or services that span multiple segments or domains.

  The TOGAF?Standard | The Open Group Website, Section 2.4 Architecture Repository.

• Question 83:

  Please read this scenario prior to answering the question

  You are serving as the Lead Architect for an Enterprise Architecture team within a leading multinational biotechnology company. The company works in three major industries, including healthcare, crop production, and agriculture. Your team works within the healthcare division.

  The healthcare division is developing a new vaccine, and has to demonstrate its effectiveness and safety in a set of clinical trials that satisfy the regulatory requirements of the relevant health authorities. The clinical trials are undertaken by its research laboratories at multiple facilities worldwide. In addition to internal research and development activities, the healthcare division is also involved in publicly funded collaborative research projects with industrial and academic partners.

  The Enterprise Architecture team has been engaged in an architecture project to develop a secure system that will allow the healthcare researchers to share information more easily about their clinical trials, and work more collaboratively across the organization and also with its partners. This system will also connect with external partners.

  The Enterprise Architecture team uses the TOGAF ADM with extensions required to support healthcare manufacturing practices and laboratory practices. Due to the highly sensitive nature of the information that is managed, special care has been taken to ensure that each architecture domain considers the security and privacy issues that are relevant.

  The Vice President for Worldwide Clinical Research is the sponsor of the Enterprise Architecture activity. She has stated that disruptions must be minimized for the clinical trials, and that the rollout must be undertaken incrementally.

  Refer to the scenario

  You have been asked to recommend the approach to identify the work packages for an incremental rollout meeting the requirements.

  Based on the TOGAF standard which of the following is the best answer?

  A. You recommend that the Solution Building Blocks from a Consolidated Gaps, Solutions and Dependencies Matrix be grouped into a set of work packages. Using the matrix as a planning tool, regroup the work packages to account for dependencies. Sequence the work packages into the Capability Increments needed to achieve the Target Architecture, so that the implementation team can schedule the rollout one region at a time to minimize disruption. Document the work packages for the Enterprise Architecture using a Transition Architecture State Evolution Table.
  B. You recommend that a Consolidated Gaps. Solutions and Dependencies Matrix is used as a planning tool for creating work packages. For each gap classify whether the solution is either a new development, purchased solution, or based on an existing product. Group the similar solutions together to define the work packages. Regroup the work packages into a set of Capability Increments to transition to the Target Architecture considering the schedule for clinical trials, and document in an Architecture Definition Increments Table.
  C. You recommend that an Implementation Factor Catalog is drawn up to indicate actions and constraints. A Consolidated Gaps. Solutions and Dependencies Matrix should also be created. For each gap. identify a proposed solution and classify it as new development, purchased solution, or based on an existing product. Group similar activities together to form work packages. Identify dependencies between work packages factoring in the clinical trial schedules. Regroup the work packages into a set of Capability Increments scheduled into a series of Transition Architectures.
  D. You recommend that the set of required Solution Building Blocks be determined by identifying those which need to be developed and which need to be procured. Eliminate any duplicates. Group the remaining Solution Building Blocks together to create the work packages using a CRUD (create, read, update, delete) matrix. Rank the work packages and select the most cost-effective options for inclusion in a series of Transition Architectures. Schedule the roll out of the work packages to be sequential across the geographic regions.
  B. You recommend that a Consolidated Gaps. Solutions and Dependencies Matrix is used as a planning tool for creating work packages. For each gap classify whether the solution is either a new development, purchased solution, or based on an existing product. Group the similar solutions together to define the work packages. Regroup the work packages into a set of Capability Increments to transition to the Target Architecture considering the schedule for clinical trials, and document in an Architecture Definition Increments Table.

  ---

  Explanation

  A Consolidated Gaps, Solutions and Dependencies Matrix is a technique that can be used to create work packages for an incremental rollout of the architecture. A work package is a set of actions or tasks that are required to implement a

  specific part of the architecture. A work package can be associated with one or more Architecture Building Blocks (ABBs) or Solution Building Blocks (SBBs), which are reusable components of business, IT, or architectural capability. A work

  package can also be associated with one or more Capability Increments, which are defined, discrete portions of the overall capability that deliver business value. A Capability Increment can be realized by one or more Transition Architectures,

  which are intermediate states of the architecture that enable the transition from the Baseline Architecture to the Target Architecture123 The steps for creating work packages using this technique are:

  For each gap between the Baseline Architecture and the Target Architecture, identify a proposed solution and classify it as new development, purchased solution, or based on an existing product. A gap is a difference or deficiency in the

  current state of the architecture that needs to be addressed by the future state of the architecture. A solution is a way of resolving a gap by implementing one or more ABBs or SBBs.

  Group similar solutions together to define the work packages. Similar solutions are those that have common characteristics, such as functionality, technology, vendor, or location.

  Identify dependencies between work packages, such as logical, temporal, or resource dependencies. Dependencies indicate the order or priority of the work packages, and the constraints or risks that may affect their implementation. Regroup

  the work packages into a set of Capability Increments to transition to the Target Architecture. Capability Increments should be defined based on the business value, effort, and risk associated with each work package, and the schedule and

  objectives of the clinical trials. Capability Increments should also be aligned with the Architecture Vision and the Architecture Principles. Document the work packages and the Capability Increments in an Architecture Definition Increments

  Table, which shows the mapping between the work packages, the ABBs, the SBBs, and the Capability Increments. The table also shows the dependencies, assumptions, and issues related to each work package and Capability Increment.

  Therefore, the best answer is B, because it describes the approach to identify the work packages for an incremental rollout meeting the requirements, using the Consolidated Gaps, Solutions and Dependencies Matrix as a planning tool.

  References: 1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30: Gap Analysis 2: The TOGAF Standard, Version 9.2, Part IV:

  Architecture Content Framework, Chapter 36: Building Blocks 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 31: Architecture Change Management : The TOGAF Standard, Version 9.2, Part II:

  Architecture Development Method (ADM), Chapter 23: Phase E: Opportunities and Solutions : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 21: Phase F:

  Migration Planning : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 23:

  Architecture Principles

• Question 84:

  Which of the following are the four purposes that typically frame the planning horizon, depth and breadth of an Architecture Project, and the contents of the EA Repository-?

  A. General Foundational Subordinate and Superior Architecture
  B. Segment, Capability. Enterprise and End-to-end Target Architecture
  C. Avant-Garde Big-Bang, Discreet and Cohesive
  D. Strategy Portfolio Project Solution Delivery
  D. Strategy Portfolio Project Solution Delivery

  ---

  Explanation

  Strategy Portfolio Project Solution Delivery are the four purposes that typically frame the planning horizon, depth and breadth of an Architecture Project, and the contents of the EA Repository. They correspond to different levels of abstraction and granularity in the architecture development process.

  The TOGAF?Standard, Version 9.2 - The Open Group, Section 2.4 Architecture Repository.

• Question 85:

  What should be put in place through organization structures, roles, responsibilities, skills and processes to carry out architectural activity effectively?

  A. An EA Capability
  B. An Enterprise Architecture
  C. An EA framework
  D. An EA repository
  A. An EA Capability

  ---

  Explanation

  An EA Capability is the ability of an organization to perform enterprise architecture effectively and efficiently. It involves establishing and maintaining the appropriate organization structures, roles, responsibilities, skills, processes, tools, and

  governance mechanisms to support the development and use of enterprise architecture. An EA Capability enables the organization to align its business and IT strategies, deliver value from its investments, manage change and complexity,

  and improve its performance and agility12

  References: 1: The TOGAF Standard, Version 9.2, Part VI:

  Architecture Capability Framework, Chapter 44: Introduction 2: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 45: Establishing and Maintaining an Enterprise Architecture Capability

• Question 86:

  Consider the following descriptions of deliverables consumed and produced across the TOGAF ADM cycle.

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

  2.The joint agreements between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture.

  3.A document that is sent from the sponsoring organization to the architecture organization to trigger the start of an architecture development cycle

  4.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
  A. 1 Architecture Principles -2 Architecture Contracts - 3 Request for Architecture Work - 4 Architecture Requirements Specification

  ---

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

  Complete the sentence The TOGAF standard covers the development of four architecture domains. Business. Data, Technology and__________________.

  A. Segment
  B. Transition
  C. Capability
  D. Application
  D. Application

  ---

  Explanation

  The TOGAF standard covers the development of four architecture domains:

  Business, Data, Technology and Application. These domains represent different aspects of an enterprise's architecture and provide a consistent way of describing, analyzing, and designing them.

  The TOGAF?Standard | The

  Open Group Website, Section 2.2 Architecture Development Method (ADM).

• Question 88:

  Which of the following describes the practice by which the enterprise architecture is managed and controlled at an enterprise-wide level?

  A. Corporate governance
  B. Architecture governance
  C. IT governance
  D. Technology governance
  B. Architecture governance

  ---

  Explanation

  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.

  References: 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.

• Question 89:

  Refer to the table below:

  

  Which ADM Phase does this describe?

  A. Phase E
  B. Phase G
  C. Phase A
  D. Phase F
  B. Phase G

  ---

  Explanation

  The table describes the output, outcome, and essential knowledge of an ADM phase that oversees the implementation of changes necessary to reach the adjusted target state. This corresponds to Phase G, also known as Implementation Governance, which ensures that the architecture defined in earlier phases is realized, and it oversees the development and implementation of projects to align with this architecture. The essential knowledge required during this phase includes understanding constraints on the implementation team and adjusting stakeholder priority and preference in response to success, value, effort, and risk of change.

  References: TOGAF Version 9.1 - 1

• Question 90:

  Consider the following statement.

  According to the TOGAF standard, a governed approach of a particular deliverable will ensure adherence to the principles, standards, and requirements of the existing or developing architectures.

  Which deliverable does this refer to?

  A. The Architecture Vision
  B. The Statement of Architecture Work
  C. An Architecture Contract
  D. The Architecture Definition Document
  C. An Architecture Contract

  ---

  Explanation

  According to the TOGAF Standard, 10th Edition, an architecture contract is "a formal agreement between a service provider and a service consumer that defines the mutual commitments and expectations for the delivery of an architecture" 1. An architecture contract is a governed approach of a particular deliverable that will ensure adherence to the principles, standards, and requirements of the existing or developing architectures, as it specifies the roles, responsibilities, deliverables, quality criteria, and acceptance criteria for the architecture work 1. The other options are not correct, as they are not governed approaches of a particular deliverable, but rather different types of deliverables within the architecture development process. An architecture vision is "a high-level, aspirational view of the target architecture" 1. A statement of architecture work is "a document that defines the scope and approach that will be used to complete an architecture project" 1. An architecture definition document is "a document that describes the baseline and target architectures for one or more domains" 1.

  References: 1: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions.