Examkin

Question

Difficulty: HardChange Management Processes

A senior cloud infrastructure engineer is preparing a change proposal to perform a critical firmware upgrade across a cluster of enterprise hypervisors hosting mission-critical services. To comply with formal change management controls before presenting the request to the Change Advisory Board (CAB), which of the following elements MUST be included in the initial change proposal? (Select TWO.)

  1. A comprehensive rollback procedure specifying step-by-step instructions to restore hypervisors to their baseline state if severe issues occur.Answer
  2. An explicit scope definition detailing all target hypervisor nodes, affected network segments, and dependent enterprise workloads.Answer
  3. C
    Completed post-implementation verification test logs demonstrating that all virtualized workloads are fully functional.
  4. D
    Direct execution of the firmware deployment on a production node to gather live performance telemetry prior to seeking advisory approval.

Answer

The initial change proposal submitted for Change Advisory Board (CAB) review must include a comprehensive rollback procedure to revert systems if unexpected failures occur, and an explicit scope definition detailing all affected hypervisors, network segments, and workloads.
Formal change management procedures require IT personnel to document the exact scope of change and a clear rollback plan before submitting a change proposal to the Change Advisory Board (CAB). The scope ensures stakeholders understand affected assets and services, while the rollback plan provides a fallback path if the upgrade fails. Both elements are critical for risk management during CAB evaluation.

Step-by-Step Solution

1
Analyze the change management lifecycle phase presented in the scenario.
The engineer is in the pre-approval phase, preparing documentation for Change Advisory Board (CAB) evaluation.
CAB approval requires complete risk assessment, scope definition, and recovery plans prior to granting authorization for execution.
2
Identify mandatory pre-implementation proposal components.
Defining the scope of change and establishing a clear rollback plan are required initial steps.
These documentation elements allow the CAB to evaluate organizational risk and ensure business continuity fallback options exist.
3
Differentiate pre-change proposal documentation from post-change execution tasks.
Post-implementation testing logs and direct production deployment occur during or after execution, making them invalid pre-proposal requirements.
Production changes cannot be executed without prior authorization, and post-testing can only occur after implementation.

Key Concept

Change Management Processes - Pre-Approval Documentation Requirements
Rate this question

Topics

Change Management Processes

More questions from this topic