Question

Difficulty: MediumChange Management Processes

A Linux systems administrator is preparing to increase RAM allocation and update the hypervisor kernel on a cluster of host servers hosting an organization's Virtual Desktop Infrastructure (VDI). The administrator has already documented the business purpose of the modification, performed a risk assessment, defined the scope of work, and drafted a step-by-step backout plan. Which of the following represents the immediate next step the administrator must perform in the formal change management lifecycle before performing the maintenance?

  1. Submit the documented change request to the Change Advisory Board (CAB) for formal authorization.Answer
  2. B
    Execute the hypervisor kernel upgrade and memory adjustments during off-peak operational hours.
  3. C
    Conduct post-implementation functionality testing directly on the live production host servers.
  4. D
    Send a system-wide notification to all corporate end users confirming that the VDI maintenance is complete.

Answer

The administrator must submit the documented change request to the Change Advisory Board (CAB) for formal authorization.
In formal change management workflows, once the change request components (purpose, scope, risk analysis, and rollback plan) are prepared, the request must be submitted to the Change Advisory Board (CAB) for review and authorization before any implementation or scheduling occurs.

Step-by-Step Solution

1
Identify the current phase of the change management process completed by the technician.
The technician has completed the initial planning phase: purpose, scope definition, risk assessment, and backout/rollback plan.
Establishing clear scope, risk level, and recovery steps is required before seeking managerial and technical review.
2
Determine the next sequential phase in standard IT enterprise change management.
The change request must be submitted for formal Change Advisory Board (CAB) review and authorization.
CAB approval ensures that proposed changes are scheduled appropriately, do not conflict with other infrastructure maintenance windows, and meet corporate risk standards prior to deployment.

Key Concept

Change Advisory Board (CAB) Approval Workflow
Rate this question