The Open Group OGEA-103 TOGAF Enterprise Architecture Combined Part 1 and Part 2 Exam Dumps and Practice Test Questions Set 1 Q1-15

Visit here for our full The Open Group OGEA-103 exam dumps and practice test questions.

Question 1

Which activity is the primary objective of Phase E in the ADM?

A) Develop the Architecture Vision
B) Create detailed architectures for business, data, application, and technology domains
C) Consolidate gaps into work packages and produce the Architecture Roadmap and Implementation and Migration Plan
D) Govern implementation and ensure compliance with the target architecture

Answer: C)

Explanation:

Developing the Architecture Vision is an early activity that establishes scope, principles, and stakeholder alignment. It frames the case for change and communicates high-level goals. This activity is critical for securing sponsorship and setting direction, but it does not consolidate gaps or produce actionable plans. It is high-level and precedes detailed design and planning.

Creating detailed architectures for business, data, application, and technology domains provides clarity on target states and gaps. These designs define capabilities, processes, information structures, applications, and technology platforms. They are essential for understanding what must change, but they remain descriptive. They do not assemble changes into work packages or sequence delivery. This work is foundational but not the central purpose of Phase E.

Governing implementation ensures compliance with architectural intent. It involves monitoring projects, conducting compliance assessments, and managing deviations. This oversight is indispensable for protecting value and ensuring outcomes match expectations. However, it is not the purpose of Phase E. Governance occurs later, once projects are mobilized and delivery begins. Phase E is about planning, not oversight.

Consolidating gaps into work packages and producing the Architecture Roadmap and Implementation and Migration Plan is the essence of Phase E. This activity translates designs into executable change plans. It prioritizes work, defines transition architectures, and sequences delivery. It ensures stakeholders understand the scale and timing of change. It provides clarity on resources, dependencies, and risks. This activity bridges design and execution, turning architecture into actionable plans. For these reasons, consolidating gaps and producing the roadmap is the primary objective of Phase E.

Question 2

What is the main purpose of the TOGAF Content Metamodel?

A) Provide a method to source and develop the architecture capability
B) Define structured relationships between architecture artifacts to enable traceability and consistency across the enterprise
C) Define organizational structures for the enterprise architecture team and governance bodies
D) Provide detailed UML profiles and implementation-level patterns for solution design

Answer: B)

Explanation:

Providing a method to source and develop the architecture capability focuses on roles, responsibilities, and processes. It ensures that the enterprise architecture function operates effectively. This guidance is essential for practice maturity, but it does not define artifact relationships. It addresses how the team works, not the structure of architectural content.

Defining organizational structures clarifies how teams are formed and how governance operates. It establishes councils, boards, and escalation paths. This guidance is vital for adoption and enforcement, but it does not define artifact types or relationships. It addresses human coordination, not content structure.

Providing detailed UML profiles and implementation-level patterns supports solution design. It defines classes, sequences, and deployment views for software systems. This work is valuable for engineering, but it operates at a level below enterprise architecture. The content metamodel is not about UML or solution-level detail. It is about enterprise-level artifact relationships.

Defining structured relationships between architecture artifacts is the essence of the content metamodel. It formalizes entities such as capabilities, processes, applications, and data, and shows how they connect. This enables traceability from drivers to solutions. It ensures consistency, reuse, and impact analysis. It makes the repository coherent and navigable. This structured model is central to TOGAF, providing semantic integrity. For these reasons, defining relationships between artifacts is the main purpose of the content metamodel.

Question 3

Which best describes the purpose of the Business Scenario technique within TOGAF?

A) Identify and quantify business value by describing processes, pain points, and requirements in context to derive architectural needs
B) Allocate financial resources and approve funding for portfolios and programs
C) Define comprehensive data models and logical schemas for enterprise information management
D) Establish architecture governance boards and decision-making structures

Answer: A)

Explanation:

Allocating financial resources and approving funding belong to portfolio management. It assesses business cases, risks, and alignment to decide which initiatives to fund. Architecture informs these decisions, but the Business Scenario technique is not a funding mechanism. It provides input, not approvals.

