What is used to structure architectural information in an orderly way so that it can be processed to meet stakeholder needs?
Correct Answer: C
A content metamodel is a formal structure that defines the types of entities and relationships that are used to capture, store, filter, query, and represent architectural information in a way that supports consistency, completeness, and traceability12. A stakeholder map is a tool that identifies and analyzes the key stakeholders and their interests, influence, and expectations in relation to the architecture3. It is not used to structure architectural information, but rather to understand the stakeholder needs and concerns. An architecture framework is a set of principles, guidelines, standards, and tools that provide a common structure and methodology for developing architectures4. It is not used to structure architectural information, but rather to guide the architecture development process and ensure alignment with the business strategy and objectives. An EA library is a repository that stores and manages the architecture artifacts, deliverables, and other relevant information produced and consumed during the architecture development and governance. It is not used to structure architectural information, but rather to provide access, security, and version control for the architecture content.
Question 2
Consider the following ADM phases objectives. Which phase does each objective match?
Correct Answer: A
The objectives listed in the question correspond to the objectives of different phases of the TOGAF ADM (Architecture Development Method), which is a method for developing and managing an enterprise architecture1. The ADM consists of nine phases, each with a specific purpose and output. The phases are1: Preliminary Phase: To prepare and initiate the architecture development cycle, including defining the architecture framework, principles, and governance. Phase A: Architecture Vision: To define the scope, vision, and stakeholders of the architecture initiative, and to obtain approval to proceed. Phase B: Business Architecture: To describe the baseline and target business architecture, and to identify the gaps between them. Phase C: Information Systems Architectures: To describe the baseline and target data and application architectures, and to identify the gaps between them. Phase D: Technology Architecture: To describe the baseline and target technology architecture, and to identify the gaps between them. Phase E: Opportunities and Solutions: To identify and evaluate the opportunities and solutions for implementing the target architecture, and to define the work packages and transition architectures. Phase F: Migration Planning: To finalize the implementation and migration plan, and to ensure alignment with the enterprise portfolio and project management. Phase G: Implementation Governance: To provide architecture oversight and guidance for the implementation projects, and to manage any architecture change requests. Phase H: Architecture Change Management: To monitor the changes in the business and technology environment, and to assess the impact and performance of the architecture. Based on the above definitions, we can match each objective with the corresponding phase as follows: Objective 1: Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision. This objective is achieved in Phase C: Information Systems Architectures, where the data architecture is defined as a subset of the information systems architecture2. Objective 2: Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals. This objective is achieved in Phase B: Business Architecture, where the business architecture is defined as a subset of the enterprise architecture3. Objective 3: Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture. This objective is achieved in Phase A: Architecture Vision, where the architecture vision is defined as a high-level description of the target architecture and its benefits4. Objective 4: Develop the Target Application Architecture that enables the Business Architecture and the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns. This objective is achieved in Phase C: Information Systems Architectures, where the application architecture is defined as a subset of the information systems architecture2. References: 1: The TOGAF Standard, Version 9.2, Chapter 5: Architecture Development Method (ADM) 2: The TOGAF Standard, Version 9.2, Chapter 9: Phase C: Information Systems Architectures 3: The TOGAF Standard, Version 9.2, Chapter 8: Phase B: Business Architecture 4: The TOGAF Standard, Version 9.2, Chapter 7: Phase A: Architecture Vision
Question 3
Consider the following ADM phases objectives. Which phase does each objective match?
Correct Answer: B
Explanation 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.
Question 4
What is the purpose of the Preliminary Phase?
Correct Answer: A
Explanation An Enterprise Architecture Capability is the ability of the organization to perform effective and efficient architecture work, including the definition, governance, and management of its architectures2. The Preliminary Phase involves the following activities1: *Reviewing the organizational context, scope, and drivers for conducting Enterprise Architecture *Establishing the Architecture Capability desired by the organization, including the maturity level, roles, responsibilities, processes, and tools *Defining and establishing the Organizational Model for Enterprise Architecture, which describes how the architecture function is organized and integrated within the enterprise *Defining and establishing the Architecture Governance framework, which provides the mechanisms for ensuring the quality, consistency, and compliance of the architecture work *Selecting and implementing the tools that support the Architecture Capability, such as repositories, modeling tools, and communication tools *Defining the Architecture Principles that will guide and constrain the architecture work, based on the business principles, goals, and drivers of the organization *Defining the Organization-Specific Architecture Framework, which is an adaptation of the generic TOGAF ADM to suit the specific requirements, standards, and practices of the organization The Preliminary Phase is essential for preparing the organization for the successful development and implementation of its architectures, as well as for ensuring the alignment of the architecture work with the business strategy and objectives1. References: 1: Preliminary Phase 2: Enterprise Architecture Capability
Question 5
What can architects present to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture?
Correct Answer: D
Explanation 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
