CompTIA N10-009 Configuration Management & Backups Guide

Configuration-management questions are state-control questions. CompTIA is usually testing whether you can keep known-good settings, recover from mistakes, and recognize when undocumented drift has turned the network into a support problem.

Baseline configuration: A known-good standard configuration used as the comparison point for support and compliance.

Configuration drift: The gradual difference between the intended standard state and the actual device state in production.

Rollback: Reverting to a previous known-good configuration after a bad or risky change.

What CompTIA is really testing

The strongest answers usually depend on whether you can separate:

• the current production config from the approved baseline
• a backup copy from a standardized template or policy baseline
• version control from ad hoc file storage
• fast restore from slow manual rebuild

Keep the config states distinct

Baseline versus backup versus snapshot thinking

A simple config-management workflow

    flowchart LR
	  A["Approved baseline"] --> B["Deploy to production"]
	  B --> C["Back up current state"]
	  C --> D["Monitor for drift or unauthorized changes"]
	  D --> E["Restore or correct when needed"]

What to notice:

• the baseline defines intended state
• backups protect current recoverable state
• drift detection matters because not every bad change causes an immediate outage

Small backup record example

1device: edge-fw-01
2baseline: v3.2-approved
3backup: 2026-03-29-2200
4last-restore-test: 2026-03-01

What to notice:

• a backup with no restore confidence is weaker than it looks
• baseline and backup are related but not identical
• version awareness makes audits and rollback easier

Backup is not enough if restore is untrusted

CompTIA often rewards the answer that protects recoverability, not just file storage. A backup is weaker when:

• nobody has tested restore
• the version naming is unclear
• the file is stored with no access control
• the team cannot tell whether it was captured before or after a bad change

Safe change sequence

    flowchart LR
	  A["Approved baseline or change plan"] --> B["Back up current state"]
	  B --> C["Apply controlled change"]
	  C --> D["Validate behavior"]
	  D --> E["Keep change or roll back quickly"]
	  E --> F["Update records and version history"]

What to notice:

• backup happens before risky change work
• validation is part of the change, not an optional afterthought
• rollback only works well when the team knows which copy is trustworthy

Why drift is so dangerous

CompTIA often likes the scenario where nobody changed the documented design, but the actual device now behaves differently because:

• small exceptions were added over time
• emergency fixes were never normalized
• backups exist, but nobody knows which version is trustworthy

That is why config discipline improves both recovery speed and auditability.

Drift clues CompTIA likes

Common traps

• treating a backup as the same thing as a baseline
• storing config files without testing whether restore actually works
• letting undocumented drift become the new norm
• failing to capture the device state before making a change
• assuming version history alone replaces a usable rollback copy

What strong answers usually do

• keep baseline, backup, and version history distinct
• test restore paths instead of assuming the backup is useful
• track changes so drift can be explained and corrected
• protect recoverability before touching production state
• prefer controlled rollback over improvised rebuilding when a known-good copy already exists

Decision order that usually wins

Separate intended state from recoverable state. First, ask whether the scenario is about standardization or recovery. That tells you whether baseline or backup matters more. Second, ask whether the device is drifting away from the approved configuration. Third, prefer versioned, testable backups over vague claims that “we saved the config somewhere.” On the exam, trustworthy recovery depends on both good copies and confidence that they can actually be restored.

Quiz

Continue with 3.5 Monitoring & Visibility to keep the domain flow intact.