Defining comprehensive data models and logical schemas is the work of data architecture. It structures information entities and relationships. This modeling is critical for integration and analytics, but it is not the purpose of the Business Scenario technique. That technique captures business situations, not data schemas.

Establishing governance boards defines councils, review cadence, and decision rights. This ensures architectural coherence and compliance. Governance is essential, but it is not the purpose of the Business Scenario technique. That technique is analytical, not organizational.

Identifying and quantifying business value by describing processes, pain points, and requirements in context is the essence of the Business Scenario technique. It frames real-world situations that expose gaps and needs. It translates concerns into requirements and measurable outcomes. It grounds architecture in operational reality, avoiding vague statements. It enables traceability from drivers to solutions and helps prioritize changes. This technique strengthens the Architecture Vision and domain architectures by rooting them in evidence. For these reasons, identifying and quantifying value through scenarios is the purpose of the Business Scenario technique.

Question 4

Which deliverable is produced in Phase B of the ADM?

A) Business Architecture describing capabilities, processes, and organizational structures
B) Technology Architecture, defining platforms and infrastructure services
C) Architecture Roadmap sequencing work packages and transition architectures
D) Architecture Vision capturing high-level goals and stakeholder concerns

Answer: A)

Explanation:

The Technology Architecture deliverable focuses on infrastructure, platforms, and technology services that enable applications and data. It defines standards, deployment models, and integration patterns for hardware, networks, middleware, and cloud services. This work is critical for ensuring scalability, resilience, and interoperability. However, this deliverable is not produced in the phase dedicated to business modeling. It belongs to a later stage where technical enablers are described after business and information needs are clarified. While indispensable, it is not the primary output of the phase concerned with business capabilities and organizational design.

The Architecture Roadmap is a consolidated plan that sequences work packages, defines transition architectures, and communicates the timeline for change. It integrates outputs from multiple domains and aligns them with business priorities, readiness, and dependencies. This roadmap is essential for moving from design to execution, providing stakeholders with clarity on when and how change will occur. Yet, this deliverable is not produced in the phase focused on business architecture. It emerges later when gaps are consolidated, and migration planning is performed. Therefore, while vital, it is not the deliverable associated with the business-focused phase.

The Architecture Vision is the high-level statement of goals, scope, and stakeholder concerns. It frames the case for change, communicates the target state, and secures buy-in. It is created early in the ADM cycle to ensure alignment and sponsorship. This vision is not detailed; it is a concise articulation of intent and value. While foundational, it is not the deliverable of the phase that develops detailed business models. It precedes that work, setting the stage for subsequent domain architectures. Thus, although important, it is not the output of the business architecture phase.

The Business Architecture deliverable describes capabilities, processes, organizational structures, and roles that define how the enterprise operates. It identifies gaps between current and target states, highlights required changes, and provides a foundation for aligning applications, data, and technology. It ensures that subsequent architectures are grounded in business needs and that solutions deliver measurable value. This deliverable is the central output of the phase dedicated to business modeling. It provides clarity on what the enterprise must do, how it organizes itself, and which capabilities are critical. By articulating these elements, it enables traceability from strategy to execution and ensures that technology investments are justified by business outcomes. For these reasons, the Business Architecture is the correct deliverable produced in Phase B.

Question 5

Which artifact is central to Phase C when addressing the Application Architecture?

A) Data Entity Catalog documenting enterprise information structures
B) Application Portfolio describing applications, their interactions, and alignment with business processes
C) Technology Standards Catalog defining infrastructure and platform standards
D) Architecture Contract governing compliance during implementation

Answer: B)

Explanation:

The Data Entity Catalog is a structured list of information entities, attributes, and relationships that define enterprise data. The Data Architecture must ensure consistency, integrity, and interoperability across systems. This catalog supports analytics, compliance, and integration. However, it is not the central artifact of the phase focused on applications. It belongs to the data domain and is produced when modeling information structures rather than application systems. Thus, while valuable, it is not the artifact associated with application architecture.

