Is 200-901 hard? Difficulty explained
200-901 is moderately hard, and the difficulty depends on where you start. For a network engineer who has never programmed it is hard, because it asks you to read Python, JSON, Dockerfiles and Git output. For a developer with no networking background it is also hard, because a fifth of the exam is networking and Cisco platforms. Cisco publishes no pass rate or passing score, so no official difficulty figure exists; the difficulty comes from breadth and from reading code in a time limit.
Why people find it hard
| Factor | Why it hurts |
|---|---|
| Breadth | Software, APIs, platforms, deployment, automation and networking in one exam |
| Two backgrounds | Almost nobody is strong in both coding and networking |
| Product facts | Many Cisco platforms, each with its own authentication and objects |
| Reading, not writing | You interpret scripts, playbooks, diffs and sequence diagrams |
| Cost | A retake costs another exam fee (300 USD at time of writing) |
Difficulty by domain
| Domain | Weight | Harder for | Typical trap |
|---|---|---|---|
| Software Development and Design | 15% | Network engineers | Git merge conflicts, parsing to Python structures |
| Understanding and Using APIs | 20% | Both | 401 vs 403, where a token goes, webhooks vs polling |
| Cisco Platforms and Development | 15% | Developers | Telling the platforms apart; AXL vs UDS |
| Application Deployment and Security | 15% | Network engineers | Dockerfile instructions, OWASP threats |
| Infrastructure and Automation | 20% | Both | Reading an Ansible playbook or a unified diff |
| Network Fundamentals | 15% | Developers | Ports, NAT and VLAN symptoms |
What trips candidates up
Similar answers. A 401 and a 403 both mean you cannot do something; the exam wants the one that matches the scenario. The same goes for PUT and PATCH, or a service orchestrator and a controller.
Platform trivia. Domain 3 is a long list. A table with one row per platform, its authentication method and its main object is more effective than rereading documentation.
Interpretation questions. Several objectives start with interpret or identify the workflow. You see a short script and must say what it automates. Practise reading code fast, without running it.
Unpublished details. Cisco does not publish the question count or the passing score on the pages used for this guide, so you cannot calculate a margin. Aim for consistent high scores on practice material instead.
How long does preparation take?
| Your background | Typical effort |
|---|---|
| Developer who knows REST and Git | 3 to 4 weeks, mostly networking and Cisco platforms |
| Network engineer who scripts a little | 4 weeks, mostly Git, Docker and APIs |
| Network engineer who never programmed | 8 weeks or more, starting with Python basics |
| New to both | 10 to 12 weeks, or consider CCNA 200-301 first |
These ranges are planning estimates from the scope of the outline, not Cisco figures.
How to make it easier
- Learn REST thoroughly first, because it supports domains 2, 3 and 5.
- Do the hands-on labs in the study resources. Running code once teaches more than reading it three times.
- Use the domain guides to find your weakest area and attack that.
- Check the exam format so nothing on the day surprises you.
Compare with the networking associate in is the CCNA hard, and decide between the two with 200-901 vs CCNA. When you are ready, book the exam and read the exam day guide.