Change management is a formal process for requesting, reviewing, approving, and documenting network changes. CompTIA Network+ N10-009 tests change management concepts as part of Network Operations. Uncontrolled changes are a leading cause of outages — change management prevents downtime caused by poorly planned or untested modifications to production networks.
Practice this topic
A formal change management process: (1) Request: the change initiator submits a change request (CR) describing what is changing, why, and when. (2) Review: the change is reviewed by a CAB (Change Advisory Board) — a group of technical and business stakeholders. (3) Approval: the CAB approves or denies. (4) Implementation: the change is made during an approved maintenance window. (5) Verification: the change is tested and verified to work correctly. (6) Documentation: all records updated — diagrams, IP records, configurations backed up.
Change categories: Standard change — pre-approved, low-risk, routine (e.g., adding a user, resetting a password). Normal change — requires CAB review and approval — most network changes. Emergency change — urgent fix for a critical outage — expedited process with post-implementation review.
Every change must have a rollback plan — documented steps to reverse the change if it causes problems. A router configuration change rollback plan might be: copy backup config to running-config and reload. Without a rollback plan, a failed change can require hours of recovery instead of minutes.
Risk assessment: evaluate the impact of both implementing and not implementing the change. Consider: maintenance window timing, affected services, number of users impacted, testing in a lab environment first, and notification to affected stakeholders. Changes should be tested in a non-production environment before production deployment.
Emergency changes bypass all change management processes
Emergency changes use an expedited process — approval may come from a smaller group or on-call manager — but they still require documentation, rollback plans, and post-implementation review
These questions are representative of what you will see on Network+ exams. The correct answer and explanation are shown immediately below each question.
A network engineer plans to upgrade firmware on the core router. Before making the change, what must be documented as part of the change management process?
Explanation: A rollback plan is a mandatory component of change management — it documents the steps to reverse the change if it causes problems. For a firmware upgrade, this would include steps to reload the previous firmware. The rollback plan must be prepared and tested before the change window begins.
A maintenance window is a pre-scheduled period of time designated for network changes, updates, and maintenance. Typically scheduled during low-usage periods (nights, weekends). During the window, affected services may experience brief interruptions. Maintenance windows are communicated to stakeholders in advance so they can plan accordingly.
Try free Change Management practice questions with explanations, topic links and progress tracking.