The Technology Standards Catalog defines infrastructure, platform, and technology standards that guide deployment and integration. It ensures consistency, reduces risk, and supports scalability. This catalog is essential for the Technology Architecture, providing a foundation for selecting and implementing technology solutions. Yet, it is not the artifact central to the application-focused phase. It belongs to a later stage where technical enablers are described. Therefore, while important, it is not the artifact produced in the application architecture phase.

The Architecture Contract governs compliance during implementation. It defines obligations, criteria, and review processes to ensure that projects adhere to architectural intent. This contract is critical for governance, providing a mechanism to manage deviations and enforce standards. However, it is not the artifact produced during application modeling. It is created later when implementation begins, ensuring alignment between design and delivery. Thus, while indispensable, it is not the central artifact of the application architecture phase.

The Application Portfolio describes applications, their interactions, and alignment with business processes. It identifies gaps, redundancies, and opportunities for rationalization. It provides clarity on how applications support capabilities and processes, enabling traceability from business needs to technology solutions. This portfolio is the central artifact of the application architecture phase. It ensures that applications are aligned with business requirements, integrated effectively, and positioned to deliver value. By articulating the application landscape, it supports decisions on modernization, consolidation, and investment. It also provides input for data and technology architectures, ensuring coherence across domains. For these reasons, the Application Portfolio is the correct artifact produced in Phase C.

Question 6

What is the primary role of Phase G in the ADM?

A) Define transition architectures and sequence work packages
B) Govern implementation to ensure compliance with the target architecture
C) Develop detailed domain architectures for business, data, application, and technology
D) Capture stakeholder concerns and create the Architecture Vision

Answer: B)

Explanation:

Defining transition architectures and sequencing work packages is the activity of migration planning. It consolidates gaps, prioritizes changes, and creates a roadmap. This work is essential for moving from design to execution, providing clarity on how change will occur incrementally. However, it is not the primary role of the phase focused on governance. It belongs to an earlier stage where plans are created rather than enforced. Thus, while critical, it is not the role of the governance phase.

Developing detailed domain architectures for business, data, application, and technology is the activity of the design phases. These architectures describe capabilities, processes, information structures, applications, and technology platforms. They provide clarity on target states and gaps. This work is foundational, but it is not the role of the governance phase. It occurs earlier in the ADM cycle, providing input for planning and execution. Therefore, while indispensable, it is not the primary role of the governance phase.

Capturing stakeholder concerns and creating the Architecture Vision is the activity of the initial phase. It frames goals, scope, and value, securing buy-in and alignment. This vision is high-level and sets the stage for subsequent work. While essential, it is not the role of the governance phase. It occurs at the beginning of the ADM cycle, not during implementation oversight. Thus, although important, it is not the primary role of the governance phase.

Governance during implementation ensures compliance with the target architecture. It involves monitoring projects, conducting compliance assessments, managing deviations, and enforcing standards. It provides checkpoints, criteria, and escalation paths to protect architectural integrity. It ensures that delivery aligns with design intent and that exceptions are managed appropriately. This role is the primary purpose of the governance phase. It enables controlled change, reduces risk, and ensures that outcomes match expectations. By enforcing complianceitotects value and ensures that investments deliver the intended benefits. For these reasons, governance during implementation is the correct role of Phase G.

Question 7

Which element is emphasized in the Preliminary Phase of the ADM?

A) Establishing the architecture repository and selecting tools
B) Developing detailed application models and portfolios
C) Creating the Architecture Roadmap and migration plan
D) Conducting compliance reviews during implementation

Answer: A)

Explanation:

Developing detailed application models and portfolios is a task that belongs to the phase dedicated to application architecture. It involves identifying applications, their interactions, and alignment with business processes. This work is critical for rationalization, modernization, and integration. However, it is not the focus of the preliminary stage. That stage is concerned with preparing the environment, defining principles, and establishing foundational structures. Application modeling occurs later, once the practice is established and the vision is clear. Therefore, while important, it is not the element emphasized in the preliminary phase.

