OGEA-101 TOGAF Enterprise Architecture Part 1 Exam (English) Questions and Answers

Statements 1 and 3 about architecture partitioning are correct. Architecture partitioning is the technique of dividing an architecture into smaller and more manageable parts that can be developed, maintained, and governed independently. Partitions are used to simplify the management of the Enterprise Architecture and to enable different teams to work on different elements of the architecture at the same time. Partitions are not equivalent to architecture levels, which are different degrees of abstraction or detail in an architecture. Partitions do not necessarily reflect the organization’s structure, which may change over time or differ from the architecture’s scope and boundaries. Reference: The TOGAF® Standard | The Open Group Website, Section 2.5 Architecture Partitioning.

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.

Architecture Principles are general rules and guidelines that inform and support the way in which an organization sets about fulfilling its mission. They reflect a level of consensus among the various elements of the enterprise, and form the basis for making future IT decisions. One of the purposes of Architecture Principles is to establish a common understanding of how to control the business in pursuit of strategic objectives, by providing a framework for evaluating and agreeing on the changes that affect the enterprise’s architecture3 References: 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 23: Architecture Principles : The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 31: Architecture Principles

An Enterprise Architecture Capability is the ability of the organization to perform effective and efficient architecture work, including the definition, governance, and management of its architectures2. The Preliminary Phase involves the following activities1:

•Reviewing the organizational context, scope, and drivers for conducting Enterprise Architecture

•Establishing the Architecture Capability desired by the organization, including the maturity level, roles, responsibilities, processes, and tools

•Defining and establishing the Organizational Model for Enterprise Architecture, which describes how the architecture function is organized and integrated within the enterprise

•Defining and establishing the Architecture Governance framework, which provides the mechanisms for ensuring the quality, consistency, and compliance of the architecture work

•Selecting and implementing the tools that support the Architecture Capability, such as repositories, modeling tools, and communication tools

•Defining the Architecture Principles that will guide and constrain the architecture work, based on the business principles, goals, and drivers of the organization

•Defining the Organization-Specific Architecture Framework, which is an adaptation of the generic TOGAF ADM to suit the specific requirements, standards, and practices of the organization

The Preliminary Phase is essential for preparing the organization for the successful development and implementation of its architectures, as well as for ensuring the alignment of the architecture work with the business strategy and objectives1.

References: 1: Preliminary Phase 2: Enterprise Architecture Capability

According to the TOGAF standard, the objectives of each ADM phase are as follows1:

•Phase E: Opportunities and Solutions

oDetermine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value

oIdentify and group major work packages within the Architecture Roadmap

oIdentify and group major implementation projects to realize the Architecture Roadmap

oIdentify dependencies between increments and projects

oEstimate cost, benefit, and risk at a high level for each increment and project

oConduct initial prioritization and sequencing of the Architecture Roadmap and projects

•Phase F: Migration Planning

oGenerate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D

oConfirm the Transition Architectures with relevant stakeholders

oCreate the Implementation and Migration Plan, including Transition Architectures, work packages, projects, and other activities

oConfirm and agree the Architecture Roadmap and Implementation and Migration Plan with relevant stakeholders

•Phase G: Implementation Governance

oFinalize the Architecture Roadmap and the supporting Implementation and Migration Plan

oEnsure conformance with the Target Architecture by implementation projects

oPerform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests

oEnsure that the architecture lifecycle is maintained

oEnsure that the Architecture Governance Framework is executed

•Phase H: Architecture Change Management

oEnsure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders

oManage risks and issues related to the Architecture Roadmap and Implementation and Migration Plan

oMonitor the implementation projects and Transition Architectures

oManage changes to the architecture baseline

oManage changes to the Architecture Capability

Therefore, the correct matching of the objectives and the phases is:

•1G: Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value

•2E: Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D

•3F: Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan

•4F: Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders

References: 1: The TOGAF Architecture Development Method

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

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 blocks12 References: 1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 23: Phase E: Opportunities and Solutions 2: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 36: Building Blocks

An Architecture Contract is a deliverable that specifies the responsibilities and obligations of the parties involved in the implementation and governance of an architecture. It ensures a system of continuous monitoring to check integrity changes decision-making and audit of all architecture-related activities. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.4 Architecture Contracts.

The purpose of Enterprise Architecture is to guide effective change by providing a coherent and consistent view of the enterprise’s current and future state, as well as the roadmap and principles for achieving it. Enterprise Architecture helps to align business and IT strategies,optimize resources and investments, reduce complexity and risks, enhance agility and innovation, and deliver value to stakeholders. Reference: The TOGAF® Standard | The Open Group Website, Section 1.3 Executive Overview.

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.

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

References:

• 1: The TOGAF Standard, Version 9.2, Chapter 5: Architecture Development Method (ADM)
• 2: The TOGAF Standard, Version 9.2, Chapter 17: Requirements Management

Concerns are interests important to the stakeholders in a system. They are used to identify and classify the system’s stakeholders and to guide the selection of viewpoints for the architecture description. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.1 Architecture Viewpoints

