A network administrator is planning to upgrade the firmware on all core network switches across a multi-building corporate campus. The administrator has already defined the scope of work, completed a risk assessment, drafted a comprehensive rollback plan, and successfully verified the firmware update in a non-production lab environment. Which of the following is the most appropriate next step in the formal change management process before implementing the upgrade?
- Submit the change proposal along with supporting documentation to the Change Advisory Board (CAB) for formal review and authorization.Answer
- BExecute the firmware update during off-peak weekend hours to minimize business disruption without waiting for administrative review.
- CBroadcast an immediate maintenance notification to all staff members announcing that core network services will restart within the hour.
- DDeploy the firmware update directly to half of the production switches to observe real-world performance before updating the rest.
Answer
Submitting the change proposal along with supporting documentation to the Change Advisory Board (CAB) for formal review and authorization is the necessary next step.
In standard IT change management workflows, once technical planning (scope, risk analysis, backout plan) and lab testing are complete, the change request must be submitted to the Change Advisory Board (CAB). The CAB reviews the documentation, checks for conflicts with other enterprise operations, approves the change, and assigns an official implementation window.
Step-by-Step Solution
Key Concept
Standard Change Management Workflow