Quibank app: now on the App Store — free, works offline. Get the app ↗

Chapters0/30 ▾
  1. 1.Models, Media & Topologies0/5
    1. The OSI and TCP/IP models: layers, data units and devices
    2. Copper and fiber: categories, distances and connectors
    3. Installing cable: plenum ratings and Power over Ethernet
    4. Wireless basics: channels, bonding, antennas and identifiers
    5. Topologies and network types: domains, mesh, spine and leaf, SAN
  2. 2.IP Addressing, Subnetting & Routing0/5
    1. IPv4 subnetting with the block-size method
    2. Private, loopback and APIPA ranges, and traffic types
    3. How routers choose a path: prefix, distance, metric and summaries
    4. IPv6: shortening, address types, SLAAC and NAT64
    5. VLANs, inter-VLAN routing and NAT
  3. 3.Ports, Protocols & Services0/5
    1. Well-known ports: secure and cleartext pairs
    2. TCP and UDP: handshake, flow control and real-time traffic
    3. DNS and DHCP: transports, records, relays and reservations
    4. Time and monitoring protocols: NTP and SNMP
    5. Tunnels, IPsec and QoS markings
  4. 4.Network Operations0/5
    1. Network documentation and the device lifecycle
    2. Monitoring with baselines, SNMP and syslog
    3. Seeing traffic: flow data, TAPs, mirror ports and availability checks
    4. Disaster recovery and high availability
    5. Change management and configuration baselines
  5. 5.Network Security0/5
    1. Core security terms: CIA, risk vocabulary and zero trust
    2. Identity and access: AAA, 802.1X, RADIUS, TACACS+, MFA and RBAC
    3. Filtering and segmentation: ACLs, screened subnets and IDS
    4. Recognizing network attacks from their symptoms
    5. Hardening, wireless authentication and physical security
  6. 6.Network Troubleshooting0/5
    1. The troubleshooting methodology, step by step
    2. Cable faults, distance limits, PoE budgets and the right tester
    3. Reading interface counters and port states
    4. Addressing and service failures: masks, DHCP, duplicates, loops, ACLs, DNS
    5. Wireless and voice quality problems
Saved in this browser. Move it to another device →
← Network Operations

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 →