Browse CompTIA Certification Guides

Network Configuration Management and Backups

March 30, 2026

How baselines, version history, backups, and drift detection keep network configurations recoverable and supportable.

On this page

Network configuration management is the practice of defining, recording, reviewing, and controlling device configuration. It makes a change explainable and a failed change recoverable.

A baseline is the approved intended state. A backup is a recoverable copy of a device’s actual state at a point in time. Configuration drift is the difference that accumulates between the approved state and the configuration running in production. These terms are related, but they are not interchangeable.

Artifact Primary purpose
Baseline or template Define the approved configuration standard
Running configuration Show the active state of a device
Startup configuration or saved configuration Preserve the state intended to survive a restart, where the platform uses this model
Backup Restore or compare a known capture of device state
Version history and change record Explain who changed state, when, and why

A practical workflow

  1. Define a baseline appropriate to the device role and software release.
  2. Store configurations in an access-controlled system with useful version history.
  3. Capture a current backup before a risky change, with the device identity and capture time.
  4. Implement and validate the approved change.
  5. Compare the resulting state to the baseline and document accepted exceptions.
  6. Periodically test the restore process, not only the existence of backup files.
1device: edge-fw-01
2baseline: firewall-edge-v3.2
3backup: edge-fw-01_2026-03-29T2200Z
4change: CHG-1042
5restore_tested: 2026-03-01
6approved_exception: temporary-partner-vpn-rule

The record ties the recoverable copy to a device and change, rather than leaving an ambiguous file named final-config.

Detect and handle drift

Drift often follows emergency repairs, manual exceptions, or changes made outside the normal workflow. It may not cause a visible outage immediately, but it complicates audits, replacement, incident response, and rollback. Compare active configurations to the baseline, investigate unexpected differences, and either correct them or record why an exception is approved.

Protect configuration backups like other sensitive infrastructure data. They can contain addresses, topology details, shared secrets, certificates, and administrator settings. Encrypt them where appropriate, limit access, and retain them according to the organization’s policy.

For the surrounding implementation and approval process, see Network Change Management.

Revised on Friday, September 11, 2026
Change Management
Monitoring and Visibility