6.1 Impact of Automation on Network Management

Why Automation Is on the CCNA

Network automation is the use of software to provision, configure, and manage network devices with minimal human interaction. On the CCNA 200-301 v1.1 exam (the version Cisco released in August 2024), Automation and Programmability is its own 10% domain — roughly 8 to 12 questions on a 100-question, 120-minute exam scored on a 300-to-1000 scale with an approximate 825/1000 passing mark. These questions are conceptual: you compare manual versus automated operations and explain benefits, not write code.

Traditional (Box-by-Box) Management

In a traditional network, an engineer touches each device individually through the CLI (Command-Line Interface):

1. SSH or console into the device.
2. Enter configure terminal.
3. Type commands by hand.
4. Run show commands to verify.
5. copy running-config startup-config to save.
6. Move to the next device and repeat.

For 5 devices this is fine. For 500, it is the source of nearly every outage.

Problems With Manual Management

Automated Management

Automated networks treat configuration as data that software applies consistently. A controller, script, or tool reads an intended state and pushes it to every target device through SSH or an API.

The Three Headline Benefits (memorize these)

• Consistency — every device receives the exact same templated configuration, so a 200-switch site is byte-for-byte uniform.
• Speed (agility) — a change validated once deploys to thousands of devices in minutes, not days.
• Reduced human error — code that was tested and peer-reviewed removes typos and forgotten commands.

Configuration Drift in Detail

Configuration drift is the gradual divergence of a device's running configuration from its intended baseline. It comes from undocumented one-off changes, troubleshooting tweaks that are never reverted, and differing engineer habits. Desired-state automation fixes drift two ways: it can continuously enforce the baseline (re-applying it on a schedule) and it can audit every device against the source of truth and flag deviations. This is why "prevents configuration drift" is a textbook correct answer when the exam asks for an automation benefit.

Infrastructure as Code (IaC)

Infrastructure as Code manages network configuration the same way developers manage software:

• Configs are written as code — YAML playbooks, Jinja2 templates, HCL files.
• They live in version control (Git), giving full history, diffs, and rollback to any prior commit.
• They are validated in a CI/CD (Continuous Integration/Continuous Delivery) pipeline before reaching production.
• The code is self-documenting — the file is the documentation.

Common Trap

A frequent distractor claims automation "eliminates the need for networking knowledge" or "makes packets travel faster." Both are wrong. Automation does not change physics or replace expertise — it removes repetitive manual labor and enforces consistency. You still need to understand OSPF, VLANs, and ACLs to write correct automation.

Traditional vs. Automated — Exam Comparison

On the Exam: If asked for the primary benefit of automation, choose the option about consistency, speed, and reduced human error. If asked what problem desired-state automation solves, choose configuration drift.

Putting It Together: A Real Scenario

Imagine a retail company with 300 branch routers, each needing an identical access-control list to block a newly discovered malicious subnet. In the traditional model, an engineer would SSH into each router, enter configuration mode, paste the ACL, apply it to the WAN interface, save the configuration, and verify reachability — roughly four minutes per device with no mistakes, which means about twenty hours of focused work and a near-certainty that at least one device gets a typo or is skipped entirely. Any router missed becomes a silent security hole that nobody notices until an incident.

In the automated model, the same ACL is written once as a template, committed to a Git repository where a teammate reviews the diff, validated against a lab device in the CI/CD pipeline, and then pushed to all 300 routers in a single run that finishes in minutes. Every router ends up identical, the change is timestamped and attributed in version control, and if the ACL turns out to be wrong it is reverted by re-running the pipeline against the previous commit.

This single example demonstrates all three headline benefits at once — consistency, speed, and reduced human error — plus the auditability and instant rollback that infrastructure as code adds on top.

Understanding this distinction is exactly what the exam is testing. You will not be asked to build the pipeline; you will be asked to explain why the automated approach is superior, to identify configuration drift as the underlying disease, and to recognize that the cure is a single source of truth that is continuously enforced rather than a stack of undocumented manual edits accumulating over months.