OGEA-103 Exam Dumps - TOGAF Enterprise Architecture Combined Part 1 and Part 2 Exam

According to the TOGAF Standard, 10th Edition, the Preliminary Phase of the Architecture Development Method (ADM) has the purpose to develop an Enterprise Architecture Capability 1. An Enterprise Architecture Capability is the ability of the organization to perform the activities and tasks related to Enterprise Architecture, such as defining the scope, principles, vision, governance, and stakeholders of the architecture. The Preliminary Phase also establishes the architecture framework, the architecture repository, the architecture tools, and the architecture team 1. The other options are not correct, as they have different purposes in the ADM. Phase G: Implementation Governance has the purpose to ensure that the implementation projects conform to the target architecture 2. Phase A: Architecture Vision has the purpose to define the scope, stakeholders, business drivers, and objectives of the architecture project 3. Phase B: Business Architecture has the purpose to describe the baseline and target business architecture, and to identify the gaps between them . References: 1: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 6: Preliminary Phase. 2: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 18: Phase G: Implementation Governance. 3: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 12: Phase A: Architecture Vision. : TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 13: Phase B: Business Architecture.

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.

According to the TOGAF Standard, Version 9.2, an architecture view is a representation of a system from the perspective of a related set of concerns1. It consists of one or more architecture models that demonstrate how the system addresses the stakeholder concerns1.

An architecture viewpoint is a specification of the conventions for constructing and using an architecture view to address specific stakeholder concerns1. It defines the perspective, scope, notation, and techniques for creating an architecture view of a system1.

Architects can present architecture views and viewpoints to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture, because23:

Architecture views and viewpoints help to communicate and visualize the architecture in a way that is meaningful and relevant to different stakeholders, addressing their specific interests and needs.

Architecture views and viewpoints help to elicit and validate the stakeholder concerns and requirements, ensuring that they are aligned with the business goals and objectives, and that they are consistent and feasible within the architecture context.

Architecture views and viewpoints help to identify and resolve any conflicts, gaps, or trade-offs among the stakeholder concerns and requirements, ensuring that they are balanced and prioritized in the architecture design and decision-making.

Architecture views and viewpoints help to demonstrate and verify the value and benefits of the architecture to the stakeholders, ensuring that they are satisfied and committed to the architecture outcome and governance.

References:

1: The TOGAF Standard, Version 9.2, Chapter 22: Architecture Views, Viewpoints, and Stakeholders

2: The TOGAF Standard, Version 9.2, Chapter 4: Introduction to Part II, Section 4.2: What is an Architecture Framework?

3: The TOGAF Standard, Version 9.2, Chapter 31: Architectural Artifacts, Section 31.1: Basic Concepts

The illustration shows the relationship between the Enterprise Continuum, the Architecture Continuum, and the Solutions Continuum, which are key concepts in the TOGAF framework. The Enterprise Continuum is a view of the Architecture Repository that shows how generic foundation architectures can be leveraged and specialized to support the requirements of an individual organization. The Architecture Continuum specifies a structured classification for architectural artifacts, such as models, patterns, and descriptions, that can be reused and adapted across different domains and levels of abstraction. The Solutions Continuum identifies implemented solutions that support various stages of business and IT capability evolution, such as common systems, industry solutions, and organization-specific solutions. The illustration also shows how the architecture context and requirements are influenced by external factors, such as business drivers, stakeholders, and standards, and how they shape the generic and specific architectures and solutions. The illustration also shows how the deployed solutions become part of the architecture context for future iterations of the architecture development cycle. References:

•TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 6: Architecture Repository, Section 6.2 Enterprise Continuum.

•TOGAF Standard, 10th Edition, Part IV: Architecture Content Framework, Chapter 35: Enterprise Continuum and Tools, Section 35.1 Introduction.

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