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?
- A documented rollback plan detailing step-by-step procedures to revert the infrastructure to its prior state if the upgrade encounters critical failuresCevap
- BPost-implementation testing logs collected directly from the live production authentication environment prior to board review
- CWritten sign-off from all end users confirming their individual consent for the scheduled system outage
- DA bypass waiver authorized by the helpdesk manager to skip pre-deployment sandbox testing due to time constraints
Cevap
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.
Adım Adım Çözüm
Anahtar Kavram
Essential Documentation Components of a Formal Change Request