A network security administrator is preparing a formal change request to deploy a critical security patch to the enterprise central remote-access VPN gateway. The administrator has documented the purpose of the change, defined the scope of affected devices, specified the maintenance window, and conducted a comprehensive risk analysis. Before submitting the proposal to the Change Advisory Board (CAB) for review, which of the following mandatory components must the administrator add to complete the change request?
- A detailed rollback plan outlining step-by-step procedures to restore the gateway to its previous operational state if the patch failsCevap
- BAn executive waiver allowing the technical team to bypass post-implementation testing in order to shorten the maintenance window
- CA formal end-user authorization agreement granting permission to skip CAB approval during emergency patch cycles
- DA request to perform primary patch validation directly on the production VPN gateway during active business hours
Cevap
A detailed rollback plan outlining step-by-step procedures to restore the gateway to its previous operational state if the patch fails
In standard ITIL and CompTIA change management processes, a formal change request must include the purpose, scope, risk assessment, implementation plan, and a documented rollback (backout) plan prior to CAB submission. The rollback plan ensures that if the patch introduces unexpected instability or connection failures, administrators can immediately restore the network service to a known operational state.
Adım Adım Çözüm
Anahtar Kavram
Change Management Processes and Rollback Planning