Business principles business goals, and business drivers provide context for architecture work, by describing the needs and ways of working employed by the enterprise. They define what the enterprise wants to achieve, how it wants to operate, and what factors influence its decisions and actions. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2 Preliminary Phase.

• The image shows a diagram that illustrates the basic concepts of architecture description as defined by the ISO/IEC/IEEE 42010:2011 standard1, which is also adopted by the TOGAF standard2.
• According to the ISO/IEC/IEEE 42010:2011 standard, an architecture description is a work product used to express an architecture, and it consists of one or more architecture views1.
• An architecture view is a representation of a system from the perspective of a related set of concerns, and it conforms to an architecture viewpoint1.
• An architecture viewpoint is a specification of the conventions for constructing and using an architecture view to address specific stakeholder concerns1.
• Therefore, the correct answer is option A, which identifies the items labeled as “A” and “B” in the image as an architecture viewpoint and an architecture view, respectively. References:
• 1: ISO/IEC/IEEE 42010:2011 - Systems and software engineering — Architecture description1
• 2: TOGAF Standard, Version 9.2 - Part IV: Architecture Content Framework - 31. Architectural Artifacts2

Risk is defined as the effect of uncertainty on objectives, according to the ISO 31000 standard, which provides principles and guidelines for risk management1 Risk can be positive or negative, depending on whether the uncertainty affects the achievement or the failure of the objectives. Risk can also be expressed in terms of likelihood and impact, which indicate the probability and the consequence of the risk occurrence. Risk management is the coordinated activities to direct and control an organization with regard to risk. Risk management is an integral part of the TOGAF standard, as it helps to identify, assess, and treat the risks that may affect the architecture development and implementation2 References: 1: ISO 31000:2018, Risk management — Guidelines, Clause 3.1 2: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 32: Risk Management

The planning horizon, depth, and breadth of an Architecture Project, along with the contents of the EA Repository, are typically framed by Strategy, Portfolio,Segment, and End-to-end Target Architecture. The 'Segment' refers to a part of the organization, typically addressed in a Segment Architecture, while 'End-to-end Target Architecture' encompasses the complete view of the planned architecture across the entire organization.

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. Reference: The TOGAF® Standard | The Open Group Website, Section 2.4 Architecture Repository.

EA applies architecture principles and practices to analyze, design, plan, and implement enterprise analysis that supports digital transformation, IT growth, and the modernization of IT2. EA also helps organizations improve the efficiency, timeliness, and reliability of business information, as well as the alignment, agility, and adaptability of the architecture to the changing needs and requirements3. Therefore, the best summary of the purpose of EA is to guide effective change.

References: 1: Enterprise architecture - Wikipedia 2: What is enterprise architecture? A framework for transformation 3: 3 The Purpose of Enterprise Architecture - The Open Group

The ability to develop, use, and sustain the architecture of a particular enterprise using architecture to govern change is an EA Capability. An EA Capability is a set of skills, processes, roles, responsibilities, tools, and techniques that enable an enterprise to successfully develop and maintain its Enterprise Architecture and achieve its desired outcomes. An EA Capability is part of an enterprise’s overall capability portfolio and should be aligned with its strategy and objectives. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2 Preliminary Phase.

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. Reference: The TOGAF® Standard, Version 9.2 - The Open Group, Section 2.4 Architecture Repository.

Business scenarios are a technique recommended by the TOGAF ADM for use in developing an Architecture Vision document12. Business scenarios are a means of capturing the business requirements and drivers, the processes and actors involved, and the desired outcomes and measures of success34.Business scenarios help to create a common vision and understanding among the stakeholders, and to identify and validate the architecture requirements . Business scenarios also provide a basis for analyzing the impact and value of the proposed architecture. References:

•The TOGAF Standard, Version 9.2 - Phase A: Architecture Vision - The Open Group

•TOGAF® Standard — Introduction - Phase A: Architecture Vision

•The TOGAF Standard, Version 9.2 - Definitions - The Open Group

•Business Scenarios - The Open Group

•[The TOGAF Standard, Version 9.2 - Architecture Requirements Specification - The Open Group]

•[The TOGAF Standard, Version 9.2 - Architecture Vision - The Open Group]

•[The TOGAF Standard, Version 9.2 - Business Transformation Readiness Assessment - The Open Group]

According to the TOGAF Standard, 10th Edition, documents which are under development and have not undergone any formal review and approval process are called draft documents, while documents which have been reviewed and approved are called approved documents 1. Draft documents are typically marked with a version number of 0.x, indicating that they are incomplete or provisional. Approved documents are typically marked with a version number of 1.0 or higher, indicating that they have been finalized and authorized. The other options are not correct, as they are not the terms used by the TOGAF Standard to distinguish between documents under development and documents that have been reviewed and approved. The terms “finalized”, “concept”, “deliverable”, and “Version 0.1” and “Version 1.0” are not specific to the TOGAF Standard, and they may have different meanings or interpretations in different contexts. References: 1: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 7: Applying Iteration to the ADM, Section 7.2.3 Document Categorization.

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