Creating the Architecture Roadmap and migration plan is the activity of migration planning. It consolidates gaps, sequences work packages, and defines transition architectures. This plan provides clarity on how change will occur incrementally, aligning with business priorities and readiness. Yet, this activity is not part of the preliminary stage. It occurs after domain architectures are developed and gaps are identified. The preliminary phase is about setting up the practice, not planning specific changes. Thus, although vital, it is not the element emphasized in the preliminary phase.

Conducting compliance reviews during implementation is the activity of governance. It ensures that delivery aligns with architectural intent, managing deviations and enforcing standards. This oversight is indispensable for protecting value and ensuring outcomes match expectations. However, it is not part of the preliminary stage. Governance occurs later, once projects are mobilized and delivery begins. The preliminary phase is about establishing the environment, not overseeing execution. Therefore, while essential, it is not the element emphasized in the preliminary phase.

Establishing the architecture repository and selecting tools is central to the preliminary stage. This involves defining principles, selecting frameworks, and setting up repositories that store artifacts, models, and standards. It ensures that the practice has the infrastructure needed to operate effectively. By establishing repositories and tools, the organization creates a foundation for consistency, traceability, and reuse. This work also includes defining governance structures, tailoring the framework, and clarifying stakeholder engagement. It prepares the enterprise to execute the ADM cycle with discipline and coherence. For these reasons, establishing the repository and selecting tools is the element emphasized in the preliminary phase.

Question 8

Which concept is central to the TOGAF Enterprise Continuum?

A) A structured catalog of reusable architecture building blocks and solution assets
B) A governance framework defining compliance checkpoints and escalation paths
C) A roadmap sequencing work packages and transition architectures
D) A stakeholder map capturing concerns, roles, and influence

Answer: A)

Explanation:

A governance framework defines compliance checkpoints, escalation paths, and decision rights. It ensures that delivery aligns with architectural intent, managing deviations and enforcing standards. This framework is critical for protecting value and ensuring outcomes match expectations. However, it is not the concept central to the continuum. Governance operates on processes and oversight, not on the classification of reusable assets. Therefore, while indispensable, it is not the concept central to the continuum.

A roadmap sequences work packages and transition architectures. It provides clarity on how change will occur incrementally, aligning with business priorities and readiness. This roadmap is essential for moving from design to execution, communicating timelines and dependencies. Yet, it is not the concept central to the continuum. The continuum is about classifying and reusing assets, not sequencing change. Thus, although vital, it is not the concept central to the continuum.

A stakeholder map captures concerns, roles, and influence. It ensures that architecture addresses stakeholder needs and secures buy-in. This map is critical for alignment and communication, providing clarity on who matters and why. However, it is not the concept central to the continuum. The continuum is about assets and reuse, not stakeholder analysis. Therefore, while important, it is not the concept central to the continuum.

A structured catalog of reusable architecture building blocks and solution assets is the essence of the continuum. It classifies assets from generic to specific, enabling reuse across contexts. It includes foundation architectures, common systems architectures, industry architectures, and organization-specific architectures. This continuum provides a way to leverage existing work, reduce duplication, and accelerate delivery. It ensures that architects can draw from a library of assets, tailoring them to specific needs. By structuring assets along a spectrum, it supports consistency, reuse, and efficiency. For these reasons, a structured catalog of reusable assets is the concept central to the continuum.

Question 9

Which deliverable is produced in Phase D of the ADM?

A) Technology Architecture describing platforms, infrastructure, and technology services
B) Business Architecture defining capabilities, processes, and organizational structures
C) Application Portfolio describing applications and their interactions
D) Architecture Vision capturing high-level goals and stakeholder concerns

Answer: A)

Explanation:

The Business Architecture defines capabilities, processes, and organizational structures. It provides clarity on how the enterprise operates and what must change. This deliverable is produced in the phase dedicated to business modeling. It ensures that subsequent architectures are grounded in business needs. However, it is not the deliverable of the technology-focused phase. Therefore, while essential, it is not the deliverable produced in Phase D.

