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.
Reference: 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

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.

Reference: 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 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 package can 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.
Reference: 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

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 involve
presenting 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.
Reference: 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

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