CCNA automation: what the exam actually asks
The automation section scares people more than it should. Here's what's on it, what isn't, and how to study it efficiently.
How much of the exam it is
On the 200-301 blueprint, Automation and Programmability is about 15% — roughly 15–20 questions out of ~100. It is not the biggest domain; IP connectivity and IP services carry more weight. But it's the domain most candidates skip, which makes it cheap marks if you prepare for it.
What's actually tested
- Traditional vs controller-based networking — the difference in architecture, and why controllers exist.
- SDN concepts — control plane vs data plane, northbound and southbound APIs, overlay/underlay at a conceptual level.
- REST APIs — HTTP verbs (GET, POST, PUT, PATCH, DELETE), status codes (200, 201, 400, 401, 404), authentication, and what CRUD means.
- Configuration management — what Ansible, Puppet and Chef are for, and how they differ from manual configuration.
- JSON — reading a nested object and picking out a value. That's it; no serialisation theory.
What isn't tested
This is where people waste weeks:
- Writing Python. The exam may show a short script and ask what it does, but you are not asked to write one.
- Deep Ansible. Knowing what a playbook and an inventory are is enough; you won't debug Jinja2 filters.
- Cisco DNA Center administration. Concepts, not clicking through a controller.
If your goal is only the certificate, you can pass the automation domain with a few focused hours. If your goal is the job, that's a different course — and a different article.
How to study it without wasting time
- Learn the vocabulary first. Control plane, data plane, northbound/southbound, idempotent, declarative vs imperative. Half the questions are vocabulary in disguise.
- Read one real JSON payload. Take any API response — even a public one — and practise extracting a nested value. That's the skill being tested.
- Do one REST call.
curl -X GETagainst a device or a public API. Seeing a 401 and a 200 once makes the status-code questions trivial. - Run one Ansible playbook in check mode. Even against a lab switch. The concept lands in ten minutes when you see the diff.
The trap: passing the exam without the skill
The automation domain is small enough to memorise. That's exactly the problem — you can pass it and still be unable to back up forty switches or push a VLAN change safely. Employers increasingly ask for the second thing.
If you want both, the order that works is: pass the exam with focused theory, then build one real script against a lab. Backups are the best first project because they're read-only, immediately useful, and teach you connection handling, timeouts and error handling without risking an outage.
Network Automation Lab picks up where the exam stops: the same Python and Ansible skills, applied to real devices, with a safe rollout at the end.