Quiz The Open Group TOGAF Enterprise Architecture Part 2

The Business Transformation Readiness Assessment is a technique that can be used to evaluate the
readiness of the organization to undergo change and to identify the actions needed to increase the
likelihood of a successful business transformation. This technique can help to address the concerns
of the key stakeholders about the risks and value of the proposed reorganization. The technique
involves assessing the following aspects of the organization: vision, commitment, capacity, capability,
culture, and communication. Based on the assessment, the risks associated with the transformations
can be identified, classified, and mitigated for. The technique also helps to identify the dependencies
between the set of changes, including gaps and work packages, and the improvement actions to be
worked into the Implementation and Migration Plan. The technique also supports the determination
of the business value, effort, and risk associated for each transformation, which can be used to
prioritize and sequence the work packages and the Transition Architectures1 Reference: 1: The
TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 27: Business
Transformation Readiness Assessment

Business continuity is the ability of an organization to maintain essential functions during and after a
disaster or disruption. Business continuity requirements are the specifications and criteria that
define the acceptable level of performance and availability of the business processes and services in
the event of a disaster or disruption. A gap analysis is a technique that compares the current state of
the architecture with the desired state, and identifies the gaps or differences that need to be
addressed. A change request is a formal proposal for an amendment to some product or system,
such as the architecture. A Request for Architecture Work is a document that describes the scope,
approach, and expected outcomes of an architecture project123
The best answer is A, because it describes the steps that would improve the resilience of the current
architecture, which is the ability to withstand and recover from a ransomware attack or any other
disruption. The steps are:
Determine the business continuity requirements, which specify the minimum acceptable level of
performance and availability of the business processes and services in case of a ransomware attack.
This would involve identifying the critical business functions, the recovery time objectives, the
recovery point objectives, and the dependencies and resources needed for recovery.
Undertake a gap analysis of the current Enterprise Architecture, which compares the current state of
the architecture with the desired state based on the business continuity requirements. This would
involve assessing the strengths and weaknesses of the current architecture, the risks and
opportunities for improvement, and the gaps or differences that need to be addressed.
Make recommendations for change requirements to address the situation and create a change
request. This would involve proposing solutions and alternatives to close the gaps, enhance the
resilience, and mitigate the risks of the current architecture. The change request would document
the rationale, scope, impact, and benefits of the proposed changes, and seek approval from the
relevant stakeholders.
Manage a meeting of the Architecture Board to assess and approve the change request. The
Architecture Board is a governance body that oversees the architecture work and ensures
compliance with the architecture principles, standards, and goals. The meeting would
involvepresenting the change request, discussing the pros and cons, resolving any issues or conflicts,
and obtaining the approval or rejection of the change request.
Once approved, produce a new Request for Architecture Work to activate an ADM cycle to carry out a
project to define the change. The Request for Architecture Work would describe the scope, approach,
and expected outcomes of the architecture project that would implement the approved change
request. The Request for Architecture Work would initiate a new cycle of the Architecture
Development Method (ADM), which is the core process of the TOGAF standard that guides the
development and management of the enterprise architecture.
1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 33: Business
Scenarios 2: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30:
Gap Analysis 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter
31: Architecture Change Management : The TOGAF Standard, Version 9.2, Part II: Architecture
Development Method (ADM), Chapter 7: Request for Architecture Work : The TOGAF Standard,
Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 34: Business Transformation Readiness
Assessment : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30:
Gap Analysis : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter
31: Architecture Change Management : The TOGAF Standard, Version 9.2, Part VI: Architecture
Capability Framework, Chapter 50: Architecture Governance : The TOGAF Standard, Version 9.2, Part
II: Architecture Development Method (ADM), Chapter 7: Request for Architecture Work

