A network engineering team is preparing to implement a major SD-WAN traffic steering policy update across all enterprise branch locations. Place the standard change management steps in the correct chronological order from first to last.
- 1Draft and submit a formal Request for Change (RFC) containing the proposed policy details, business impact analysis, and rollback plan.
- 2Present the RFC to the Change Advisory Board (CAB) for formal review, risk assessment, and deployment authorization.
- 3Schedule the maintenance window according to CAB approval and issue change notifications to impacted business stakeholders.
- 4Create baseline backups of existing device configurations and execute the policy deployment during the authorized window.
- 5Perform post-implementation verification testing, update network configuration documentation, and close the change ticket.
Cevap
The correct chronological order is: 1) Draft and submit a formal RFC with a rollback plan, 2) Present the RFC to the CAB for authorization, 3) Schedule the maintenance window and notify stakeholders, 4) Create configuration backups and deploy the change during the maintenance window, and 5) Perform post-implementation verification, update documentation, and close the RFC ticket.
The standard network change management workflow progresses systematically through request formulation (RFC creation with risk analysis and rollback plans), advisory review (CAB approval), logistics and communication (window scheduling and user notifications), controlled deployment (pre-change backups and execution), and post-deployment closure (testing, documentation updates, and RFC ticket closure).
Adım Adım Çözüm
Anahtar Kavram
Standard Network Change Management Lifecycle