The Application Portfolio describes applications and their interactions. It identifies gaps, redundancies, and opportunities for rationalization. This portfolio is produced in the phase dedicated to application architecture. It ensures that applications align with business processes and deliver value. Yet, it is not the deliverable of the technology-focused phase. Thus, although important, it is not the deliverable produced in Phase D.

The Architecture Vision captures high-level goals and stakeholder concerns. It frames the case for change, communicates the target state, and secures buy-in. This vision is produced early in the ADM cycle, setting the stage for subsequent work. While foundational, it is not the deliverable of the technology-focused phase. It precedes that work, providing context rather than detailed design. Therefore, while vital, it is not the deliverable produced in Phase D.

The Technology Architecture describes platforms, infrastructure, and technology services. It defines standards, deployment models, and integration patterns for hardware, networks, middleware, and cloud services. This deliverable ensures scalability, resilience, and interoperability. It provides clarity on technical enablers that support applications and data. By articulating the technology landscape, it enables rationalization, modernization, and investment decisions. This deliverable is the central output of the technology-focused phase. It ensures that technical solutions align with business needs and application requirements. For these reasons, the Technology Architecture is the deliverable produced in Phase D.

Question 10

Which activity is the primary focus of Phase H in the ADM?

A) Monitor the architecture environment and manage change requests
B) Develop detailed data models and entity catalogs
C) Create the Architecture Vision and secure stakeholder buy-in
D) Define transition architectures and sequence work packages

Answer: A)

Explanation:

Developing detailed data models and entity catalogs is the work of the data architecture phase. It involves defining information structures, relationships, and schemas that support enterprise information management. This work ensures consistency, integrity, and interoperability across systems. While critical, it is not the focus of the phase dedicated to change management. That phase is concerned with monitoring the environment, managing requests, and ensuring that the architecture remains relevant. Data modeling occurs earlier, providing input for applications and technology, not for change governance.

Creating the Architecture Vision and securing stakeholder buy-in is the activity of the initial phase. It frames goals, scope, and value, ensuring alignment and sponsorship. This vision is high-level and sets the stage for subsequent work. While foundational, it is not the focus of the change management phase. That phase occurs later, once architectures are developed and implemented. The vision provides context, but change management ensures ongoing relevance. Therefore, while essential, it is not the activity of the change management phase.

Defining transition architectures and sequencing work packages is the activity of migration planning. It consolidates gaps, prioritizes changes, and creates a roadmap. This plan provides clarity on how change will occur incrementally, aligning with business priorities and readiness. Yet, this activity is not part of the change management phase. It occurs earlier, when plans are created rather than monitored. Change management ensures that those plans remain valid and adapts them as needed. Thus, although vital, it is not the activity of the change management phase.

Monitoring the architecture environment and managing change requests is the essence of the change management phase. This involves tracking external drivers, internal initiatives, and emerging technologies that may impact the architecture. It ensures that the architecture remains aligned with business needs and adapts to new circumstances. It includes managing requests for change, assessing their impact, and updating architectures accordingly. This activity protects relevance, reduces risk, and ensures that investments continue to deliver value. It provides a mechanism for continuous improvement, ensuring that the architecture evolves with the enterprise. For these reasons, monitoring and managing change is the primary focus of Phase H.

Question 11

Which concept is central to the TOGAF Architecture Repository?

A) A structured store of architectural artifacts, standards, and reference models
B) A governance framework defining compliance checkpoints and escalation paths
C) A stakeholder map capturing concerns, roles, and influence
D) A roadmap sequencing work packages and transition architectures

Answer: A)

Explanation:

A governance framework defines compliance checkpoints, escalation paths, and decision rights. It ensures that delivery aligns with architectural intent, managing deviations and enforcing standards. This framework is critical for protecting value and ensuring outcomes match expectations. However, it is not the concept central to the repository. Governance operates on processes and oversight, not on the storage of artifacts. Therefore, while indispensable, it is not the concept central to the repository.

A stakeholder map captures concerns, roles, and influence. It ensures that architecture addresses stakeholder needs and secures buy-in. This map is critical for alignment and communication, providing clarity on who matters and why. However, it is not the concept central to the repository. The repository is about storing and organizing artifacts, not stakeholder analysis. Therefore, while important, it is not the concept central to the repository.