A Consolidated Gaps, Solutions and Dependencies Matrix is a technique that can be used to create
work packages for an incremental rollout of the architecture. A work package is a set of actions or
tasks that are required to implement a specific part of the architecture. A work packagecan be
associated with one or more Architecture Building Blocks (ABBs) or Solution Building Blocks (SBBs),
which are reusable components of business, IT, or architectural capability. A work package can also
be associated with one or more Capability Increments, which are defined, discrete portions of the
overall capability that deliver business value. A Capability Increment can be realized by one or more
Transition Architectures, which are intermediate states of the architecture that enable the transition
from the Baseline Architecture to the Target Architecture123
The steps for creating work packages using this technique are:
For each gap between the Baseline Architecture and the Target Architecture, identify a proposed
solution and classify it as new development, purchased solution, or based on an existing product. A
gap is a difference or deficiency in the current state of the architecture that needs to be addressed by
the future state of the architecture. A solution is a way of resolving a gap by implementing one or
more ABBs or SBBs.
Group similar solutions together to define the work packages. Similar solutions are those that have
common characteristics, such as functionality, technology, vendor, or location.
Identify dependencies between work packages, such as logical, temporal, or resource dependencies.
Dependencies indicate the order or priority of the work packages, and the constraints or risks that
may affect their implementation.
Regroup the work packages into a set of Capability Increments to transition to the Target
Architecture. Capability Increments should be defined based on the business value, effort, and risk
associated with each work package, and the schedule and objectives of the clinical trials. Capability
Increments should also be aligned with the Architecture Vision and the Architecture Principles.
Document the work packages and the Capability Increments in an Architecture Definition Increments
Table, which shows the mapping between the work packages, the ABBs, the SBBs, and the Capability
Increments. The table also shows the dependencies, assumptions, and issues related to each work
package and Capability Increment.
Therefore, the best answer is B, because it describes the approach to identify the work packages for
an incremental rollout meeting the requirements, using the Consolidated Gaps, Solutions and
Dependencies Matrix as a planning tool.
1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30: Gap
Analysis 2: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 36:
Building Blocks 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques,
Chapter 31: Architecture Change Management : The TOGAF Standard, Version 9.2, Part II:
Architecture Development Method (ADM), Chapter 23: Phase E: Opportunities and Solutions : The
TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 21: Phase F:
Migration Planning : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method
(ADM), Chapter 18: Phase A: Architecture Vision : The TOGAF Standard, Version 9.2, Part III: ADM
Guidelines and Techniques, Chapter 23: Architecture Principles

A security domain model is a technique that can be used to define the security requirements and
policies for the architecture. A security domain is a grouping of assets that share a common level of
security and trust. A security policy is a set of rules and procedures that govern the access and
protection of the assets within a security domain. A security domain model can help to identify the
security domains, the assets within each domain, the security policies for each domain, and the
relationships and dependencies between the domains1
Since the data is being shared across partners, a security federation is needed to establish a trust
relationship and a common security framework among the different parties. A security federation is
a collection of security domains that have agreed to interoperate under a set of shared security
policies and standards. A security federation can enable secure data exchange and collaboration
across organizational boundaries, while preserving the autonomy and privacy of each party. A
security federation requires contractual arrangements, and a definition of the responsibility areas for
the data exchanged, as well as security implications2
A risk assessment is a process that identifies, analyzes, and evaluates the risks that may affect the
architecture. A risk assessment can help to determine the likelihood and impact of the threats and
vulnerabilities that may compromise the security and privacy of the data assets. A risk assessment
can also help to prioritize and mitigate the risks, and to monitor and review the risk situation3
Therefore, the best answer is D, because it describes the risk and security considerations that would
be included in the current phase of the architecture development, which is focused on the Business
Architecture. The answer covers the security domain model, the security federation, and the risk
assessment techniques that are relevant to the scenario.
1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 35: Security
Architecture and the ADM 2: The TOGAF Standard, Version 9.2, Part IV: Architecture Content
Framework, Chapter 38: Security Architecture 3: The TOGAF Standard, Version 9.2, Part III: ADM
Guidelines and Techniques, Chapter 32: Risk Management

A Request for Architecture Work is a document that describes the scope, approach, and expected
outcomes of an architecture project. A Request for Architecture Work is usually initiated by the
sponsor or client of the architecture work, and approved by the Architecture Board, which is a
governance body that oversees the architecture work and ensures compliance with the architecture
principles, standards, and goals. A Request for Architecture Work triggers a new cycle of the
Architecture Development Method (ADM), which is the core process of the TOGAF standard that
guides the development and management of the enterprise architecture12
An Architecture Vision is a high-level description of the desired outcomes and benefits of the
proposed architecture. An Architecture Vision is the output of Phase A: Architecture Vision of the
ADM cycle, which is the first phase of the architecture development. An Architecture Vision defines
the scope and approach of the architecture work, and establishes the business goals and drivers that
motivate the architecture work. An Architecture Vision also involves obtaining the approval and
commitment of the sponsors and other key stakeholders, and initiating the Architecture Governance
process3
A trade-off analysis is a technique that can be used to evaluate and compare different architecture
alternatives and select the most suitable one. A trade-off analysis involves identifying the criteria and
factors that are relevant to the decision, such as costs, benefits, risks, and opportunities, and
assessing the strengths and weaknesses of each alternative. A trade-off analysis also involves
balancing and reconciling the multiple, often conflicting, requirements and concerns of the
stakeholders, and ensuring alignment with the Architecture Vision and the Architecture Principles.
Therefore, the best answer is D, because it proposes the best approach for architecture development
to realize the CEO’s change in direction for the company. The answer covers the Request for
Architecture Work, the Architecture Vision, and the trade-off analysis techniques that are relevant to
the scenario.
1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 7:
Request for Architecture Work 2: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability
Framework, Chapter 50: Architecture Governance 3: The TOGAF Standard, Version 9.2, Part II:
Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision : The TOGAF
Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30: Trade-Off Analysis

