The Open Group OGEA-103 Practice Test - Questions Answers, Page 3

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.

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.

This statement best supports the need to govern Enterprise Architecture. Best practice governance enables the organization to control value realization by ensuring that architectures are aligned with the enterprise’s strategy and objectives, meet the quality and performance requirements, and deliver the expected benefits and outcomes. The Architecture Project does not mandate the governance of the target architecture, but rather follows the governance framework established by the enterprise. The TOGAF standard can be used without executive governance, but it is recommended that executive sponsorship and support are obtained for successful architecture development and transition. The Stakeholders preferences may go beyond the architecture project scope and need control, but this is not the primary reason for governing Enterprise Architecture.

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

According to the TOGAF template for Architecture Principles, the Rationale section shoulddescribe the relationship to other principles, as well as the business benefits and the intentionsof adhering to the principle. The Rationale section should use business terminology and point tothe similarity of information and technology principles to the principles governing business operations. The Rationale section should also explain how the principle supports theachievement of the business objectives and key architecture drivers.Reference:Architecture Principles TemplateThe TOGAF Standard, Version 9.2 - Architecture PrinciplesThe Open Group Exam OGEA-103 Topic 1 Question 4 Discussion

1E: To identify delivery vehicles (projects programs portfolios) that will deliver the Target Architecture 2F: To confirm readiness and ability to undergo change 3E: To determine whether an incremental approach is required and if so identify Transition Architectures that will deliver continuous business value 4G: To perform appropriate governance functions while the solution is being implemented

Reference: The TOGAF® Standard | The Open Group Website, Section 3.2 ADM Phases.

This statement best describes iteration and the ADM. The ADM is iterative over the whole process between phases and within phases because it allows for feedback loops and refinements at any point in the architecture development and transition process. Iteration enables architects to address changing requirements, assumptions, constraints, and environments; to validate and improve architectures; to manage risks and issues; and to ensure stakeholder satisfaction and value realization. Reference: The TOGAF® Standard | The Open Group Website, Section 3.1 Introduction to the ADM.

The four dimensions used to scope an architecture are Breadth, Depth, Time Period, and Architecture Domains. Breadth refers to the extent of the enterprise covered by the architecture. Depth refers to the level of detail and completeness of the architecture. Time Period refers to the planning horizon and the number of Transition Architectures required to achieve the Target Architecture. Architecture Domains refer to the four domains of Business, Data, Application, and Technology that constitute an enterprise’s architecture. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.1 Phase A: Architecture Vision.

The statement illustrates iteration and the ADM. Iteration is the technique of repeating a process or a phase with the aim of improving or refining the outcome. Iteration allows for feedback loops and adaptations at any point in the architecture development and transition process. Separate projects may operate their own ADM cycles concurrently, with relationships between the different projects, to address different aspects or levels of the architecture in an iterative manner. Reference: The TOGAF® Standard | The Open Group Website, Section 3.1 Introduction to the ADM.

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.