A roadmap sequences work packages and transition architectures. It provides clarity on how change will occur incrementally, aligning with business priorities and readiness. This roadmap is essential for moving from design to execution, communicating timelines and dependencies. Yet, it is not the concept central to the repository. The repository is about storing artifacts, not sequencing change. Thus, although vital, it is not the concept central to the repository.

A structured store of architectural artifacts, standards, and reference models is the essence of the repository. It provides a central location for storing deliverables, models, and standards. It ensures consistency, traceability, and reuse across the enterprise. Organizing artifacts enables impact analysis, compliance checks, and reporting. It also supports collaboration, ensuring that teams work with shared content. This repository is the backbone of the practice, providing a single source of truth. For these reasons, a structured store of artifacts and standards is the concept central to the repository.

Question 12

Which role is emphasized in the Requirements Management phase of the ADM?

A) Ensure that requirements are identified, stored, and addressed throughout the ADM cycle
B) Define technology standards and infrastructure services
C) Capture stakeholder concerns and create the Architecture Vision
D) Govern implementation to ensure compliance with the target architecture

Answer: A)

Explanation:

Defining technology standards and infrastructure services is the work of the technology architecture phase. It involves selecting platforms, defining standards, and ensuring scalability and resilience. This work is critical for enabling applications and data. However, it is not the role of the requirements management phase. That phase is concerned with capturing, storing, and addressing requirements, not defining technology standards. Therefore, while important, it is not the role emphasized in requirements management.

Capturing stakeholder concerns and creating the Architecture Vision is the activity of the initial phase. It frames goals, scope, and value, ensuring alignment and sponsorship. This vision is high-level and sets the stage for subsequent work. While foundational, it is not the role of the requirements management phase. That phase occurs throughout the ADM cycle, ensuring that requirements are addressed. The vision provides context, but requirements management ensures traceability and completeness. Thus, although essential, it is not the role emphasized in requirements management.

Governing implementation to ensure compliance with the target architecture is the activity of the governance phase. It involves monitoring projects, conducting compliance assessments, and managing deviations. This oversight is indispensable for protecting value and ensuring outcomes match expectations. However, it is not the role of the requirements management phase. That phase is concerned with requirements, not governance. Therefore, while vital, it is not the role emphasized in requirements management.

Ensuring that requirements are identified, stored, and addressed throughout the ADM cycle is the essence of requirements management. This involves capturing requirements from stakeholders, storing them in a repository, and ensuring that they are addressed in each phase. It provides traceability from drivers to solutions, ensuring that nothing is overlooked. It also enables impact analysis, showing how changes affect requirements. This role is critical for ensuring that architecture delivers value and meets stakeholder needs. It provides a mechanism for continuous alignment, ensuring that requirements remain relevant and complete. For these reasons, ensuring that requirements are identified, stored, and addressed is the role emphasized in requirements management.

Question 13

Which deliverable is produced in Phase A of the ADM?

A) Architecture Vision capturing high-level goals and stakeholder concerns
B) Technology Architecture describing platforms and infrastructure services
C) Application Portfolio describing applications and their interactions
D) Business Architecture defining capabilities, processes, and organizational structures

Answer: A)

Explanation:

The Technology Architecture deliverable focuses on platforms, infrastructure, and technology services. It defines standards, deployment models, and integration patterns for hardware, networks, middleware, and cloud services. This work ensures scalability, resilience, and interoperability. However, it is not produced in the initial phase. That phase is concerned with framing goals, scope, and stakeholder concerns, not with technical enablers. Technology architecture occurs later, once business and application needs are clarified. Therefore, while essential, it is not the deliverable of the initial phase.

The Application Portfolio describes applications and their interactions. It identifies gaps, redundancies, and opportunities for rationalization. This portfolio ensures that applications align with business processes and deliver value. It is produced in the application architecture phase, not in the initial phase. The initial phase is about vision and alignment, not application modeling. Thus, although important, it is not the deliverable of the initial phase.