The Target Architecture is a description of the future state of the architecture that addresses the
business goals and drivers, and satisfies the stakeholder requirements and concerns. The Target
Architecture is developed through the Architecture Development Method (ADM), which is the core
process of the TOGAF standard that guides the development and management of the enterprise
architecture. The Target Architecture is typically divided into four domains: Business, Data,
Application, and Technology. The Target Architecture also includes a roadmap for change, which
defines the Transition Architectures, the Capability Increments, and the work packages that enable
the transition from the Baseline Architecture to the Target Architecture12
The best answer is B, because it describes the approach that should be taken to determine and
organize the work to deliver the requested architectures, which are the Information Systems and
Technology Architectures. The answer covers the following steps:
Refer to the end-to-end Target Architecture for guidance and direction. The end-to-end Target
Architecture provides the overall vision, scope, and objectives of the architecture work, and the
alignment with the business strategy and goals. The end-to-end Target Architecture also provides the
high-level definitions and principles for the four architecture domains, and the roadmap for change
that outlines the major milestones and deliverables.
Identify projects, dependencies and synergies, then prioritize before initiating the projects. Projects
are the units of work that implement the architecture work packages, which are the sets of actions or
tasks that are required to implement a specific part of the architecture. Dependencies are the
relationships and constraints that affect the order or priority of the projects, such as logical,
temporal, or resource dependencies. Synergies are the benefits or advantages that result from the
combination or coordination of the projects, such as cost savings, efficiency gains, or innovation
opportunities. Prioritization is the process of ranking the projects according to their importance,
urgency, or value, and assigning resources and schedules accordingly.
Develop high-level architecture descriptions. High-level architecture descriptions are the outputs of
the architecture development phases (B, C, and D) of the ADM cycle, which describe the Business,
Data, Application, and Technology Architectures in terms of the Architecture Building Blocks (ABBs)
and the Solution Building Blocks (SBBs), which are reusable components of business, IT, or
architectural capability. High-level architecture descriptions also include the Architecture Views,
which are representations of the system of interest from the perspective of one or more stakeholders
and their concerns.
For each project, estimate effort size, identify reference architectures, and candidate building blocks.
Effort size is the measure of the amount of work, time, or resources required to complete a project.
Effort size can be estimated using various techniques, such as analogy, expert judgment, parametric,
or bottom-up. Reference architectures are standardized architectures that provide a common
framework and vocabulary for a specific domain or industry. Reference architectures can be used as a
source of best practices, patterns, and models for the architecture development. Candidate building
blocks are the potential ABBs or SBBs that can be used to implement the architecture. Candidate
building blocks can be identified from the Architecture Repository, which is a collection of
architecture assets, such as models, patterns, principles, standards, and guidelines.
Identify the resource needs considering cost and value. Resource needs are the specifications and
criteria that define the acceptable level and quality of the resources required to complete the
project, such as human, financial, physical, or technological resources. Resource needs can be
identified by analyzing the scope, complexity, and dependencies of the project, and the availability,
capability, and suitability of the resources. Cost and value are the factors that influence the allocation
and utilization of the resources, such as the budget, the return on investment, the benefits, or the
risks.
Document options, risks, and controls to enable viability analysis and trade-off with the stakeholders.
Options are the alternative ways of achieving the project objectives, such as different solutions,
technologies, vendors, or approaches. Risks are the effects of uncertainty on the project objectives,
such as threats or opportunities. Controls are the measures or actions that are taken to prevent,
reduce, or mitigate the risks, such as policies, procedures, or standards. Viability analysis is the
process of evaluating and comparing the options, risks, and controls, and determining the feasibility,
suitability, and desirability of each option. Trade-off is the decision outcome that balan

