Examkin

Question

Difficulty: EasyConfiguration and Change Management

Place the standard stages of an enterprise network change management workflow in the correct chronological order from first to last.

  1. 1Submit a formal Request for Change (RFC) document detailing the purpose, scope, and rollback plan.
  2. 2Perform a risk assessment and obtain formal review and authorization from the Change Advisory Board (CAB).
  3. 3Execute the configuration changes on the target network devices during the approved maintenance window.
  4. 4Perform post-implementation testing and update configuration baseline documentation.

Answer

The correct chronological sequence is: 1) Submit a formal Request for Change (RFC) document, 2) Perform a risk assessment and obtain Change Advisory Board (CAB) approval, 3) Execute the configuration changes during the maintenance window, and 4) Perform post-implementation testing and update configuration baseline documentation.
The standard change management lifecycle follows a strict sequence: initiating the process by submitting an RFC, analyzing risks and acquiring authorization from the Change Advisory Board (CAB), carrying out the change inside an authorized maintenance window, and concluding with post-implementation validation and documentation updates.

Step-by-Step Solution

1
Identify the initial step of proposing a change.
Submitting the RFC initiates the formal workflow.
Changes must be documented and formally requested before evaluation can begin.
2
Identify the review and authorization step.
CAB review and risk assessment evaluate the proposal.
Management and stakeholders must review and approve the request prior to deployment to mitigate potential downtime.
3
Identify the execution phase.
Implementation occurs in a scheduled maintenance window.
Approved changes must be carried out during pre-determined maintenance hours to minimize business disruption.
4
Identify the final verification and documentation step.
Post-implementation review and baseline updates finalize the change.
Verification ensures functional stability, and updated documentation ensures configuration records reflect the new operational state.

Key Concept

Standard Change Management Process Lifecycle
Rate this question

Topics

Configuration and Change Management

More questions from this topic