The Business Architecture defines capabilities, processes, and organizational structures. It provides clarity on how the enterprise operates and what must change. This deliverable is produced in the business architecture phase, not in the initial phase. The initial phase sets the stage for subsequent work, providing context rather than detailed design. Therefore, while vital, it is not the deliverable of the initial phase.

The Architecture Vision captures high-level goals and stakeholder concerns. It frames the case for change, communicates the target state, and secures buy-in. This vision is concise, providing alignment and sponsorship. It ensures that stakeholders understand the purpose and value of the initiative. It sets the scope, constraints, and principles that guide subsequent work. By articulating the vision, the enterprise creates a foundation for detailed architectures and migration planning. This deliverable is the central output of the initial phase. It ensures that the endeavor is justified, aligned, and supported. For these reasons, the Architecture Vision is the deliverable produced in Phase A.

Question 14

Which concept is central to the TOGAF concept of Building Blocks?

A) Reusable components that can be combined to create architectures and solutions
B) Governance structures defining compliance checkpoints and escalation paths
C) Stakeholder maps capturing concerns, roles, and influence
D) Roadmaps,, sequencing work packages,, and transition architectures

Answer: A)

Explanation:

Governance structures define compliance checkpoints, escalation paths, decision rights, and monitoring mechanisms that ensure architectural discipline is maintained throughout delivery. These structures guide how decisions are made, how risks are addressed, and how exceptions are handled. They serve as the backbone of oversight, ensuring that projects do not diverge from the approved architectural direction. Governance includes activities such as enforcing standards, performing compliance assessments, conducting design reviews, and managing architectural deviations. It helps protect business value by ensuring consistency, reducing unnecessary complexity, and maintaining alignment with strategic objectives. Despite its importance, governance does not represent the concept at the heart of building blocks. Governance is primarily about processes, controls, and oversight rather than reusable components. It ensures that the right components are used correctly, but it does not define what building blocks are or why they matter. Therefore, while essential to a functioning architecture ecosystem, governance is not the concept central to building blocks.

Stakeholder maps capture concerns, expectations, roles, influence, and responsibilities of individuals or groups involved in or affected by architectural work. They help architects understand who the key players are, what drives their priorities, and how architecture must respond to their needs. These maps guide communication strategies, ensure alignment, and prevent misunderstandings. By documenting who cares about what, stakeholder maps help the architecture team engage effectively and maintain support. They play a crucial role during phases where vision, requirements, and constraints are identified. However, stakeholder maps focus on people, relationships, and perspectives. They provide insight into how decisions are shaped, but they do not define or describe reusable architectural components. Building blocks operate within the structural and functional domains of architecture, not within the realm of stakeholder engagement. For this reason, stakeholder maps, although highly valuable, are not the concept central to building blocks.

Roadmaps sequence work packages, initiatives, and transition architectures that guide the journey from the current state to the target state. They convey how change will be delivered incrementally, reflecting business priorities, dependencies, risks, and resource availability. Roadmaps provide a structured timeline that guides execution teams, program managers, and business leaders. They help stakeholders understand when key capabilities will be delivered, how the organization will evolve, and what must happen in each transition stage. Roadmaps are essential for planning transformation and ensuring that the enterprise moves forward in a controlled and coordinated manner. However, while roadmaps provide structure and sequencing, they do not define the fundamental building blocks used to create architectures. A roadmap explains how change unfolds,, but does not describe the modular components that are assembled to create solutions. Therefore, roadmaps, despite their importance, are not the concept central to building blocks.

Reusable components that can be combined, extended, or adapted to create architectures and solutions are the essence of building blocks. This concept lies at the core of architectural design within frameworks such as TOGAF. Building blocks provide modular, well-defined elements that can be reused across multiple scenarios, reducing redundancy and improving consistency. Architectural building blocks describe capabilities, services, or patterns that define what is needed at a conceptual or logical level. Solution building blocks describe specific products, technologies, or implementations that realize those architectural definitions. These components serve as the raw materials from which architectures are constructed. By using building blocks, architects establish repeatable structures, speed up design activities, and ensure alignment across projects. Building blocks also foster interoperability, as components are defined in a consistent manner that supports integration. Their modular nature supports flexibility, allowing architects to adapt or replace components without disrupting the entire architecture. They promote traceability, showing how each component contributes to broader business and technical outcomes. Because they enable reuse, reduce effort, and support structured design, reusable components stand as the concept central to building blocks.

