Examkin

Question

Difficulty: HardChange Management Processes

A senior systems administrator is preparing a change request for an upcoming upgrade to the organization's central identity management and single sign-on (SSO) infrastructure. The administrator has documented the purpose of the change, defined the scope of affected directory services, conducted a risk assessment, and scheduled the maintenance window. Which of the following critical components must still be included in the change request documentation before it is submitted to the Change Advisory Board (CAB) for review and authorization?

  1. A documented rollback plan detailing step-by-step procedures to revert the infrastructure to its prior state if the upgrade encounters critical failuresAnswer
  2. B
    Post-implementation testing logs collected directly from the live production authentication environment prior to board review
  3. C
    Written sign-off from all end users confirming their individual consent for the scheduled system outage
  4. D
    A bypass waiver authorized by the helpdesk manager to skip pre-deployment sandbox testing due to time constraints

Answer

The change request documentation must include a documented rollback plan detailing step-by-step procedures to revert the infrastructure to its prior state if the upgrade fails.
In enterprise IT operational procedures, a formal change request submitted for CAB approval must include a comprehensive rollback plan alongside purpose, scope, risk analysis, and notification schedules. The rollback plan guarantees a clear remediation path to restore services if the implementation fails.

Step-by-Step Solution

1
Analyze the change management lifecycle phase in the scenario.
The administrator is preparing the change proposal before submitting it to the Change Advisory Board (CAB).
The CAB requires a complete change proposal containing purpose, scope, risk analysis, implementation plan, rollback plan, and notification plan prior to authorization.
2
Identify the missing essential documentation component.
The administrator has defined the purpose, scope, risk assessment, and schedule, but has omitted the rollback plan.
Standard operational procedures mandate that every change request must specify how to safely revert changes if an unintended service disruption or deployment failure occurs.
3
Evaluate the incorrect choices.
Post-implementation testing cannot occur in production before approval, individual user sign-offs are not required, and skipping sandbox testing violates change management policies.
These choices represent procedural errors or improper workflow sequences within change management.

Key Concept

Essential Documentation Components of a Formal Change Request
Rate this question

Topics

Change Management Processes

More questions from this topic