Examkin

Question

Difficulty: EasyConfiguration and Change Management

A network technician needs to upgrade the firmware on a campus access switch following standard IT service management practices. In what chronological order should the technician execute the steps of the change management lifecycle from first to last?

  1. 1Draft and submit a formal Request for Change (RFC) detailing the change scope, risk analysis, and rollback procedure.
  2. 2Obtain formal authorization and scheduling clearance from the Change Advisory Board (CAB).
  3. 3Execute the firmware installation and perform initial verification during the approved maintenance window.
  4. 4Conduct a post-implementation review (PIR) to confirm change success and update configuration baselines.

Answer

The correct sequence starts with submitting the RFC, followed by securing CAB approval, deploying the update during the maintenance window, and concluding with a post-implementation review.
Standard change management follows a strict lifecycle: initiating an RFC with impact and rollback details, obtaining formal CAB authorization, implementing the change within an approved maintenance window, and concluding with a post-implementation review to verify success and document the updated baseline.

Step-by-Step Solution

1
Identify the initial administrative step required prior to review.
The RFC must be drafted and submitted first with risk assessments and rollback plans.
Governance frameworks require documented justification and safety plans before evaluating proposed modifications.
2
Determine the governing authorization step.
The CAB reviews the submitted RFC and grants authorization.
Stakeholders must evaluate potential operational impacts before scheduling the change.
3
Identify the execution phase.
The technician installs the firmware during the scheduled maintenance window.
Authorized changes are performed during pre-approved windows to avoid disrupting production traffic.
4
Identify the final closeout phase.
Perform a post-implementation review (PIR) and update documentation.
Final validation ensures objectives were met and administrative records remain accurate.

Key Concept

Standard Change Management Lifecycle
Rate this question

Topics

Configuration and Change Management

More questions from this topic