Examkin

Question

Difficulty: HardChange Management Processes

An enterprise systems engineer is preparing a formal change request to migrate an organization's central Identity and Access Management (IAM) directory server to a high-availability cloud infrastructure. The engineer has already detailed the business purpose, defined the technical scope, evaluated potential operational risks, and established a backout procedure using virtual machine snapshots. Which of the following additional elements must be included in the change documentation before presenting it to the Change Advisory Board (CAB) for authorization?

  1. An end-user notification plan specifying expected service downtime and communication channels.Answer
  2. B
    A post-implementation sign-off waiver signed by helpdesk staff to bypass testing upon deployment.
  3. C
    Administrative root credential delegation documents assigning domain control to the Change Advisory Board.
  4. D
    Preliminary deployment verification logs gathered from applying the change directly to the live production server.

Answer

An end-user notification plan specifying expected service downtime and communication channels is the required element missing from the change documentation.
A complete change management request must include the purpose, scope, risk analysis, plan for change, rollback/backout plan, and end-user notification plan before being submitted to the Change Advisory Board (CAB) for approval. Communicating scheduled downtime and expectations to impacted users is a critical requirement of the change management lifecycle.

Step-by-Step Solution

1
Analyze the core change management components already completed in the scenario.
The engineer has completed the purpose, scope, risk analysis, and rollback (backout) plan.
Identifying what has been completed isolates which essential CompTIA change management phase is still absent.
2
Evaluate the remaining standard requirements for a formal change request proposal.
Standard ITIL/CompTIA change management process requires: Purpose, Scope, Risk Analysis, Plan for Change, End-User Notification, Rollback Plan, and CAB Approval.
End users and business stakeholders must be notified in advance regarding when service maintenance will occur and how workflows might be impacted.
3
Select the required missing component prior to CAB submission.
The end-user notification plan must be included in the change proposal prior to formal CAB review and approval.
CAB approval relies on knowing that business stakeholders have been properly notified of scheduled downtime.

Key Concept

Change Management Processes - Required Documentation Elements
Rate this question

Topics

Change Management Processes

More questions from this topic