A Stakeholder Map is a technique that can be used to identify and classify the stakeholders of the
architecture work, and to document their key interests, requirements, and concerns. A stakeholder is
any person, group, or organization that has a stake in the outcome of the architecture work, such as
the sponsor, the client, the users, the suppliers, the regulators, or the competitors. A Stakeholder
Map can help to understand the needs and expectations of the stakeholders, and to communicate
and engage with them effectively1
The steps for creating a Stakeholder Map are:
Identify the stakeholders of the architecture work, using various sources and methods, such as
interviews, surveys, workshops, or existing documents.
Classify the stakeholders according to their roles, responsibilities, and relationships, using various
criteria and dimensions, such as power, influence, interest, attitude, or impact.
Define the concerns and relevant views for each stakeholder group, using various techniques, such as
business scenarios, use cases, or value propositions. A concern is a key interest or issue that is
relevant to the stakeholder, such as a goal, a problem, a need, or a risk. A view is a representation of
the system of interest from the perspective of one or more stakeholders and their concerns.
Record the stakeholders and their concerns in a Stakeholder Map, which shows the mapping
between the stakeholder groups, the concerns, and the views. The Stakeholder Map also shows the
dependencies, assumptions, and issues related to each stakeholder and concern.
Therefore, the best answer is B, because it recommends the approach that would enable the
development of an architecture that addresses the concerns of the CIO and the partners, using the
Stakeholder Map technique. The answer covers the following aspects:
An analysis of the stakeholders is undertaken, which involves identifying, classifying, and defining
the stakeholders and their concerns.
The stakeholders and their concerns are documented in a Stakeholder Map, which provides a clear
and comprehensive picture of the stakeholder landscape and their interests.
The concerns and relevant views are recorded in the Architecture Vision document, which is the
output of Phase A: Architecture Vision of the Architecture Development Method (ADM), which is the
core process of the TOGAF standard that guides the development and management of the enterprise
architecture. The Architecture Vision defines the scope and approach of the architecture work, and
establishes the business goals and drivers that motivate the architecture work. The Architecture
Vision also involves obtaining the approval and commitment of the sponsors and other key
stakeholders, and initiating the Architecture Governance process2
The requirements include risk mitigation through regular assessments, which involves identifying,
analyzing, and evaluating the risks that may affect the architecture, and determining the appropriate
measures or actions to prevent, reduce, or mitigate the risks. Risk mitigation can also involve
monitoring and reviewing the risk situation, and communicating and reporting the risk status and
actions3
This approach also allows a supervised agile implementation of the continuous Machine Learning,
which involves applying agile principles and practices to the architecture development and
implementation, such as iterative and incremental delivery, frequent feedback, collaboration, and
adaptation. A supervised agile implementation can help to ensure the quality, value, and alignment
of the architecture, and to respond to the changing needs and expectations of the stakeholders.
1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 24:
Stakeholder Management 2: The TOGAF Standard, Version 9.2, Part II: Architecture Development
Method (ADM), Chapter 18: Phase A: Architecture Vision 3: The TOGAF Standard, Version 9.2, Part III:
ADM Guidelines and Techniques, Chapter 32: Risk Management : The TOGAF Standard, Version 9.2,
Part III: ADM Guidelines and Techniques, Chapter 29: Applying Iteration to the ADM

The Business Value Assessment Technique is a technique that can be used to estimate and compare
the business value of the projects and project increments that implement the architecture work
packages, which are the sets of actions or tasks that are required to implement a specific part of the
architecture. The business value is the measure of the benefits or advantages that the project or
project increment delivers to the business, such as increased revenue, reduced costs, improved
quality, or enhanced customer satisfaction1
The steps for applying the Business Value Assessment Technique are:
Identify the criteria and factors that are relevant to the business value assessment, such as costs,
benefits, risks, and opportunities. The criteria and factors should be aligned with the business goals
and drivers that motivate the architecture work, and the stakeholder requirements and concerns that
influence the architecture work.
Assign weights and scores to the criteria and factors, using various methods, such as expert
judgment, historical data, or analytical models. The weights and scores should reflect the importance
and performance of the criteria and factors, and the trade-offs and preferences of the stakeholders.
Calculate the business value for each project or project increment, using various techniques, such as
net present value, return on investment, or balanced scorecard. The business value should indicate
the expected or actual outcomes and impacts of the project or project increment on the business.
Prioritize the implementation projects and project increments, based on the business value and
other considerations, such as dependencies, resources, or risks. The prioritization should determine
the order or sequence of the projects and project increments, and the allocation and utilization of
the resources.
Therefore, the best answer is C, because it describes the next steps for the migration planning, which
are the activities that support the transition from the Baseline Architecture to the Target
Architecture. The answer covers the Business Value Assessment Technique, which is relevant to the
scenario.
1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 28: Business
Value Assessment Technique : The TOGAF Standard, Version 9.2, Part II: Architecture Development
Method (ADM), Chapter 18: Phase A: Architecture Vision : The TOGAF Standard, Version 9.2, Part II:
Architecture Development Method (ADM), Chapter 21: Phase F: Migration Planning : The TOGAF
Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 36: Building Blocks

