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

A business scenario describes business and technology environment in which those problems occur. It provides a realistic context for identifying and addressing business problems and opportunities, as well as their impact on the enterprise's architecture.

Reference: The TOGAF Standard | The Open Group Website, Section 3.3.1 Business Scenarios.

Phase B of the ADM cycle is the Business Architecture phase. It describes the development of a Business Architecture to support an agreed Architecture Vision. The objectives of this phase are to describe the baseline and target Business Architecture, identify candidate Architecture Roadmap components based on gaps between the baseline and target, and determine whether an incremental approach is required.

Reference: The TOGAF Standard | The Open Group Website, Section 3.2.2 Phase B: Business Architecture.

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.

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

According to the TOGAF Standard, Version 9.2, the ADM phases and their objectives are as follows1:

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.

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

oObjective 1: Ensure that the business value and cost of work packages and transition architectures is understood by key stakeholders.This objective is achieved inPhase H: Architecture Change Management, where the value realization and cost-benefit analysis of the architecture are performed2.

oObjective 2: Ensure conformance with the Target Architecture by implementation projects.This objective is achieved inPhase F: Migration Planning, where the conformance requirements and criteria for the implementation projects are defined3.

oObjective 3: Ensure that the architecture development cycle is maintained.This objective is achieved inPhase F: Migration Planning, where the architecture roadmap and iteration cycle are maintained3.

oObjective 4: Ensure that the Architecture Governance Framework is executed.This objective is achieved inPhase G: Implementation Governance, where the architecture governance processes and procedures are applied to the implementation projects4.

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

Enterprises are examples of the scope of an architecture according to the TOGAF Standard. An enterprise is defined as any collection of organizations that has a common set of goals and/or a single bottom line. Enterprises can be whole corporations or divisions of a corporation, government agencies or single government departments, partnerships and alliances of businesses working together, etc.

Reference: The TOGAF Standard | The Open Group Website, Section 2.1 Core Concepts.

When considering agile development, Architecture to Support Project will identify what products the enterprise needs, the boundary of the products, and what constraints a product owner has. This defines the enterprise's backlog. A backlog is a list of features or tasks that need to be done to deliver a product or service. It is prioritized by the product owner based on the value and urgency of each item.

Reference: The TOGAF Standard | The Open Group Website, Section 3.3.5 Architecture to Support Project.

Ensuring compliance with internal and external standards and regulatory obligations is one of the activities included as part of Architecture Governance. Architecture Governance is the practice and orientation by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level. It involves establishing processes, roles, responsibilities, policies, and standards to ensure that architectures are aligned with the enterprise's strategy and objectives, and meet the quality and performance requirements.

Reference: The TOGAF Standard | The Open Group Website, Section 3.3.6 Architecture Governance.

The Enterprise Continuum provides methods for classifying architecture artifacts as they evolve from generic architectures to Organization-Specific Architectures. Generic architectures are architectures that have been developed for use across a wide range of enterprises with similar characteristics. They provide common models, functions, and services that can be reused and adapted for specific purposes. Organization-Specific Architectures are architectures that have been tailored to meet the needs and requirements of a particular enterprise or a major organizational unit within an enterprise. They reflect the unique vision, goals, culture, structure, processes, systems, and technologies of that enterprise or unit.

Reference: The TOGAF Standard | The Open Group Website, Section 2.3 Enterprise Continuum.

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.