Please read this scenario prior to answering the question Your role is that of a senior architect, reporting to the Chief Enterprise Architect, at a…

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