Chapters0/30 ▾
Chapter 4 · Lesson 5 of 5
Change management and configuration baselines
1 min read
A change request records who wants what changed, on which systems, when, and with what approval.
The rollback (back-out) plan and a verified configuration backup are part of that request and must exist before approval, because once a core switch is down there is no time to design a recovery and the old configuration may be gone. This applies to any change that can affect service, not only emergencies.
Change records also speed up troubleshooting. When something that worked yesterday fails and no device reports a fault, a change is the most likely cause, so check the change log first. Rack drawings, heat maps and inventories describe a steady state and record nothing about what was modified.
When monitoring reports that a running configuration has drifted from the golden baseline, find out why.
If the change was unauthorized, revert it. If it was requested and approved, promote it into a new baseline version and refresh the stored backup, so future rebuilds do not silently undo it. Example: an approved new VLAN shows up as drift on Monday; the right step is to version the baseline, not to delete the VLAN or switch off the alert.
Check yourself
1. At what point in the change management process must a documented rollback (back-out) plan exist for a firmware upgrade on a core switch?
2. An automated comparison reports that a switch's running configuration no longer matches the approved baseline (golden) configuration. Investigation shows the difference came from a change that was properly requested, risk-assessed, and approved. What is the correct next step?
Facts checked 2026-11-16 · Sources: CompTIA Network+ certification overview, RFC 5424: The Syslog Protocol, NIST SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems
CompTIA Network+ cheat sheet: every key fact on one page →