OGEA-101 Exam Dumps - TOGAF Enterprise Architecture Part 1 Exam (English)

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.

Business Transformation Readiness Assessment is a joint effort between corporate staff lines of business and IT planners to evaluate the readiness of the organization to undergo change. It involves assessing factors such as vision, commitment, capacity, capability, culture, and motivation that may influence the success of a business transformation initiative. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.2 Business Transformation Readiness Assessment.

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.

Phase G: Implementation Governance provides architectural oversight of the implementation. It ensures that the implementation conforms to the Target Architecture using Architecture Contracts and governance frameworks.

Phase H: Architecture Change Management is about maintaining the architecture lifecycle and handling new requirements, not direct implementation oversight.

Preliminary Phase is about setting up the architecture capability.

Phase A is about developing the Architecture Vision.

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 section should 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.

This description matches Phase B: Business Architecture. In TOGAF, Phase B is the phase in which the architect develops the target Business Architecture and identifies the gaps between the baseline and target states. The phase is not limited to producing models only; it also ensures that the resulting domain architecture is reviewed and approved by stakeholders and that the implications of the gaps are understood. The wording in the question is characteristic of the domain architecture phases, and among the options provided, Phase B is the only domain architecture phase listed.

Phase A is concerned with developing the Architecture Vision, scope, constraints, and stakeholder consensus at a high level. The Preliminary Phase establishes the architecture capability and governance framework. Phase E is focused on Opportunities and Solutions, where solution building blocks, work packages, and transition approaches are identified. None of those primarily describe development of a domain architecture with stakeholder approval and identified gaps.

Because the question refers to a domain architecture, stakeholder approval, and a defined set of gaps to be addressed, the best answer is Phase B. It represents the ADM phase where the Business Architecture is formally developed and agreed.

===========

The Request for Architecture Work is a deliverable that is sent from the sponsor and triggers the start of an architecture development cycle. It defines the scope, budget, schedule, and deliverables for a specific architecture project. The Statement of Architecture Work is a deliverable that is produced by the architect and defines the approach and resources needed to complete an architecture project. It forms the basis of a contractual agreement between the sponsor and the architecture organization. The Architecture Principles are a deliverable that is produced by the architect and defines the general rules and guidelines for the architecture work. They reflect the business principles, business goals, and business drivers of the organization. The Architecture Requirements Specification is a deliverable that is produced by the architect and defines the requirements that govern the architecture work. It covers both functional and non-functional requirements as well as constraints and assumptions. 

•Phase A: Architecture Vision

oDevelop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture

oDefine the scope and boundaries of the architecture engagement

oIdentify the key stakeholders and their concerns and expectations

oDefine the Architecture Vision statement and the Architecture Definition Document

oObtain approval and commitment from the sponsors and stakeholders

•Phase B: Business Architecture

oDevelop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals

oDefine the Baseline Business Architecture, if not available

oPerform a gap analysis between the Baseline and Target Business Architectures

oDefine candidate roadmap components for the Business Architecture

oResolve impacts across the Architecture Landscape

•Phase C: Information Systems Architecture

oDevelop the Target Data Architecture that enables the Business Architecture and the Architecture Vision

oDevelop the Target Application Architecture that supports the Business Architecture and the Architecture Vision

oDefine the Baseline Data and Application Architectures, if not available

oPerform a gap analysis between the Baseline and Target Data and Application Architectures

oDefine candidate roadmap components for the Information Systems Architecture

oResolve impacts across the Architecture Landscape

•Phase D: Technology Architecture

oDevelop the Target Technology Architecture that enables the Information Systems Architecture and the Architecture Vision

oDefine the Baseline Technology Architecture, if not available

oPerform a gap analysis between the Baseline and Target Technology Architectures

oIdentify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures

oResolve impacts across the Architecture Landscape

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

•1C: Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision

•2B: Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals

•3A: Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture

•4D: Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures