Examkin

Soru

Zorluk: Çok zorChange Management Processes

A storage area network (SAN) engineer is preparing a change request to update the microcode on an enterprise SAN array hosting critical Virtual Desktop Infrastructure (VDI) datastores. The engineer has defined the purpose and scope of the change, completed a risk analysis regarding potential storage disruption, created a step-by-step implementation plan, and established post-implementation testing protocols. Prior to presenting this request to the Change Advisory Board (CAB) for formal authorization, which of the following mandatory change management components must the engineer add to complete the change documentation?

  1. A detailed rollback plan outlining specific procedures to revert the storage array microcode and configuration to its prior operational state if the update fails.Cevap
  2. B
    A completed post-implementation review detailing the overall success and latency metrics observed after maintenance.
  3. C
    An emergency script that automatically applies the microcode update directly to production nodes to bypass maintenance windows.
  4. D
    A signed service-level agreement (SLA) modification approved by external software vendors authorizing maintenance operations.

Cevap

A detailed rollback plan outlining specific procedures to revert the storage array microcode and configuration to its prior operational state if the update fails.
The correct answer emphasizes the necessity of a documented rollback plan. Standard CompTIA change management workflows mandate that every proposed change include a clear purpose, scope, risk assessment, implementation plan, rollback plan, end-user notification, CAB authorization, and post-implementation testing. Without a predefined strategy to revert changes, the risk of unrecoverable downtime is unacceptably high.

Adım Adım Çözüm

1
Analyze the change request preparation phase described in the scenario.
Identified existing components: purpose, scope, risk analysis, implementation plan, post-implementation testing, and end-user notification strategy.
CompTIA change management process mandates specific documentation requirements prior to CAB submission.
2
Evaluate missing prerequisite components for CAB submission.
Recognized that a documented rollback (backout) plan has not yet been defined.
Without a rollback plan, the organization cannot mitigate risk if the microcode update causes unforeseen system failure or data corruption.
3
Select the correct mandatory documentation step.
Determined that developing a rollback plan is the required next step before formal CAB authorization.
CAB approval requires verification that services can be safely restored to a baseline state if unexpected issues occur.

Anahtar Kavram

Core Elements of Formal Change Documentation
Bu soruyu puanla

Konular

Change Management Processes

Bu konudan daha fazla soru