Based on the TOGAF standard, this answer is the best approach for architecture development to
realize the CEO’s change in direction for the company. The reason is as follows:
The scenario describes a major business transformation that requires a clear understanding of the
current and future states of the enterprise, as well as the gaps and opportunities for change.
Therefore, the priority is to understand and bring structure to the definition of the change, rather
than focusing on the implementation details or the technology aspects.
The team should use the TOGAF ADM as the method and guiding framework for architecture
development, and adapt it to suit the specific needs and context of the enterprise. The team should
also leverage the existing Architecture Capability and the Architecture Repository to reuse and
integrate relevant architecture assets and resources.
The team should focus iteration cycles on a baseline first approach to architecture development,
which means starting with the definition of the Baseline Architecture in each domain (Business, Data,
Application, and Technology), and then defining the Target Architecture in each domain. This will
help to identify the current and desired states of the enterprise, and to perform a gap analysis to
determine what needs to change in order to achieve the business goals and objectives.
The team should then focus on transition planning, which involves identifying and prioritizing the
work packages, projects, and activities that will deliver the change. The team should also create an
Architecture Roadmap and an Implementation and Migration Plan that will guide the execution and
governance of the change.
The team should use the Architecture Vision phase and the Requirements Management phase to
work out in detail what the shared vision is for the change, and to capture and validate the
stakeholder requirements and expectations. The team should also use the Architecture Governance
framework to ensure the quality, consistency, and compliance of the architecture work.
The TOGAF Standard, Version 9.2 - Architecture Development Method : The TOGAF Standard,
Version 9.2 - Architecture Vision : The TOGAF Standard, Version 9.2 - Requirements Management :
[The TOGAF Standard, Version 9.2 - Architecture Governance]

The best answer is C. You would hold a series of interviews at each of the manufacturing plants using
the business scenarios technique. This will allow you to understand the systems and integrations
with local partners. You would use stakeholder analysis to identify key players in the engagement,
and to understand their concerns. You will then identify and document the key high-level stakeholder
requirements for the architecture. You will then generate high level definitions of the baseline and
target architectures.
This answer is based on the TOGAF standard, which recommends the following steps to initiate the
architecture project1:
Establish the architecture project
Identify stakeholders, concerns, and business requirements
Confirm and elaborate business goals, business drivers, and constraints
Evaluate business capabilities
Assess readiness for business transformation
Define scope
Confirm and elaborate Architecture Principles, including business principles
Develop Architecture Vision
Define the Target Architecture value propositions and KPIs
Identify the business transformation risks and mitigation activities
Secure stakeholder and sponsor approval
The answer C covers most of these steps, by using the business scenarios technique to elicit and
validate the business requirements, goals, drivers, and constraints, as well as the current and future
states of the architecture2. The answer C also uses stakeholder analysis to identify and engage the
key stakeholders, and to address their concerns and expectations3. The answer C also generates high
level definitions of the baseline and target architectures, which can be used to develop the
Architecture Vision and the value propositions4.
The other answers are not the best approach for architecture development, because:
Answer A focuses on researching vendor literature and conducting briefings with vendors, which is
not the best way to understand the business needs and the current situation of the enterprise.
Answer A also defines a preliminary Architecture Vision without involving the stakeholders or
validating the requirements, which may lead to misalignment and lack of consensus.
Answer B conducts a pilot project that will enable vendors to demonstrate potential solutions, which
is premature and costly at this stage of the architecture project. Answer B also does not address the
stakeholder concerns or the current systems and integrations, which may result in gaps and risks.
Answer B also develops the requirements after the pilot project, which may not reflect the actual
business needs and goals.
Answer D develops baseline and target architectures for each of the manufacturing plants, which
may not consider the enterprise-wide perspective and the potential benefits of a common ERP
system. Answer D also does not involve the stakeholders or address their concerns, which may result
in resistance and conflict. Answer D also does not define the business case or the performance
metrics, which are essential for demonstrating the value and feasibility of the architecture.
1: The TOGAF Standard, Version 9.2 - Architecture Vision 2: The TOGAF Standard, Version 9.2 -
Business Scenarios 3: [The TOGAF Standard, Version 9.2 - Stakeholder Management] 4: [The TOGAF
Standard, Version 9.2 - Architecture Definition Document]