Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
Complete the following sentence. In the ADM documents which are under development and have not undergone any formal review and approval process are_______________.
In the ADM documents which are under development and have not undergone any formal review and approval process are called ''draft''. This indicates that they are subject to change and refinement as the architecture development progresses. Reference: The TOGAF Standard | The Open Group Website, Section 4.2.5 Architecture Deliverables.
Please read this scenario prior to answering the question.
You are employed as an Enterprise Architect for a company that is an international supplier of manufacturing systems.
The company has multiple manufacturing plants where it assembles both standard and customized products for industrial production automation. Each of these plants has been operating its own planning and production scheduling systems, as well as applications and control systems that drive the automated production line. The current systems work with the local partners in the supply chain at each plant.
The company has been facing competition in the marketplace and its leadership has been considering how to improve production efficiency. A favored proposal is to replace many of the systems with a centralized system communicating with the manufacturing plants. The CIO has asked the EA team to develop an architecture for this approach that supports both standardized and customized production across multiple manufacturing plants, while maintaining enterprise-wide integration and governance.
The company has an Enterprise Architecture (EA) practice and uses the TOGAF standard as the basis for its work. It has been running for many years and has established governance and development processes for E
The correct answer is Option A because it most closely follows the objectives and activities of Phase A -- Architecture Vision in the TOGAF ADM. The scenario states that the Request for Architecture Work has already been approved, which means the architecture engagement has been formally initiated and the next activity is to establish a shared Architecture Vision.
During Phase A, TOGAF recommends identifying stakeholders, understanding their concerns, gathering high-level business requirements, and developing an Architecture Vision that includes summary views of the baseline and target environments. The purpose is to obtain stakeholder agreement on the scope, value, constraints, and direction of the proposed architecture before detailed architecture development begins. Option A reflects this process by gathering requirements through workshops, creating a preliminary Architecture Vision, describing the baseline and target environments across the business, information systems, and technology domains, and using the vision to build stakeholder consensus.
Option B is incorrect because selecting technology through a proof-of-concept occurs much later and should not precede architecture definition. Option C includes useful activities such as stakeholder analysis and requirement gathering, but it omits the essential TOGAF deliverable of the Architecture Vision. Option D describes activities associated with later ADM phases, including gap analysis and work package identification.
Therefore, according to the TOGAF Standard, Option A is the best answer because it accurately reflects the purpose and outputs of Phase A -- Architecture Vision.
Exhibit:
Consider the image showing basic architectural concepts.
What are items A and B?
In the context of TOGAF, a stakeholder is any individual, team, or organization who has interests in, or concerns relative to, the outcome of the architecture. Concerns are those interests which pertain to any aspect of the system's functioning, development or operation, including considerations such as performance, reliability, and security1. Reference:
*The TOGAF Standard, Version 9.2 - Definitions - The Open Group
Refer to the table below:
Which ADM Phase does this describe?
The description provided aligns with Phase F: Migration Planning in the TOGAF ADM. This phase focuses on finalizing and implementing the projects necessary to reach the adjusted target state.
Phase F Objective:
Ensures projects and work packages are well-defined and align with stakeholder priorities.
Translates architecture changes into actionable implementation projects.
Assesses risk, value, and effort in implementation.
Establishes the Implementation and Migration Plan.
Key Outputs of Phase F:
Architecture Roadmap (Updated)
Implementation and Migration Plan
Governance Model for Change Implementation
Why Other Options Are Incorrect:
Option A (Phase E: OpportunitiesandSolutions): Focuses on defining projects and high-level solutions, but does not complete their implementation planning.
Option B (Phase A: Architecture Vision): Establishes high-level goals but does not involve migration planning.
Option C (Phase G: Implementation Governance): Ensures the execution aligns with architecture, but does not define projects for migration.
TOGAF Standard, 10th Edition -- Part II: Architecture Development Method, Chapter 19 (Phase F: Migration Planning).
Complete the sentence. The purpose of the Gap Analysis technique is to _____.
Comprehensive and Detailed Explanation
Gap Analysis is an ADM technique used in Phases B, C, and D of the TOGAF ADM (Business, Information Systems, and Technology Architectures).
Its main purpose is to validate the target architecture by comparing the Baseline Architecture with the Target Architecture and identifying:
Gaps (building blocks or capabilities present in the target but missing in the baseline).
Overlaps (building blocks duplicated across architectures).
Conflicts (inconsistencies between baseline and target).
The output of Gap Analysis provides:
A validated Target Architecture.
A set of identified gaps that must be addressed by future work packages in Phase E: Opportunities and Solutions.
Therefore, the purpose of Gap Analysis is best expressed as to validate the architecture (Answer D).
Why the other options are incorrect
A . Establish quality metrics for the architecture: This is part of performance management and governance, not Gap Analysis.
B . Identify non-functional requirements: Non-functional requirements are captured through requirements management and stakeholder analysis, not Gap Analysis.
C . Determine service levels: Service levels are typically defined in SLAs and operational models, not through Gap Analysis.
Reference
The Open Group, TOGAF Standard, Version 9.2, Part III: ADM Guidelines & Techniques --- Gap Analysis.
The Open Group, TOGAF 9 Certified Study Guide --- explains the role of Gap Analysis in validating architectures and identifying work package inputs.
200 questions covering all exam domains, starting from $20
14 domains from the The Open Group OGEA-103 exam outline, with approximate weightings. Every sample question above is tagged with the domain it comes from
Candidates are assessed on fundamental concepts and components forming the foundation of the TOGAF standard, including its structure and terminology. This includes understanding the TOGAF framework structure, key terms, and how the standard is organized.
This section introduces the purpose and benefits of enterprise architecture, providing a high-level overview of its role in aligning business and technology strategies. It covers why organizations adopt enterprise architecture and what benefits it delivers.
This section delves into the structured process of developing and managing enterprise architecture initiatives, ensuring consistency and alignment with business goals. Candidates learn the ADM phases from Preliminary through Phase H and how to apply them end-to-end.
Candidates explore the concept of the Enterprise Continuum and the array of tools available to support the creation and maintenance of enterprise architectures. This includes understanding how organizations position themselves within the continuum and selecting appropriate tools.
This section is dedicated to understanding the processes and models that establish effective oversight and direction for an organization's enterprise architecture. Candidates learn governance structures, decision-making frameworks, and dispensation processes.
Candidates demonstrate their ability to interpret and apply the reference frameworks provided by TOGAF to guide enterprise architecture adoption and implementation. This covers how to use TOGAF's built-in models and customize them for organizational contexts.
This section emphasizes the importance of understanding the scope and impact of enterprise architecture within the broader context of an organization's operations and strategies. Candidates learn how to position architecture work within organizational strategy and constraints.
Candidates learn strategies to identify, engage, and effectively manage stakeholders, ensuring their requirements are addressed throughout the enterprise architecture journey. This includes techniques for stakeholder analysis and engagement planning.
Sample question from this domain above: Q4
This section highlights the initial steps of the ADM, which involve defining the vision, scope, and objectives that set the tone for the entire initiative. Candidates learn how to structure Phase A work and set up architecture projects for success.
Candidates are tested on skills related to the process of crafting architecture artifacts, ensuring they align with the unique needs and aspirations of the organization. This covers developing business, information systems, and technology architectures.
Sample question from this domain above: Q2
This section equips candidates with the knowledge to smoothly transition from planning to execution, adopting best practices for a successful architecture implementation. Candidates learn implementation planning and governance during the implementation phase.
In this section, change management strategies are explored, teaching candidates how to incorporate updates and adapt the architecture to meet evolving business demands. This includes managing the architecture lifecycle and responding to organizational change.
The focus of this section is on understanding the methods and techniques for gathering, analyzing, and overseeing requirements to ensure the architecture meets the dynamic needs of the business. Candidates learn requirement management processes throughout the ADM.
Sample question from this domain above: Q1
Candidates prove their skill related to the array of tools, techniques, and practices that facilitate the efficient execution of the ADM, ultimately enhancing the development and management of enterprise architectures. This includes supporting methodologies and best practices.
Common questions about the exam itself
