The short version
Plan on roughly 60 to 100 hours in total if you already know some Python and networking, and more if you do not. The 4-week plan fits about 15 to 20 hours a week. The 8-week plan fits 8 to 12 hours a week and suits beginners. These ranges vary a lot from person to person.
Before you start
Do three things on day one.
- Download the current exam topics from Cisco’s exam page and keep them open. Every study session should map to a numbered topic.
- Set up a place to run code. You need Python 3, the requests library, Git, and a text editor. Docker is useful too.
- Create a free account for Cisco DevNet resources such as the Sandbox and Learning Labs, so you can try real APIs.
Weightings drive the plan: APIs and Infrastructure and Automation are 20% each, the other four domains 15% each. The domains page explains each one.
Rules that apply to both plans
- Run code, do not only read it. For every topic, write or modify a tiny script.
- Keep a short error log. Write down each practice question you missed and why.
- Take your first practice set cold, before you finish studying. It gives you a baseline per domain.
- Use the how to study guide for general techniques such as spaced review.
The 4-week plan (about 15 to 20 hours a week)
This plan assumes you can already read Python and know basic networking.
Week 1: foundations and APIs.
- Take practice set 1 as a baseline (about 2.5 hours, including review).
- Software Development and Design: JSON, XML and YAML, parsing into Python data structures, Git operations, and test-driven development.
- Understanding and Using APIs: build REST requests with the requests library, learn status codes, headers and authentication types.
Week 2: platforms and deployment.
- Cisco Platforms and Development: Meraki, Catalyst Center, ACI, Catalyst SD-WAN, NSO, Webex, Intersight, UCS Manager, security platforms, and the DevNet resources.
- Model-driven programmability: YANG, NETCONF and RESTCONF.
- Application Deployment and Security: deployment models, containers, Dockerfiles, CI/CD, OWASP threats, bash.
Week 3: automation and networking.
- Infrastructure and Automation: Ansible playbooks, Terraform concepts, infrastructure as code, controller versus device level, unified diffs, sequence diagrams, pyATS and Cisco Modeling Labs.
- Network Fundamentals: VLANs, IP addressing and subnetting, DHCP, DNS, NAT, SNMP, NTP, port numbers and troubleshooting.
- Take practice set 2 at the end of the week.
Week 4: review and simulation.
- Redo your weakest two domains with labs.
- Take practice sets 3 and 4, and read every explanation, including the ones you got right.
- Take set 5 as a timed simulation in one sitting.
The 8-week plan (about 8 to 12 hours a week)
This plan suits you if Python or networking is new.
| Week | Focus | Practice |
|---|---|---|
| 1 | Python basics, data formats, Git | Baseline: set 1 |
| 2 | Software design, testing, development methods | Short quiz by domain |
| 3 | REST APIs, status codes, authentication, webhooks | Write three small API scripts |
| 4 | Cisco platforms: Meraki, Catalyst Center, ACI, SD-WAN, Webex | Set 2 |
| 5 | YANG, NETCONF, RESTCONF, Docker, CI/CD, security | Review error log |
| 6 | Ansible, Terraform, NSO, bash scripts, diffs | Set 3 |
| 7 | Network fundamentals and troubleshooting | Set 4 |
| 8 | Weak spots, timed simulation, rest | Set 5 |
How to use practice exams
- Study first, then test. A practice set is a measuring tool, not a teacher.
- After each set, look at your score per domain. Spend your next study block on the lowest domain.
- Read the explanation for every wrong answer and for those you guessed. Write one sentence on why the tempting option was wrong.
- Re-take a set only after several days, so that you test understanding and not memory.
- Treat your own target as the goal: score consistently above it on the final timed set. Our pass marks are our own settings, not Cisco’s.
The last three days
- Three days out: one last timed set. Review misses only. No new topics.
- Two days out: skim your error log and the exam topics. Write a short cheat list from memory: common status codes, port numbers, Git commands, HTTP methods, YANG keywords. Check it afterwards.
- The day before: light review for an hour or less. Confirm your booking, ID and, if you test online, your room and computer. See the exam day guide.
- Exam day: eat, arrive early, and pace yourself. Mark time-consuming questions and return to them.
When to book
Book once your timed practice results are steady, not at the very beginning. A booked date can motivate, but a date that is too early causes stress. Leave a few weeks of slack.
More guides for CCNAAUTO-200-901
- 200-901 CCNAAUTO Exam Format and Scoring
- 200-901 CCNAAUTO Sample Questions
- Is the 200-901 CCNAAUTO Exam Hard?
- 200-901 CCNAAUTO Prerequisites
- 200-901 CCNAAUTO Renewal and Retakes Explained
- Is 200-901 CCNAAUTO Worth It? An Honest Look
- 200-901 CCNAAUTO Cheat Sheet: Key Facts
- CCNA vs CCNA Automation: Which Exam First?
Next step
Read the domains explained page to see what each domain involves. When you are ready for a baseline, the 200-901 practice exams report your score per domain.
FAQ
How many hours do I need?
Many candidates with some coding and networking background report somewhere between 60 and 100 hours. Beginners need more. It varies.
Can I study in 2 weeks?
Only if you already work with Python, REST APIs and Cisco platforms daily. Otherwise use the 4-week plan.
Should I do labs or watch videos?
Do labs. Videos help you get started, but the exam rewards the ability to read and reason about code.