The Open Group OGEA-101 Online Practice Questions and Exam Preparation

The Open Group OGEA-101 Online Questions & Answers

• Question 11:

  In which phase of the ADM cycle do building blocks become implementation-specific?

  A. Phase B
  B. Phase C
  C. Phase D
  D. Phase E
  D. Phase E

  ---

  Explanation

  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 identifiesthe delivery vehicles, such as projects, programs, or portfolios, that will realize the building blocks

• Question 12:

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

  A. Reference Library
  B. Architecture Capability
  C. Architecture Requirements Repository
  D. Governance Log
  C. Architecture Requirements Repository

  ---

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

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

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

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

• Question 13:

  Which statement about Requirements Management is most correct?

  A. The purpose of Requirements Management is to process change requests
  B. Stakeholder requirements are captured once in Phase A and managed throughout the ADM cycle
  C. Requirements Management is a step of all ADM Phases
  D. Requirements Management and stakeholder engagement are placed at the center of architecture development
  D. Requirements Management and stakeholder engagement are placed at the center of architecture development

  ---

  Explanation

  This statement about Requirements Management is most correct because it reflects the central role of Requirements Management and stakeholder engagement in the ADM cycle. Requirements Management is not a step of all ADM Phases, but rather an ongoing process that ensures that all relevant requirements are elicited, analyzed, prioritized, and addressed throughout the architecture development and transition. Stakeholder engagement is also a continuous activity that involves identifying, communicating, and managing stakeholder expectations and concerns.

  The TOGAF?Standard | The Open Group Website, Section 3.1 Introduction to the ADM.

• Question 14:

  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
  C. backlog

  ---

  Explanation

  When considering agile development,Architecture to Support Portfoliowill 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'sbacklog, which in agile methodologies, is a prioritized list of work for the development team that is derived from the roadmap and its requirements.

• Question 15:

  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
  C. Architecture Landscape

  ---

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

  Consider the following chart: Which important concept for Enterprise Architecture Practitioners does it illustrate?

  

  A. Enterprise Architects must use Gantt charts to communicate with Stakeholders.
  B. An Enterprise Architecture must be developed in phases with a limited fixed duration.
  C. ADM phases must be run in a sequenced approach to produce the Architecture.
  D. ADM phases must be run simultaneously until the relevant information has been produced.
  C. ADM phases must be run in a sequenced approach to produce the Architecture.

  ---

  Explanation

  The chart shown is a Gantt chart, which is commonly used for project management to illustrate a project schedule. In the context of TOGAF (The Open Group Architecture Framework), which is a framework for enterprise architecture, this Gantt chart is demonstrating the sequenced approach to the Architecture Development Method (ADM). The ADM is the core process of TOGAF which provides a tested and repeatable process for developing architectures. The ADM is described as being iterative, over the whole process, between phases, and within phases. For each iteration of the ADM, a fresh decision must be taken about each of the parameters (scope, granularity, time period, and architecture assets). The ADM consists of a number of phases that have to be followed in sequence: Preliminary Phase: Framework and principles Phase A: Architecture Vision Phase B: Business Architecture Phase C: Information Systems Architectures, including Data and Application Architectures Phase D: Technology Architecture Phase E: Opportunities and Solutions Phase F: Migration Planning Phase G: Implementation Governance Phase H: Architecture Change Management Requirements Management Each phase is dependent on the outputs of the previous phase and the Requirements Management phase runs throughout. The Gantt chart clearly shows the dependency and sequence in which these phases occur, implying that a structured approach is followed to produce the enterprise architecture.

  References: The TOGAF Standard, Version 9.2, a standard of The Open Group The TOGAF documentation available at https://publications.opengroup.org/standards/architecture andhttps://publications.opengroup.org/guides/architecture

• Question 17:

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

• Question 18:

  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
  B. identify potential missing or overlapping functions

  ---

  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 aremissing 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 requirements

• Question 19:

  Which of the following best describes the need for the ADM process to be governed?

  A. To enable development of reference architectures
  B. To verify that the method is being applied correctly
  C. To enable a fast response to market changes
  D. To permit the architecture domains to be integrated
  B. To verify that the method is being applied correctly

  ---

  Explanation

  According to the TOGAF standard, the need for the ADM process to be governed is to ensure that the architecture development and implementation activities are conducted in a consistent, coherent, and compliant manner1. Governance

  provides the means to verify that the method is being applied correctly and effectively, and that the architecture deliverables and artifacts meet the quality and standards criteria1. Governance also enables the management of risks, issues,

  changes, and dependencies that may arise during the ADM process.

  Some of the benefits of governing the ADM process are:

  1. Improved alignment of the architecture with the business strategy and objectives

  2. Inhanced stakeholder engagement and communication

  3. Increased reuse and integration of architecture assets and resources

  4. Reduced complexity and duplication of architecture efforts

  5. Increased agility and adaptability of the architecture to changing needs and requirements

  6. Improved compliance and auditability of the architecture outcomes and outputs

  References: 1: Architecture Governance 2: Architecture Governance Benefits

• Question 20:

  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
  A. Rationale

  ---

  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 sectionshould 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" 1. The implications section should identify the impact of the principle on the enterprise, such as the changes, costs, benefits, and risks that may result from applying or violating the principle 1.

  References: 1: TOGAF Standard, 10th Edition, Part III: ADM Guidelines and Techniques, Chapter 23: Architecture Principles, Section 23.3 Developing Architecture Principles.