Question 15

Which activity is the primary focus of Phase F in the ADM?

A) Develop detailed domain architectures for business, data, application, and technology
B) Govern implementation to ensure compliance with the target architecture
C) Conduct migration planning, finalize the Architecture Roadmap, and secure approval for implementation
D) Capture stakeholder concerns and create the Architecture Vision

Answer: C)

Explanation:

Developing detailed domain architectures for business, data, application, and technology is foundational work carried out during the design-oriented phases of an architecture framework. These phases concentrate on defining what the future-state enterprise should look like from different architectural lenses. In the business domain, this involves outlining processes, organizational structures, capabilities, and stakeholder relationships. In the data domain, architects identify information requirements, logical data models, and data flows needed to support operations. Application architecture specifies the systems, integrations, and functional applications that will work together to support business capabilities. Technology architecture defines the infrastructure, platforms, and technical components required to host and enable the applications. This set of architectural deliverables becomes a blueprint for transformation. Although comprehensive and essential, these tasks are not performed during the migration planning phase. They happen earlier because migration planning can only begin after target-state architectures have been fully defined, validated, and approved. For this reason, even though domain architecture development is indispensable, it does not represent the purpose of the migration planning phase.

Governing implementation to ensure compliance with the target architecture is another key activity, but it belongs to the governance or architecture oversight phase. During this stage, architects monitor active projects, evaluate whether technical decisions align with the approved target architecture, and enforce compliance through checkpoints, assessments, and exception processes. This governance ensures that the transformation stays on track, adheres to principles, and produces predictable outcomes. The governance phase focuses on protecting architectural integrity during delivery. It includes activities such as reviewing project solutions, analyzing deviations, managing risks, and ensuring that approved standards are implemented consistently. Although governance is essential for maintaining value and ensuring that designed architectures are followed correctly, it does not belong to the migration planning phase. Migration planning occurs before implementation begins, while governance occurs during and after implementation. Therefore, even though governance is critical, it is not the central activity associated with the migration planning phase.

Capturing stakeholder concerns and creating the Architecture Vision is work that takes place in the initial and high-level strategic phase. During this phase, architects gather inputs from executives, business leaders, technical teams, and other stakeholders to understand goals, pain points, constraints, desired outcomes, and opportunities. This phase sets direction by articulating the scope of the architectural effort, high-level requirements, guiding principles, and value propositions. The Architecture Vision serves as a conceptual north star that aligns all stakeholders and provides justification for the architecture work that follows. While extremely important for establishing context and securing sponsorship, this early-phase work is not part of the migration planning phase. Migration planning depends on fully developed architectural designs, which means it happens significantly later in the lifecycle. Thus, stakeholder alignment and vision creation are early activities, not tasks associated with migration planning.

Conducting migration planning, finalizing the Architecture Roadmap, and securing approval for implementation represent the core activities of the migration planning phase. In this phase, architects evaluate the gaps identified between the current state and the target state and organize them into structured, achievable increments. They define transition architectures, which describe intermediate states that the enterprise will pass through while moving toward the final vision. Migration planning clarifies the sequence of initiatives, dependencies, risks, required resources, and expected outcomes. It ensures that the transformation is feasible, realistic, and aligned with business priorities. This phase also involves preparing the Architecture Roadmap, a time-phased representation of work packages, capability increments, and major deliverables. Stakeholder approval is another essential aspect, as no roadmap can proceed without agreement on scope, funding, and timing. The migration planning phase transforms architectural designs into actionable steps that guide implementation teams. It is the link between vision and execution, ensuring that the enterprise advances in a structured and predictable manner. For these reasons, migration planning and roadmap finalization are the defining activities of Phase F.