Question #1
What is an objective of the ADM Preliminary Phase?
- A . To develop a vision of the business value to be delivered by the proposed enterprise architecture
- B . To select and implement tools to support the Architecture Capability
- C . To obtain approval for the Statement of Architecture Work
- D . To create the initial version of the Architecture Roadmap
Correct Answer: B
B
Explanation:
The Preliminary Phase is the preparatory phase of the Architecture Development Method (ADM) cycle, which sets the context and direction for the architecture work. One of the objectives of this phase is to select and implement tools to support the Architecture Capability, which is the ability of an organization to perform enterprise architecture effectively and efficiently. Tools can include software applications, methods, techniques, standards, and frameworks that assist the architecture development and governance processes. The selection and implementation of tools should be based on the requirements and constraints of the organization, and the alignment with the Architecture Principles and the Architecture Vision3 References: 3: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 6: Preliminary Phase: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 45: Establishing and Maintaining an Enterprise Architecture Capability: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 46: Tools for Architecture Development
B
Explanation:
The Preliminary Phase is the preparatory phase of the Architecture Development Method (ADM) cycle, which sets the context and direction for the architecture work. One of the objectives of this phase is to select and implement tools to support the Architecture Capability, which is the ability of an organization to perform enterprise architecture effectively and efficiently. Tools can include software applications, methods, techniques, standards, and frameworks that assist the architecture development and governance processes. The selection and implementation of tools should be based on the requirements and constraints of the organization, and the alignment with the Architecture Principles and the Architecture Vision3 References: 3: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 6: Preliminary Phase: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 45: Establishing and Maintaining an Enterprise Architecture Capability: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 46: Tools for Architecture Development
Question #2
Consider the image showing basic architectural concepts.
What are items A and B?
- A . A-Architecture Viewpoint, B-Architecture View
- B . A-Architecture Board, B-Architecture Capability
- C . A-Candidate Architecture, B-Trade-off
- D . A-Requirement. B-Candidate Architecture
Correct Answer: A
A
Explanation:
– The image shows a diagram that illustrates the basic concepts of architecture description as defined by the ISO/IEC/IEEE 42010:2011 standard1, which is also adopted by the TOGAF standard2.
– According to the ISO/IEC/IEEE 42010:2011 standard, an architecture description is a work product
used to express an architecture, and it consists of one or more architecture views1.
– An architecture view is a representation of a system from the perspective of a related set of concerns, and it conforms to an architecture viewpoint1.
– An architecture viewpoint is a specification of the conventions for constructing and using an architecture view to address specific stakeholder concerns1.
– Therefore, the correct answer is option A, which identifies the items labeled as “A” and “B” in the image as an architecture viewpoint and an architecture view, respectively.
References:
– 1: ISO/IEC/IEEE 42010:2011 – Systems and software engineering ― Architecture description1
– 2: TOGAF Standard, Version 9.2 – Part IV: Architecture Content Framework – 31. Architectural Artifacts2
A
Explanation:
– The image shows a diagram that illustrates the basic concepts of architecture description as defined by the ISO/IEC/IEEE 42010:2011 standard1, which is also adopted by the TOGAF standard2.
– According to the ISO/IEC/IEEE 42010:2011 standard, an architecture description is a work product
used to express an architecture, and it consists of one or more architecture views1.
– An architecture view is a representation of a system from the perspective of a related set of concerns, and it conforms to an architecture viewpoint1.
– An architecture viewpoint is a specification of the conventions for constructing and using an architecture view to address specific stakeholder concerns1.
– Therefore, the correct answer is option A, which identifies the items labeled as “A” and “B” in the image as an architecture viewpoint and an architecture view, respectively.
References:
– 1: ISO/IEC/IEEE 42010:2011 – Systems and software engineering ― Architecture description1
– 2: TOGAF Standard, Version 9.2 – Part IV: Architecture Content Framework – 31. Architectural Artifacts2
Question #3
Consider the following chart:
Which important concept for Enterprise Architecture Practitioners does it illustrate?
- A . Enterprise Architects must use Gantt charts to communicate with Stakeholders.
- B . An Enterprise Architecture must be developed in phases with a limited fixed duration.
- C . ADM phases must be run in a sequenced approach to produce the Architecture.
- D . ADM phases must be run simultaneously until the relevant information has been produced.
Correct Answer: C
C
Explanation:
The chart shown is a Gantt chart, which is commonly used for project management to illustrate a project schedule. In the context of TOGAF (The Open Group Architecture Framework), which is a framework for enterprise architecture, this Gantt chart is demonstrating the sequenced approach to the Architecture Development Method (ADM). The ADM is the core process of TOGAF which provides a tested and repeatable process for developing architectures. The ADM is described as being iterative, over the whole process, between phases, and within phases. For each iteration of the ADM, a fresh decision must be taken about each of the parameters (scope, granularity, time period, and architecture assets).
The ADM consists of a number of phases that have to be followed in sequence:
– Preliminary Phase: Framework and principles
– Phase A: Architecture Vision
– Phase B: Business Architecture
– Phase C: Information Systems Architectures, including Data and Application Architectures
– Phase D: Technology Architecture
– Phase E: Opportunities and Solutions
– Phase F: Migration Planning
– Phase G: Implementation Governance
– Phase H: Architecture Change Management
– Requirements Management
Each phase is dependent on the outputs of the previous phase and the Requirements Management phase runs throughout. The Gantt chart clearly shows the dependency and sequence in which these phases occur, implying that a structured approach is followed to produce the enterprise architecture.
References:
– The TOGAF Standard, Version 9.2, a standard of The Open Group
– The TOGAF documentation available at https://publications.opengroup.org/standards/architecture and https://publications.opengroup.org/guides/architecture
C
Explanation:
The chart shown is a Gantt chart, which is commonly used for project management to illustrate a project schedule. In the context of TOGAF (The Open Group Architecture Framework), which is a framework for enterprise architecture, this Gantt chart is demonstrating the sequenced approach to the Architecture Development Method (ADM). The ADM is the core process of TOGAF which provides a tested and repeatable process for developing architectures. The ADM is described as being iterative, over the whole process, between phases, and within phases. For each iteration of the ADM, a fresh decision must be taken about each of the parameters (scope, granularity, time period, and architecture assets).
The ADM consists of a number of phases that have to be followed in sequence:
– Preliminary Phase: Framework and principles
– Phase A: Architecture Vision
– Phase B: Business Architecture
– Phase C: Information Systems Architectures, including Data and Application Architectures
– Phase D: Technology Architecture
– Phase E: Opportunities and Solutions
– Phase F: Migration Planning
– Phase G: Implementation Governance
– Phase H: Architecture Change Management
– Requirements Management
Each phase is dependent on the outputs of the previous phase and the Requirements Management phase runs throughout. The Gantt chart clearly shows the dependency and sequence in which these phases occur, implying that a structured approach is followed to produce the enterprise architecture.
References:
– The TOGAF Standard, Version 9.2, a standard of The Open Group
– The TOGAF documentation available at https://publications.opengroup.org/standards/architecture and https://publications.opengroup.org/guides/architecture
Question #4
Which of the following best summarizes the purpose of Enterprise Architecture?
- A . Taking major improvement decisions.
- B . Guiding effective change.
- C . Controlling the bigger changes.
- D . Governing the Stakeholders.
Correct Answer: B
B
Explanation:
EA applies architecture principles and practices to analyze, design, plan, and implement enterprise analysis that supports digital transformation, IT growth, and the modernization of IT2. EA also helps organizations improve the efficiency, timeliness, and reliability of business information, as well as the alignment, agility, and adaptability of the architecture to the changing needs and requirements3. Therefore, the best summary of the purpose of EA is to guide effective change.
References: 1: Enterprise architecture – Wikipedia 2: What is enterprise architecture? A framework for
transformation 3: 3 The Purpose of Enterprise Architecture – The Open Group
B
Explanation:
EA applies architecture principles and practices to analyze, design, plan, and implement enterprise analysis that supports digital transformation, IT growth, and the modernization of IT2. EA also helps organizations improve the efficiency, timeliness, and reliability of business information, as well as the alignment, agility, and adaptability of the architecture to the changing needs and requirements3. Therefore, the best summary of the purpose of EA is to guide effective change.
References: 1: Enterprise architecture – Wikipedia 2: What is enterprise architecture? A framework for
transformation 3: 3 The Purpose of Enterprise Architecture – The Open Group
Question #5
According to the TOGAF standard, what term describes an individual with an interest in a system?
- A . stakeholder
- B . consumer
- C . lead architect
- D . sponsor
Correct Answer: A
A
Explanation:
According to the TOGAF Standard, 10th Edition, a stakeholder is “an individual with an interest in a system”
A
Explanation:
According to the TOGAF Standard, 10th Edition, a stakeholder is “an individual with an interest in a system”
Question #5
According to the TOGAF standard, what term describes an individual with an interest in a system?
- A . stakeholder
- B . consumer
- C . lead architect
- D . sponsor
Correct Answer: A
A
Explanation:
According to the TOGAF Standard, 10th Edition, a stakeholder is “an individual with an interest in a system”
A
Explanation:
According to the TOGAF Standard, 10th Edition, a stakeholder is “an individual with an interest in a system”
Question #7
Refer to the table below:
Which ADM Phase does this describe?
- A . Phase A
- B . Phase B
- C . Preliminary Phase
- D . Phase C
Correct Answer: B
B
Explanation:
Phase B of the ADM cycle is the Business Architecture phase. It describes the development of a Business Architecture to support an agreed Architecture Vision. The objectives of this phase are to describe the baseline and target Business Architecture, identify candidate Architecture Roadmap components based on gaps between the baseline and target, and determine whether an incremental approach is required.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.2 Phase B: Business Architecture.
B
Explanation:
Phase B of the ADM cycle is the Business Architecture phase. It describes the development of a Business Architecture to support an agreed Architecture Vision. The objectives of this phase are to describe the baseline and target Business Architecture, identify candidate Architecture Roadmap components based on gaps between the baseline and target, and determine whether an incremental approach is required.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.2 Phase B: Business Architecture.
Question #8
What is the purpose of the Preliminary Phase?
- A . Developing an Enterprise Architecture Capability.
- B . Describing the target architecture.
- C . Defining the Enterprise Strategy.
- D . Identifying the stakeholders and their requirements.
Correct Answer: A
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
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 #9
Complete the sentence A business scenario describes______________
- A . shortfalls between the Baseline and Target Architectures
- B . business domain gaps such as cross-training requirements
- C . business and technology environment in which those problems occur
- D . general rules and guidelines tor the architecture being developed
Correct Answer: C
C
Explanation:
A business scenario describes business and technology environment in which those problems occur. It provides a realistic context for identifying and addressing business problems and opportunities, as well as their impact on the enterprise’s architecture.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.1 Business Scenarios.
C
Explanation:
A business scenario describes business and technology environment in which those problems occur. It provides a realistic context for identifying and addressing business problems and opportunities, as well as their impact on the enterprise’s architecture.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.1 Business Scenarios.
Question #10
Which of the following describes how the Enterprise Continuum is used when developing an enterprise architecture?
- A . To identify and understand business requirements
- B . To coordinate with the other management frameworks in use
- C . To describe how an architecture addresses stakeholder concerns
- D . To classify architecture and solution assets
Correct Answer: D
D
Explanation:
The Enterprise Continuum consists of two complementary concepts: the Architecture Continuum and the Solutions Continuum1. The Architecture Continuum provides a consistent way to describe and understand the generic and reusable architecture building blocks, such as models, patterns, and standards, that can be applied and tailored to specific situations2. The Solutions Continuum provides a consistent way to describe and understand the specific and implemented solution building blocks, such as products, services, and components, that realize the architecture building blocks3. The Enterprise Continuum enables the reuse and integration of architecture and solution assets across different levels of abstraction, scope, and detail, ranging from foundation architectures to organization-specific architectures1.
The Enterprise Continuum is used when developing an enterprise architecture to support the following activities1:
• Selecting relevant architecture and solution assets from the Architecture Repository or other sources, based on the business drivers, goals, and requirements
• Adapting and customizing the architecture and solution assets to suit the specific needs and context of the enterprise
• Defining and developing the target architecture and the architecture roadmap, based on the gaps and opportunities identified between the baseline and the target states
• Defining and developing the implementation and migration plan, based on the architecture roadmap and the solution building blocks
• Governing and managing the architecture and solution assets throughout the architecture lifecycle, ensuring their quality, consistency, and compliance
References: 1: The TOGAF Standard, Version 9.2 – Enterprise Continuum 2: The TOGAF Standard, Version 9.2 – Architecture Continuum 3: The TOGAF Standard, Version 9.2 – Solutions Continuum
D
Explanation:
The Enterprise Continuum consists of two complementary concepts: the Architecture Continuum and the Solutions Continuum1. The Architecture Continuum provides a consistent way to describe and understand the generic and reusable architecture building blocks, such as models, patterns, and standards, that can be applied and tailored to specific situations2. The Solutions Continuum provides a consistent way to describe and understand the specific and implemented solution building blocks, such as products, services, and components, that realize the architecture building blocks3. The Enterprise Continuum enables the reuse and integration of architecture and solution assets across different levels of abstraction, scope, and detail, ranging from foundation architectures to organization-specific architectures1.
The Enterprise Continuum is used when developing an enterprise architecture to support the following activities1:
• Selecting relevant architecture and solution assets from the Architecture Repository or other sources, based on the business drivers, goals, and requirements
• Adapting and customizing the architecture and solution assets to suit the specific needs and context of the enterprise
• Defining and developing the target architecture and the architecture roadmap, based on the gaps and opportunities identified between the baseline and the target states
• Defining and developing the implementation and migration plan, based on the architecture roadmap and the solution building blocks
• Governing and managing the architecture and solution assets throughout the architecture lifecycle, ensuring their quality, consistency, and compliance
References: 1: The TOGAF Standard, Version 9.2 – Enterprise Continuum 2: The TOGAF Standard, Version 9.2 – Architecture Continuum 3: The TOGAF Standard, Version 9.2 – Solutions Continuum
Question #11
Which of the following best describes the purpose of the Gap Analysis technique?
- A . To govern the architecture throughout its implementation process
- B . To develop a set of general rules and guidelines for the architecture
- C . To identify items omitted from the Target Architecture
- D . To allocate resources for architecture projects
Correct Answer: C
C
Explanation:
The purpose of the Gap Analysis technique is similar to the previous question, but with a focus on the Target Architecture. The technique helps to identify the items that are not included or specified in the Target Architecture, such as capabilities, services, components, standards, or technologies. These items may be essential for achieving the vision and goals of the enterprise, or for addressing the stakeholder concerns and requirements. By identifying the items omitted from the Target Architecture, the technique helps to ensure that the architecture is comprehensive, feasible, and realistic.
C
Explanation:
The purpose of the Gap Analysis technique is similar to the previous question, but with a focus on the Target Architecture. The technique helps to identify the items that are not included or specified in the Target Architecture, such as capabilities, services, components, standards, or technologies. These items may be essential for achieving the vision and goals of the enterprise, or for addressing the stakeholder concerns and requirements. By identifying the items omitted from the Target Architecture, the technique helps to ensure that the architecture is comprehensive, feasible, and realistic.
Question #11
Which of the following best describes the purpose of the Gap Analysis technique?
- A . To govern the architecture throughout its implementation process
- B . To develop a set of general rules and guidelines for the architecture
- C . To identify items omitted from the Target Architecture
- D . To allocate resources for architecture projects
Correct Answer: C
C
Explanation:
The purpose of the Gap Analysis technique is similar to the previous question, but with a focus on the Target Architecture. The technique helps to identify the items that are not included or specified in the Target Architecture, such as capabilities, services, components, standards, or technologies. These items may be essential for achieving the vision and goals of the enterprise, or for addressing the stakeholder concerns and requirements. By identifying the items omitted from the Target Architecture, the technique helps to ensure that the architecture is comprehensive, feasible, and realistic.
C
Explanation:
The purpose of the Gap Analysis technique is similar to the previous question, but with a focus on the Target Architecture. The technique helps to identify the items that are not included or specified in the Target Architecture, such as capabilities, services, components, standards, or technologies. These items may be essential for achieving the vision and goals of the enterprise, or for addressing the stakeholder concerns and requirements. By identifying the items omitted from the Target Architecture, the technique helps to ensure that the architecture is comprehensive, feasible, and realistic.
Question #11
Which of the following best describes the purpose of the Gap Analysis technique?
- A . To govern the architecture throughout its implementation process
- B . To develop a set of general rules and guidelines for the architecture
- C . To identify items omitted from the Target Architecture
- D . To allocate resources for architecture projects
Correct Answer: C
C
Explanation:
The purpose of the Gap Analysis technique is similar to the previous question, but with a focus on the Target Architecture. The technique helps to identify the items that are not included or specified in the Target Architecture, such as capabilities, services, components, standards, or technologies. These items may be essential for achieving the vision and goals of the enterprise, or for addressing the stakeholder concerns and requirements. By identifying the items omitted from the Target Architecture, the technique helps to ensure that the architecture is comprehensive, feasible, and realistic.
C
Explanation:
The purpose of the Gap Analysis technique is similar to the previous question, but with a focus on the Target Architecture. The technique helps to identify the items that are not included or specified in the Target Architecture, such as capabilities, services, components, standards, or technologies. These items may be essential for achieving the vision and goals of the enterprise, or for addressing the stakeholder concerns and requirements. By identifying the items omitted from the Target Architecture, the technique helps to ensure that the architecture is comprehensive, feasible, and realistic.
Question #14
Partnerships and alliances of businesses working together, such as a consortium or supply chain
What are those examples of according to the TOGAF Standard?
- A . Enterprises
- B . Organizations
- C . Business Units
- D . Architectures Scopes
Correct Answer: D
D
Explanation:
According to the TOGAF standard, the two statements provided refer to different scopes within which architecture can be developed:
– Groups of countries, governments, or governmental organizations working together typically align with broader, often international, scopes of architecture that transcend individual enterprise boundaries.
– Partnerships and alliances of businesses working together, such as a consortium or supply chain, refer to collaborative efforts that can define architecture at a scope involving multiple enterprises.
In both cases, the term "Architectures Scopes" is appropriate because it reflects the varying levels and contexts in which architectures can be defined, ranging from single business units to collaborative inter-organizational efforts.
D
Explanation:
According to the TOGAF standard, the two statements provided refer to different scopes within which architecture can be developed:
– Groups of countries, governments, or governmental organizations working together typically align with broader, often international, scopes of architecture that transcend individual enterprise boundaries.
– Partnerships and alliances of businesses working together, such as a consortium or supply chain, refer to collaborative efforts that can define architecture at a scope involving multiple enterprises.
In both cases, the term "Architectures Scopes" is appropriate because it reflects the varying levels and contexts in which architectures can be defined, ranging from single business units to collaborative inter-organizational efforts.
Question #15
Which of the following best describes purpose of the Business Scenarios?
- A . To identify risk when implementing an architecture project
- B . To identify and understand requirements
- C . To catch errors in a project architecture early
- D . To guide decision making throughout the enterprise
Correct Answer: B
B
Explanation:
Business scenarios are a technique for capturing, clarifying, and communicating the functional and non-functional requirements of a system. Business scenarios describe the business environment, the actors involved, the desired outcomes, and the processes or rules that govern the behavior of the system. Business scenarios are useful for ensuring that the architecture addresses the real needs and concerns of the stakeholders, and for validating and testing the architecture against expected situations. Business scenarios are developed in Phase A: Architecture Vision of the ADM cycle, and refined and updated throughout the other phases3 References: 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 26: Business Scenarios: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision
B
Explanation:
Business scenarios are a technique for capturing, clarifying, and communicating the functional and non-functional requirements of a system. Business scenarios describe the business environment, the actors involved, the desired outcomes, and the processes or rules that govern the behavior of the system. Business scenarios are useful for ensuring that the architecture addresses the real needs and concerns of the stakeholders, and for validating and testing the architecture against expected situations. Business scenarios are developed in Phase A: Architecture Vision of the ADM cycle, and refined and updated throughout the other phases3 References: 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 26: Business Scenarios: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision
Question #16
Which of the following supports the need to govern Enterprise Architecture?
- A . The Architecture Project mandates the governance of the target architecture
- B . The TOGAF standard cannot be used without executive governance
- C . Best practice governance enables the organization to control value realization
- D . The Stakeholders preferences may go beyond the architecture project scope and needs control
Correct Answer: C
C
Explanation:
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.
C
Explanation:
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.
Question #17
What are the four architecture domains that the TOGAF standard deals with?
- A . Business, Data, Application, Technology
- B . Capability, Segment, Enterprise, Federated
- C . Baseline, Candidate, Transition, Target
- D . Application, Data, Information, Knowledge
Correct Answer: A
A
Explanation:
The TOGAF standard divides Enterprise Architecture into four primary architecture domains: business, data, application, and technology. These domains represent different aspects of an enterprise and how they relate to each other. The business domain defines the business strategy, governance, organization, and key business processes. The data domain describes the structure of the logical and physical data assets and data management resources. The application domain provides a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes. The technology domain describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. Other domains, such as motivation, security, or governance, may span across these four primary domains.
References:
– The TOGAF Standard, Version 9.2 – Core Concepts
– Domains – The Open Group
– TOGAF® Standard ― Introduction – Definitions – The Open Group
– The TOGAF Standard, Version 9.2 – Definitions – The Open Group
– TOGAF and the history of enterprise architecture | Enable Architect
A
Explanation:
The TOGAF standard divides Enterprise Architecture into four primary architecture domains: business, data, application, and technology. These domains represent different aspects of an enterprise and how they relate to each other. The business domain defines the business strategy, governance, organization, and key business processes. The data domain describes the structure of the logical and physical data assets and data management resources. The application domain provides a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes. The technology domain describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. Other domains, such as motivation, security, or governance, may span across these four primary domains.
References:
– The TOGAF Standard, Version 9.2 – Core Concepts
– Domains – The Open Group
– TOGAF® Standard ― Introduction – Definitions – The Open Group
– The TOGAF Standard, Version 9.2 – Definitions – The Open Group
– TOGAF and the history of enterprise architecture | Enable Architect
Question #18
Exhibit
Consider the illustration showing an architecture development cycle Which description matches the phase of the ADM labeled as item 1?
- A . Conducts implementation planning for the architecture defined in previous phases
- B . Provides architectural oversight for the implementation
- C . Operates the process of managing architecture requirements
- D . Establishes procedures for managing change to the new architecture
Correct Answer: C
C
Explanation:
– The illustration shows an architecture development cycle based on 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.
– In addition to these phases, there is a central process called Requirements Management, which is labeled as item 1 in the illustration. This process operates throughout the ADM cycle, and its purpose is to manage the architecture requirements throughout the architecture development, ensuring that they are aligned with the business requirements and the stakeholder concerns2.
– Therefore, the description that matches the phase of the ADM labeled as item 1 is
C. Operates the process of managing architecture requirements.
References:
1: The TOGAF Standard, Version 9.2, Chapter 5: Architecture Development Method (ADM)
2: The TOGAF Standard, Version 9.2, Chapter 17: Requirements Management
C
Explanation:
– The illustration shows an architecture development cycle based on 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.
– In addition to these phases, there is a central process called Requirements Management, which is labeled as item 1 in the illustration. This process operates throughout the ADM cycle, and its purpose is to manage the architecture requirements throughout the architecture development, ensuring that they are aligned with the business requirements and the stakeholder concerns2.
– Therefore, the description that matches the phase of the ADM labeled as item 1 is
C. Operates the process of managing architecture requirements.
References:
1: The TOGAF Standard, Version 9.2, Chapter 5: Architecture Development Method (ADM)
2: The TOGAF Standard, Version 9.2, Chapter 17: Requirements Management
Question #19
When considering the scope of an architecture, what dimension considers to what level of detail the architecting effort should go?
- A . Project
- B . Breadth
- C . Depth
- D . Architecture Domains
Correct Answer: C
C
Explanation:
The scope of an architecture is the extent and level of detail of the architecture work. The scope of an architecture can be defined along four dimensions: project, breadth, depth, and architecture domains. The project dimension considers the boundaries and objectives of the architecture project, such as the time frame, budget, resources, and deliverables. The breadth dimension considers the coverage and completeness of the architecture across the enterprise, such as the organizational units, business functions, processes, and locations. The depth dimension considers the level of detail and specificity of the architecture, such as the granularity, abstraction, and precision of the architectural elements and relationships. The architecture domains dimension considers the aspects or segments of the architecture, such as the business, data, application, and technology domains.
Therefore, the depth dimension is the one that considers to what level of detail the architecting effort should go.
References: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 25: Architecture Scope: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 25.2: Scope Dimensions: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 25.2.1: Project, Breadth, Depth, and Architecture Domains
C
Explanation:
The scope of an architecture is the extent and level of detail of the architecture work. The scope of an architecture can be defined along four dimensions: project, breadth, depth, and architecture domains. The project dimension considers the boundaries and objectives of the architecture project, such as the time frame, budget, resources, and deliverables. The breadth dimension considers the coverage and completeness of the architecture across the enterprise, such as the organizational units, business functions, processes, and locations. The depth dimension considers the level of detail and specificity of the architecture, such as the granularity, abstraction, and precision of the architectural elements and relationships. The architecture domains dimension considers the aspects or segments of the architecture, such as the business, data, application, and technology domains.
Therefore, the depth dimension is the one that considers to what level of detail the architecting effort should go.
References: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 25: Architecture Scope: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 25.2: Scope Dimensions: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 25.2.1: Project, Breadth, Depth, and Architecture Domains
Question #20
What is presented as ”striking a balance between positive and negative outcomes resulting from the realization of either opportunities or threats?
- A . Agile development
- B . Architecture Security
- C . Transition Management
- D . Risk Management
Correct Answer: D
D
Explanation:
Risk Management is the process of identifying, assessing, and responding to risks that may affect the achievement of the enterprise’s objectives. Risk Management involves balancing positive and negative outcomes resulting from the realization of either opportunities or threats.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.3 Risk Management.
D
Explanation:
Risk Management is the process of identifying, assessing, and responding to risks that may affect the achievement of the enterprise’s objectives. Risk Management involves balancing positive and negative outcomes resulting from the realization of either opportunities or threats.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.3 Risk Management.
Question #21
Which of the following best describes the purpose of the Architecture Roadmap?
- A . It provides for effective communication of the end architecture project to the stakeholders
- B . It is sent from the sponsor and triggers the start of an architecture development cycle
- C . It forms the basis of a contractual agreement between the sponsor and the architecture organization
- D . It lists work packages on a timeline showing progress towards the Target Architecture
Correct Answer: D
D
Explanation:
The purpose of the Architecture Roadmap is to provide a high-level view of how the Baseline Architecture will transition to the Target Architecture over time. It lists work packages on a timeline showing progress towards the Target Architecture, as well as dependencies, risks, and benefits. The Architecture Roadmap forms part of the Implementation and Migration Plan and guides the execution of the architecture projects.
References: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap20.html
D
Explanation:
The purpose of the Architecture Roadmap is to provide a high-level view of how the Baseline Architecture will transition to the Target Architecture over time. It lists work packages on a timeline showing progress towards the Target Architecture, as well as dependencies, risks, and benefits. The Architecture Roadmap forms part of the Implementation and Migration Plan and guides the execution of the architecture projects.
References: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap20.html
Question #22
Which of the following best describes the purpose of the Architecture Requirements Specification?
- A . It contains an assessment of the current architecture requirements
- B . It provides a set of statements that outline what a project must do to comply with the architecture
- C . It is sent from the sponsor and triggers the start of an architecture development cycle
- D . It defines the scope and approach to complete an architecture project
Correct Answer: B
B
Explanation:
The Architecture Requirements Specification is one of the TOGAF deliverables that provides a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture12. It is a companion to the Architecture Definition Document, which provides a qualitative view of the solution and aims to communicate the intent of the architect. The Architecture Requirements
Specification provides a quantitative view of the solution, stating measurable criteria that must be met during the implementation of the architecture3. It typically forms a major component of an implementation contract or contract for more detailed Architecture Definition4.
References:
• Deliverable: Architecture Requirements Specification – The Open Group
• Architecture Requirements Specification – Visual Paradigm Community Circle
• The TOGAF Standard, Version 9.2 – Definitions – The Open Group
• The TOGAF Standard, Version 9.2 – Architecture Requirements Specification – The Open Group
B
Explanation:
The Architecture Requirements Specification is one of the TOGAF deliverables that provides a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture12. It is a companion to the Architecture Definition Document, which provides a qualitative view of the solution and aims to communicate the intent of the architect. The Architecture Requirements
Specification provides a quantitative view of the solution, stating measurable criteria that must be met during the implementation of the architecture3. It typically forms a major component of an implementation contract or contract for more detailed Architecture Definition4.
References:
• Deliverable: Architecture Requirements Specification – The Open Group
• Architecture Requirements Specification – Visual Paradigm Community Circle
• The TOGAF Standard, Version 9.2 – Definitions – The Open Group
• The TOGAF Standard, Version 9.2 – Architecture Requirements Specification – The Open Group
Question #23
Which section of the TOGAF template for Architecture Principles should highlight the business benefits of adhering to the principle?
- A . Rationale
- B . Name
- C . Implications
- D . Statement
Correct Answer: A
A
Explanation:
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”
A
Explanation:
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”
Question #23
Which section of the TOGAF template for Architecture Principles should highlight the business benefits of adhering to the principle?
- A . Rationale
- B . Name
- C . Implications
- D . Statement
Correct Answer: A
A
Explanation:
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”
A
Explanation:
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”
Question #25
Complete the sentence Business Transformation Readiness Assessment is_________________.
- A . a joint effort between corporate staff lines of business and IT planners
- B . to ensure the active support of powerful stakeholders
- C . a way to put building blocks into context thereby supporting re-usable solutions
- D . widely used to validate an architecture that is being developed
Correct Answer: A
A
Explanation:
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.
A
Explanation:
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.
Question #26
Exhibit:
Consider the illustration.
What are the items labelled A, B, and C?
- A . A-Enterprise Repository, B-Governance Repository, C-Board Repository
- B . A-Architecture Repository, B-Governance Repository, C-Architecture Capability
- C . A-Architecture Repository, B-Governing Board, C-Enterprise Capability
- D . A-Enterprise Repository, B-Board repository, C-Enterprise Capability
Correct Answer: C
C
Explanation:
A-Architecture Repository: This is a part of the Architecture Metamodel that contains artifacts structured according to the metamodel. It includes the Architecture Landscape which is adopted by the enterprise and governed by certain standards and practices.
B-Governing Board: The Governing Board ensures visibility and escalation, meaning it oversees and manages the capability of the architecture landscape. It plays a crucial role in governance.
C-Enterprise Capability: This refers to how well an enterprise can execute its mission, meet business objectives or satisfy its stakeholders’ needs and expectations. It’s influenced by both internal factors (like resources, processes) and external ones (like market trends).
References: TOGAF Version 9.1, Chapter 34: 1
C
Explanation:
A-Architecture Repository: This is a part of the Architecture Metamodel that contains artifacts structured according to the metamodel. It includes the Architecture Landscape which is adopted by the enterprise and governed by certain standards and practices.
B-Governing Board: The Governing Board ensures visibility and escalation, meaning it oversees and manages the capability of the architecture landscape. It plays a crucial role in governance.
C-Enterprise Capability: This refers to how well an enterprise can execute its mission, meet business objectives or satisfy its stakeholders’ needs and expectations. It’s influenced by both internal factors (like resources, processes) and external ones (like market trends).
References: TOGAF Version 9.1, Chapter 34: 1
Question #27
Which of the following best describes the need for the ADM process to be governed?
- A . To enable development of reference architectures
- B . To verify that the method is being applied correctly
- C . To enable a fast response to market changes
- D . To permit the architecture domains to be integrated
Correct Answer: B
B
Explanation:
According to the TOGAF standard, the need for the ADM process to be governed is to ensure that the architecture development and implementation activities are conducted in a consistent, coherent, and compliant manner1. Governance provides the means to verify that the method is being applied correctly and effectively, and that the architecture deliverables and artifacts meet the quality and standards criteria1. Governance also enables the management of risks, issues, changes, and dependencies that may arise during the ADM process1.
Some of the benefits of governing the ADM process are2:
• Improved alignment of the architecture with the business strategy and objectives
• Enhanced stakeholder engagement and communication
• Increased reuse and integration of architecture assets and resources
• Reduced complexity and duplication of architecture efforts
• Increased agility and adaptability of the architecture to changing needs and requirements
• Improved compliance and auditability of the architecture outcomes and outputs
References: 1: Architecture Governance 2: Architecture Governance Benefits
B
Explanation:
According to the TOGAF standard, the need for the ADM process to be governed is to ensure that the architecture development and implementation activities are conducted in a consistent, coherent, and compliant manner1. Governance provides the means to verify that the method is being applied correctly and effectively, and that the architecture deliverables and artifacts meet the quality and standards criteria1. Governance also enables the management of risks, issues, changes, and dependencies that may arise during the ADM process1.
Some of the benefits of governing the ADM process are2:
• Improved alignment of the architecture with the business strategy and objectives
• Enhanced stakeholder engagement and communication
• Increased reuse and integration of architecture assets and resources
• Reduced complexity and duplication of architecture efforts
• Increased agility and adaptability of the architecture to changing needs and requirements
• Improved compliance and auditability of the architecture outcomes and outputs
References: 1: Architecture Governance 2: Architecture Governance Benefits
Question #28
Complete the following sentence. In the ADM documents which are under development and have not undergone any formal review and approval process are_______________.
- A . Called ‘’draft’’
- B . Invalid
- C . In between phases
- D . Known as ‘’Version 0.1’’
Correct Answer: A
A
Explanation:
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.
A
Explanation:
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.
Question #28
Complete the following sentence. In the ADM documents which are under development and have not undergone any formal review and approval process are_______________.
- A . Called ‘’draft’’
- B . Invalid
- C . In between phases
- D . Known as ‘’Version 0.1’’
Correct Answer: A
A
Explanation:
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.
A
Explanation:
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.
Question #28
Complete the following sentence. In the ADM documents which are under development and have not undergone any formal review and approval process are_______________.
- A . Called ‘’draft’’
- B . Invalid
- C . In between phases
- D . Known as ‘’Version 0.1’’
Correct Answer: A
A
Explanation:
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.
A
Explanation:
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.
Question #28
Complete the following sentence. In the ADM documents which are under development and have not undergone any formal review and approval process are_______________.
- A . Called ‘’draft’’
- B . Invalid
- C . In between phases
- D . Known as ‘’Version 0.1’’
Correct Answer: A
A
Explanation:
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.
A
Explanation:
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.
Question #28
Complete the following sentence. In the ADM documents which are under development and have not undergone any formal review and approval process are_______________.
- A . Called ‘’draft’’
- B . Invalid
- C . In between phases
- D . Known as ‘’Version 0.1’’
Correct Answer: A
A
Explanation:
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.
A
Explanation:
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.
Question #33
Digital Transformation and operations will be more effective and efficient.
Which statements highlight the value and necessity for Architecture Governance to be adopted within organizations?
- A . 1 & 4
- B . 1 & 3
- C . 2 & 4
- D . 2& 3
Correct Answer: B
B
Explanation:
Statements 1 and 3 highlight the value and necessity for Architecture Governance to be adopted within organizations. Architecture Governance is the practice and orientation by which Enterprise Architectures and other architectures are managed and controlled at an enterprise-wide level12. It ensures that architectural decisions are aligned with the organization’s strategy, objectives, and standards. Architecture Governance also involves establishing and maintaining processes, decision-making, and mechanisms to avoid or minimize potential conflicts of interest, such as between different stakeholders, business units, or projects34. Moreover, Architecture Governance requires transparency and accountability for all actions implemented and their decision support, so that they can be inspected and evaluated by authorized parties, such as auditors, regulators, or customers5.
References:
• The TOGAF Standard, Version 9.2 – Architecture Governance – The Open Group
• Architecture Governance – The Open Group
• Tutorial: Governance in TOGAF’s Architecture Development Method (ADM)
• Architecture Governance in TOGAF: Ensuring Effective Management and Compliance
• The TOGAF Standard, Version 9.2 – Definitions – The Open Group
• [Architecture Governance in TOGAF: Ensuring Alignment and Control]
B
Explanation:
Statements 1 and 3 highlight the value and necessity for Architecture Governance to be adopted within organizations. Architecture Governance is the practice and orientation by which Enterprise Architectures and other architectures are managed and controlled at an enterprise-wide level12. It ensures that architectural decisions are aligned with the organization’s strategy, objectives, and standards. Architecture Governance also involves establishing and maintaining processes, decision-making, and mechanisms to avoid or minimize potential conflicts of interest, such as between different stakeholders, business units, or projects34. Moreover, Architecture Governance requires transparency and accountability for all actions implemented and their decision support, so that they can be inspected and evaluated by authorized parties, such as auditors, regulators, or customers5.
References:
• The TOGAF Standard, Version 9.2 – Architecture Governance – The Open Group
• Architecture Governance – The Open Group
• Tutorial: Governance in TOGAF’s Architecture Development Method (ADM)
• Architecture Governance in TOGAF: Ensuring Effective Management and Compliance
• The TOGAF Standard, Version 9.2 – Definitions – The Open Group
• [Architecture Governance in TOGAF: Ensuring Alignment and Control]
Question #34
Consider the following ADM phases objectives.
Which phase does each objective match?
- A . 1C-2B-3A-4C
- B . 1A-2B-3C-4D
- C . 1B-2D-3A-4C
- D . 1C-2D-3B-4A
Correct Answer: A
A
Explanation:
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
A
Explanation:
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 #35
Complete the sentence. When considering agile development, Architecture to Support Portfolio will identify what products the Enterprise needs, the boundary of the products, and what constraints a product owner has; this defines the Enterprise’s
- A . risk tolerance
- B . business continuity
- C . backlog
- D . operating model
Correct Answer: C
C
Explanation:
When considering agile development, Architecture to Support Portfolio will identify the necessary products for the enterprise, define their boundaries, and outline the constraints for a product owner. This process directly relates to defining the enterprise’s backlog, which in agile methodologies, is a prioritized list of work for the development team that is derived from the roadmap and its requirements.
C
Explanation:
When considering agile development, Architecture to Support Portfolio will identify the necessary products for the enterprise, define their boundaries, and outline the constraints for a product owner. This process directly relates to defining the enterprise’s backlog, which in agile methodologies, is a prioritized list of work for the development team that is derived from the roadmap and its requirements.
Question #36
Complete the sentence A set of architecture principles that cover every situation perceived meets the recommended criteria of_______________
- A . consistency
- B . robustness
- C . stability
- D . completeness
Correct Answer: D
D
Explanation:
A set of architecture principles that cover every situation perceived meets the recommended criteria of completeness. Completeness is one of the six criteria that should be applied when developing or assessing architecture principles. Completeness means that there are no gaps or overlaps in the coverage of principles across all relevant aspects of the enterprise’s architecture.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.7 Architecture Principles.
D
Explanation:
A set of architecture principles that cover every situation perceived meets the recommended criteria of completeness. Completeness is one of the six criteria that should be applied when developing or assessing architecture principles. Completeness means that there are no gaps or overlaps in the coverage of principles across all relevant aspects of the enterprise’s architecture.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.7 Architecture Principles.
Question #37
Which of the following statements about architecture partitioning are correct*?
1 Partitions are used to simplify the management of the Enterprise Architecture
2 Partitions are equivalent to architecture levels
3 Partitions enable different teams to work on different element of the architecture at the same time.
4 Partitions reflect the organization’s structure
- A . 2 & 3
- B . 1 & 3
- C . 1 & 4
- D . 2 & 4
Correct Answer: B
B
Explanation:
Statements 1 and 3 about architecture partitioning are correct. Architecture partitioning is the technique of dividing an architecture into smaller and more manageable parts that can be developed, maintained, and governed independently. Partitions are used to simplify the management of the Enterprise Architecture and to enable different teams to work on different elements of the architecture at the same time. Partitions are not equivalent to architecture levels, which are different degrees of abstraction or detail in an architecture. Partitions do not necessarily reflect the organization’s structure, which may change over time or differ from the architecture’s scope and boundaries.
Reference: The TOGAF® Standard | The Open Group Website, Section 2.5 Architecture Partitioning.
B
Explanation:
Statements 1 and 3 about architecture partitioning are correct. Architecture partitioning is the technique of dividing an architecture into smaller and more manageable parts that can be developed, maintained, and governed independently. Partitions are used to simplify the management of the Enterprise Architecture and to enable different teams to work on different elements of the architecture at the same time. Partitions are not equivalent to architecture levels, which are different degrees of abstraction or detail in an architecture. Partitions do not necessarily reflect the organization’s structure, which may change over time or differ from the architecture’s scope and boundaries.
Reference: The TOGAF® Standard | The Open Group Website, Section 2.5 Architecture Partitioning.
Question #38
Consider the following statement:
According to the TOGAF Standard a governed approach of a particular deliverable will ensure a system of continuous monitoring to check integrity changes decision-making and audit of all architecture-related activities
Which deliverable is being referred to?
- A . An Architecture Contract
- B . The Architecture Definition Document
- C . The Architecture Vision
- D . The Statement of Architecture Work
Correct Answer: A
A
Explanation:
An Architecture Contract is a deliverable that specifies the responsibilities and obligations of the parties involved in the implementation and governance of an architecture. It ensures a system of continuous monitoring to check integrity changes decision-making and audit of all architecture-related activities.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.4 Architecture Contracts.
A
Explanation:
An Architecture Contract is a deliverable that specifies the responsibilities and obligations of the parties involved in the implementation and governance of an architecture. It ensures a system of continuous monitoring to check integrity changes decision-making and audit of all architecture-related activities.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.4 Architecture Contracts.
Question #39
Complete the sentence. The architecture domains that are considered by the TOGAF standard as subsets of an overall enterprise architecture are Business, Technology,
- A . Logical and Physical
- B . Information and Data
- C . Capability and Segment
- D . Application and Data
Correct Answer: D
D
Explanation:
These domains provide a consistent way to describe and understand the architecture from different perspectives, such as business, information, and technology12. Each domain has its own set of concepts, models, views, and artifacts that define the structure and behavior of the architecture within that domain12.
The other options are incorrect because:
• Logical and Physical are not architecture domains, but rather levels of abstraction that can be applied to any domain. Logical architecture describes the functionality and behavior of the system, while physical architecture describes the implementation and deployment of the system3.
• Information and Data are not distinct architecture domains, but rather aspects of the same domain. Information architecture describes the meaning and context of the data, while data architecture describes the structure and format of the data4.
• Capability and Segment are not architecture domains, but rather levels of granularity that can be applied to any domain. Capability architecture describes the current and desired states of a specific business capability, while segment architecture describes a subdivision of the enterprise that has a clear business focus5.
References:
1: The TOGAF Standard, Version 9.2 – Definitions 2: TOGAF® Standard ― Introduction – Definitions 3: [Logical vs Physical Architecture] 4: [Information Architecture vs Data Architecture] 5: [The TOGAF Standard, Version 9.2 – Applying the ADM Across the Architecture Landscape]
D
Explanation:
These domains provide a consistent way to describe and understand the architecture from different perspectives, such as business, information, and technology12. Each domain has its own set of concepts, models, views, and artifacts that define the structure and behavior of the architecture within that domain12.
The other options are incorrect because:
• Logical and Physical are not architecture domains, but rather levels of abstraction that can be applied to any domain. Logical architecture describes the functionality and behavior of the system, while physical architecture describes the implementation and deployment of the system3.
• Information and Data are not distinct architecture domains, but rather aspects of the same domain. Information architecture describes the meaning and context of the data, while data architecture describes the structure and format of the data4.
• Capability and Segment are not architecture domains, but rather levels of granularity that can be applied to any domain. Capability architecture describes the current and desired states of a specific business capability, while segment architecture describes a subdivision of the enterprise that has a clear business focus5.
References:
1: The TOGAF Standard, Version 9.2 – Definitions 2: TOGAF® Standard ― Introduction – Definitions 3: [Logical vs Physical Architecture] 4: [Information Architecture vs Data Architecture] 5: [The TOGAF Standard, Version 9.2 – Applying the ADM Across the Architecture Landscape]
Question #40
Consider the following statement:
Separate projects may operate their own ADM cycles concurrently, with relationships between the different projects
What does it illustrate?
- A . Implementation governance
- B . Enterprise Architecture
- C . Iteration
- D . Requirements management
Correct Answer: C
C
Explanation:
The statement illustrates iteration and the ADM. Iteration is the technique of repeating a process or a phase with the aim of improving or refining the outcome. Iteration allows for feedback loops and adaptations at any point in the architecture development and transition process. Separate projects may operate their own ADM cycles concurrently, with relationships between the different projects, to address different aspects or levels of the architecture in an iterative manner.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.1 Introduction to the ADM.
C
Explanation:
The statement illustrates iteration and the ADM. Iteration is the technique of repeating a process or a phase with the aim of improving or refining the outcome. Iteration allows for feedback loops and adaptations at any point in the architecture development and transition process. Separate projects may operate their own ADM cycles concurrently, with relationships between the different projects, to address different aspects or levels of the architecture in an iterative manner.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.1 Introduction to the ADM.
Question #41
Consider the following ADM phases objectives.
Objective
1-Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value
2-Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D
3-Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan
4-Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders
Which phase does each objective match?
- A . 1E-2F-3E-4F
- B . 1G-2E-3F-4F
- C . 1E-2E-3F-4F
- D . 1F-2E-3F-4G
Correct Answer: B
B
Explanation:
According to the TOGAF standard, the objectives of each ADM phase are as follows1:
• Phase E: Opportunities and Solutions
– Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value
– Identify and group major work packages within the Architecture Roadmap
– Identify and group major implementation projects to realize the Architecture Roadmap oIdentify dependencies between increments and projects
– Estimate cost, benefit, and risk at a high level for each increment and project oConduct initial prioritization and sequencing of the Architecture Roadmap and projects • Phase F: Migration Planning
– Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D
– Confirm the Transition Architectures with relevant stakeholders
– Create the Implementation and Migration Plan, including Transition Architectures, work packages, projects, and other activities
– Confirm and agree the Architecture Roadmap and Implementation and Migration Plan with relevant stakeholders
• Phase G: Implementation Governance
– Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan oEnsure conformance with the Target Architecture by implementation projects
– Perform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests
– Ensure that the architecture lifecycle is maintained
– Ensure that the Architecture Governance Framework is executed • Phase H: Architecture Change Management
– Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders
– Manage risks and issues related to the Architecture Roadmap and Implementation and Migration Plan – Monitor the implementation projects and Transition Architectures
– Manage changes to the architecture baseline
– Manage changes to the Architecture Capability
Therefore, the correct matching of the objectives and the phases is:
• 1G: Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value
• 2E: Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D
• 3F: Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan
• 4F: Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders
References: 1: The TOGAF Architecture Development Method
B
Explanation:
According to the TOGAF standard, the objectives of each ADM phase are as follows1:
• Phase E: Opportunities and Solutions
– Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value
– Identify and group major work packages within the Architecture Roadmap
– Identify and group major implementation projects to realize the Architecture Roadmap oIdentify dependencies between increments and projects
– Estimate cost, benefit, and risk at a high level for each increment and project oConduct initial prioritization and sequencing of the Architecture Roadmap and projects • Phase F: Migration Planning
– Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D
– Confirm the Transition Architectures with relevant stakeholders
– Create the Implementation and Migration Plan, including Transition Architectures, work packages, projects, and other activities
– Confirm and agree the Architecture Roadmap and Implementation and Migration Plan with relevant stakeholders
• Phase G: Implementation Governance
– Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan oEnsure conformance with the Target Architecture by implementation projects
– Perform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests
– Ensure that the architecture lifecycle is maintained
– Ensure that the Architecture Governance Framework is executed • Phase H: Architecture Change Management
– Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders
– Manage risks and issues related to the Architecture Roadmap and Implementation and Migration Plan – Monitor the implementation projects and Transition Architectures
– Manage changes to the architecture baseline
– Manage changes to the Architecture Capability
Therefore, the correct matching of the objectives and the phases is:
• 1G: Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value
• 2E: Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D
• 3F: Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan
• 4F: Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders
References: 1: The TOGAF Architecture Development Method
Question #42
Complete the sentence The purpose of Enterprise Architecture is to_______________.
- A . take major improvement decisions
- B . control the bigger changes
- C . guide effective change
- D . govern the stakeholders
Correct Answer: C
C
Explanation:
The purpose of Enterprise Architecture is to guide effective change by providing a coherent and consistent view of the enterprise’s current and future state, as well as the roadmap and principles for achieving it. Enterprise Architecture helps to align business and IT strategies, optimize resources and investments, reduce complexity and risks, enhance agility and innovation, and deliver value to stakeholders.
Reference: The TOGAF® Standard | The Open Group Website, Section 1.3 Executive Overview.
C
Explanation:
The purpose of Enterprise Architecture is to guide effective change by providing a coherent and consistent view of the enterprise’s current and future state, as well as the roadmap and principles for achieving it. Enterprise Architecture helps to align business and IT strategies, optimize resources and investments, reduce complexity and risks, enhance agility and innovation, and deliver value to stakeholders.
Reference: The TOGAF® Standard | The Open Group Website, Section 1.3 Executive Overview.
Question #43
What can architects present to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture?
- A . Solutions and Applications
- B . Alternatives and Trade-offs
- C . Business Scenarios and Business Models
- D . Architecture Views and Architecture Viewpoints
Correct Answer: D
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
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
Question #44
What is an objective of the ADM Implementation Governance Phase?
- A . To provide continual monitoring of the governance framework
- B . To ensure conformance for the target architecture
- C . To finalize the Implementation and Migration Plan
- D . To establish the resources for architecture governance
Correct Answer: B
B
Explanation:
The objective of the ADM Implementation Governance Phase is to provide an architectural oversight of the implementation and to ensure conformance for the target architecture. This phase involves establishing procedures and processes to monitor and control the implementation projects and to verify that they comply with the defined architecture.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.7 Phase G: Implementation Governance.
B
Explanation:
The objective of the ADM Implementation Governance Phase is to provide an architectural oversight of the implementation and to ensure conformance for the target architecture. This phase involves establishing procedures and processes to monitor and control the implementation projects and to verify that they comply with the defined architecture.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.7 Phase G: Implementation Governance.
Question #45
Which section of the TOGAF template for Architecture Principles should highlight the requirements for carrying out the principle?
- A . Rationale
- B . Name
- C . Statement
- D . Implications
Correct Answer: D
D
Explanation:
The Implications section describes the impact of adhering to the principle on the organization, the processes, the information systems, and the technology23. It also identifies the changes, costs, and risks that may result from applying the principle23. The Implications section helps to communicate the benefits and consequences of the principle to the stakeholders and to guide the implementation and governance of the architecture23.
The other sections of the TOGAF template for Architecture Principles are1:
• Name: This section provides a short and memorable name for the principle that represents its essence and purpose23. The name should not mention any specific technology or solution23.
• Statement: This section provides a concise and formal definition of the principle that expresses the fundamental rule or constraint that the principle imposes23. The statement should be clear, unambiguous, and testable23.
• Rationale: This section provides the reasoning and justification for the principle, explaining why it is important and how it supports the business goals and drivers23. The rationale should also link the principle to the higher-level enterprise or IT principles that it elaborates on23.
References: 2: The TOGAF Standard, Version 9.2 – Architecture Principles 3: TOGAF 8.1.1 Online – Architecture Principles 1: Architecture Principles Template
D
Explanation:
The Implications section describes the impact of adhering to the principle on the organization, the processes, the information systems, and the technology23. It also identifies the changes, costs, and risks that may result from applying the principle23. The Implications section helps to communicate the benefits and consequences of the principle to the stakeholders and to guide the implementation and governance of the architecture23.
The other sections of the TOGAF template for Architecture Principles are1:
• Name: This section provides a short and memorable name for the principle that represents its essence and purpose23. The name should not mention any specific technology or solution23.
• Statement: This section provides a concise and formal definition of the principle that expresses the fundamental rule or constraint that the principle imposes23. The statement should be clear, unambiguous, and testable23.
• Rationale: This section provides the reasoning and justification for the principle, explaining why it is important and how it supports the business goals and drivers23. The rationale should also link the principle to the higher-level enterprise or IT principles that it elaborates on23.
References: 2: The TOGAF Standard, Version 9.2 – Architecture Principles 3: TOGAF 8.1.1 Online – Architecture Principles 1: Architecture Principles Template
Question #46
Complete the sentence The Enterprise Continuum provides methods for classifying architecture artifacts as they evolve from________________________.
- A . Solutions Architectures to Solution Building Blocks
- B . generic architectures to reusable Solution Building Blocks
- C . Foundation Architectures to re-usable architecture assets
- D . generic architectures to Organization-Specific Architectures
Correct Answer: D
D
Explanation:
The Enterprise Continuum provides methods for classifying architecture artifacts as they evolve from generic architectures to Organization-Specific Architectures. Generic architectures are architectures that have been developed for use across a wide range of enterprises with similar characteristics. They provide common models, functions, and services that can be reused and adapted for specific purposes. Organization-Specific Architectures are architectures that have been tailored to meet the needs and requirements of a particular enterprise or a major organizational unit within an enterprise. They reflect the unique vision, goals, culture, structure, processes, systems, and technologies of that enterprise or unit.
Reference: The TOGAF® Standard | The Open Group Website, Section 2.3 Enterprise Continuum.
D
Explanation:
The Enterprise Continuum provides methods for classifying architecture artifacts as they evolve from generic architectures to Organization-Specific Architectures. Generic architectures are architectures that have been developed for use across a wide range of enterprises with similar characteristics. They provide common models, functions, and services that can be reused and adapted for specific purposes. Organization-Specific Architectures are architectures that have been tailored to meet the needs and requirements of a particular enterprise or a major organizational unit within an enterprise. They reflect the unique vision, goals, culture, structure, processes, systems, and technologies of that enterprise or unit.
Reference: The TOGAF® Standard | The Open Group Website, Section 2.3 Enterprise Continuum.
Question #47
Complete the sentence The Architecture Landscape is divided into levels known as__________________________.
- A . Gaps Plateaus, and Target Architectures
- B . Baseline. Transition and To Be Architectures
- C . Segment Strategic and Capability Architectures
- D . Transitional Complete and incremental Architectures
Correct Answer: C
C
Explanation:
The Architecture Landscape is divided into levels known as Segment Strategic and Capability Architectures. These levels correspond to different scopes and purposes of architectures within an enterprise.
Segment
Architectures are architectures that address specific business units, functions, or processes within an enterprise. Strategic Architectures are architectures that provide a high-level view of the enterprise’s vision, goals, and direction. Capability Architectures are architectures that address specific business capabilities or services that span multiple segments or domains.
Reference: The TOGAF® Standard | The Open Group Website, Section 2.4 Architecture Repository.
C
Explanation:
The Architecture Landscape is divided into levels known as Segment Strategic and Capability Architectures. These levels correspond to different scopes and purposes of architectures within an enterprise.
Segment
Architectures are architectures that address specific business units, functions, or processes within an enterprise. Strategic Architectures are architectures that provide a high-level view of the enterprise’s vision, goals, and direction. Capability Architectures are architectures that address specific business capabilities or services that span multiple segments or domains.
Reference: The TOGAF® Standard | The Open Group Website, Section 2.4 Architecture Repository.
Question #48
In which phase of the ADM cycle do building blocks become implementation-specific?
- A . Phase B
- B . Phase C
- C . Phase D
- D . Phase E
Correct Answer: D
D
Explanation:
Building blocks are reusable components of business, IT, or architectural capability that can be combined to deliver architectures and solutions. Building blocks can be defined at various levels of detail, depending on the stage of architecture development. In the earlier phases of the ADM cycle (A to D), building blocks are defined in generic terms, such as logical or physical, to provide a high-level view of the architecture. In Phase
E: Opportunities and Solutions, building blocks become implementation-specific, meaning that they are linked to specific products, standards, technologies, and vendors that are available in the market. This phase also identifies the delivery vehicles, such as projects, programs, or portfolios, that will realize the building blocks12
References: 1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 23: Phase E: Opportunities and Solutions 2: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 36: Building Blocks
D
Explanation:
Building blocks are reusable components of business, IT, or architectural capability that can be combined to deliver architectures and solutions. Building blocks can be defined at various levels of detail, depending on the stage of architecture development. In the earlier phases of the ADM cycle (A to D), building blocks are defined in generic terms, such as logical or physical, to provide a high-level view of the architecture. In Phase
E: Opportunities and Solutions, building blocks become implementation-specific, meaning that they are linked to specific products, standards, technologies, and vendors that are available in the market. This phase also identifies the delivery vehicles, such as projects, programs, or portfolios, that will realize the building blocks12
References: 1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 23: Phase E: Opportunities and Solutions 2: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 36: Building Blocks