Network engineering has spent the last decade absorbing a skill set it did not originally ask for. Configuration by CLI still works, but the roles that pay best increasingly expect you to reach for an API, commit to Git, and let a pipeline push the change. The Cisco 200-901 exam exists at exactly that junction, and it is the credential for engineers who want to prove they can operate on both sides of it.
What makes the exam distinctive is its balance. It is not a programming test, and it is not a networking test. It asks whether you can use software techniques to manage network infrastructure — which means a developer with no routing knowledge and a network engineer with no API experience are each missing about half of it. This guide covers the six domains, where the marks concentrate, and how to prepare depending on which half you are starting from.
What Is the Cisco 200-901 Exam?
The Cisco 200-901 exam, Automating Networks Using Cisco Platforms, validates your ability to apply software development and automation techniques to Cisco network infrastructure. It covers APIs, data formats, version control, Cisco platform programmability, deployment practices, and the network fundamentals that underpin all of it. It is an associate-level credential aimed at engineers working where networking and software meet.
The exam sits at the entry point of Cisco’s automation track. That positioning matters: it is designed to be reachable by a working network engineer who has never written production code, and equally by a developer who has never configured a switch — while still requiring genuine competence in both directions.
| Attribute | Detail |
|---|---|
| Exam code | 200-901 |
| Exam name | Automating Networks Using Cisco Platforms (CCNAAUTO) |
| Number of questions | 90–110 |
| Duration | 120 minutes |
| Passing score | Approximately 750–850 of 1000 (scaled) |
| Price | $300 USD |
Two details are worth noting. The question count is a range rather than a fixed number, so pace yourself against the clock rather than a target. And the passing score is scaled — Cisco does not publish a simple percentage, and the threshold is not a straight 70%. Treat the scaled score as a reason to aim comfortably clear of borderline rather than to calculate a minimum. Cisco’s developer portal, Cisco DevNet resources, is the primary home for the platform material this exam draws on.
What Does the 200-901 Exam Cover?
The 200-901 exam spans six domains covering software development and design, APIs, Cisco platforms, application deployment and security, infrastructure automation, and network fundamentals. The weighting is unusually even, with no domain above 20% and none below 15%.
| Domain | Weight |
|---|---|
| Understanding and Using APIs | 20% |
| Infrastructure and Automation | 20% |
| Software Development and Design | 15% |
| Cisco Platforms and Development | 15% |
| Application Deployment and Security | 15% |
| Network Fundamentals | 15% |
That distribution is the most useful planning input you have. There is no dominant domain to concentrate on and no small domain you can quietly drop — the gap between the largest and smallest is five percentage points. Every area is worth roughly a sixth of your result.
The practical consequence is that breadth beats depth here. A candidate who is outstanding at APIs and blank on deployment practices is in worse shape than one who is solidly competent across all six. Plan your study time close to evenly, then adjust only for the areas your background genuinely does not cover.
Why Do APIs and Automation Dominate the Blueprint?
APIs and Infrastructure and Automation are the two largest domains at 20% each, together making up 40% of the exam. That is not arbitrary weighting — these two areas are the actual mechanism by which modern networks are managed programmatically, and everything else on the blueprint exists to support them.
On the API side, expect REST fundamentals rather than trivia: how a request is constructed, what HTTP response codes signal, how authentication mechanisms differ, and how to interpret the data that comes back. Data formats sit alongside this — XML, JSON, and YAML are all examinable, and being able to read a payload and identify its structure is a recurring practical skill.
On the automation side, the syllabus names the tooling directly. Model-driven programmability through YANG, RESTCONF, and NETCONF appears here, as do configuration management tools including Ansible and Terraform, alongside infrastructure-as-code concepts. The exam expects you to know what each tool is for and when you would reach for it rather than to recite command syntax, so working through the Ansible documentation and the Terraform documentation at a conceptual level is time well spent.
If your study time is constrained, this 40% is where it produces the most return. It is also the content that transfers most directly to daily work, which makes it the least wasted preparation on the entire blueprint.
Which Cisco Platforms Must You Know?
The Cisco Platforms and Development domain is 15% of the exam and covers the programmable capabilities of Cisco’s major product lines. The syllabus names Meraki, Catalyst Center, ACI, SD-WAN, and NSO specifically. You are expected to know what each platform does and how it is programmatically accessed — not to administer any of them in depth.
Group them by the problem each solves and the domain becomes far more manageable. Meraki handles cloud-managed networking with a straightforward REST API. Catalyst Center provides campus network automation and assurance. ACI covers data-centre policy-driven networking. SD-WAN manages wide-area connectivity through controllers. NSO orchestrates services across multi-vendor estates.
The examinable question is almost always positional: given a described automation requirement, which platform and which API would you use? That is a reasoning task rather than a recall task, and it rewards understanding each platform’s purpose over memorising endpoint names.
Candidates working through Cisco’s broader tracks will notice this domain acts as connective tissue to the rest of the portfolio. If you have already explored the CCNP Enterprise certification paths, the platforms will feel familiar and this becomes one of the easier 15% blocks on the exam.
How Much Coding Do You Actually Need?
Software Development and Design is 15% of the 200-901 exam, covering development methods, data structures, version control with Git, and design principles. You need to read and reason about code comfortably, but you are not being assessed as a professional software engineer, and no domain asks you to build an application from scratch.
Git deserves specific attention because it appears explicitly in the syllabus and because it is the tool most network engineers have avoided longest. Understand the basic workflow — clone, branch, commit, merge, pull request — and why version control matters when configuration lives in files rather than on devices. That conceptual shift, from configuring devices to versioning intent, is genuinely what the domain is testing, and the official Git documentation covers the workflow concisely.
Beyond Git, expect software development lifecycle concepts, common design patterns at a recognition level, and enough data-structure literacy to parse and manipulate an API response. Python is the practical lingua franca here, and being able to follow a script that calls an API and handles the result is a realistic bar.
Engineers who have avoided programming often find this domain less intimidating than expected. The exam is testing whether you can work alongside software practice, not whether you could pass a developer interview. A few weeks of deliberate practice reading and modifying small scripts covers most of what is asked.
“The capabilities of the new network create new job roles, such as the Network Automation Developer and DevSecOps Professional, and these professionals need a combination of network infrastructure engineering and software development skills.”
How Much Networking Knowledge Is Required?
Network Fundamentals is 15% of the exam and covers routing, switching, and IP services. For working network engineers this is the most comfortable domain on the blueprint. For developers approaching from the software side, it is usually the hardest, and it is the one most likely to be underestimated.
The content is foundational rather than advanced. You need to understand how traffic moves, how addressing and subnetting work, what the common IP services do, and enough about routing and switching behaviour to reason about what an automation change would actually affect. It is not asking for expert-level protocol analysis.
That said, the domain matters more than its 15% suggests, because networking context underpins the automation questions elsewhere. Automating a change you do not conceptually understand is how outages happen, and the exam reflects that by assuming baseline network literacy throughout the other domains rather than quarantining it here.
If you are coming from software, budget disproportionate time for this domain and start with it rather than leaving it until last. The automation content will make considerably more sense once you understand what is being automated.
Who Should Take the 200-901 Exam?
The 200-901 exam suits network engineers moving toward automation, developers working with network infrastructure, and DevOps practitioners whose remit includes networking. There are no formal prerequisites. The ideal candidate has working familiarity with either networking or software development and wants to build competence in the other.
Network engineers are the largest audience and arguably the best served. Your existing knowledge covers Network Fundamentals outright and gives real context to the platform domain. The work is learning APIs, version control, and deployment practice — genuinely new skills, but ones that attach naturally to infrastructure you already understand.
Developers come at it from the opposite direction, with the software domains largely covered and the networking content as the gap. That path is entirely viable, but it demands honesty about how much foundational networking you actually hold, since the exam assumes it well beyond the domain nominally labelled for it.
The third group is engineers whose organisation is moving toward infrastructure-as-code and who need credible evidence of the skill set. For them the exam’s value lies as much in the preparation as the credential — the syllabus is a well-structured curriculum for exactly this transition.
How Should You Prepare for 200-901?
Effective 200-901 preparation allocates study time nearly evenly across the six domains and concentrates extra effort on whichever half of the exam — networking or software — your background does not cover. Most candidates need six to ten weeks. Hands-on practice with real APIs matters more than any amount of reading.
| Step | Focus | Goal |
|---|---|---|
| 1 | Honest self-audit: networking side vs software side | Know which half is your gap before you start |
| 2 | Your weaker half — fundamentals first | Baseline literacy so the rest makes sense |
| 3 | APIs and data formats — REST, JSON, XML, YAML | Read a payload and construct a request confidently |
| 4 | Automation tooling — YANG, RESTCONF, NETCONF, Ansible, Terraform | Explain what each tool is for and when to use it |
| 5 | Cisco platforms and deployment practice | Match a requirement to the right platform and API |
| 6 | Timed practice across all six domains | Consistent scores under two-hour conditions |
Step one is the step that decides your timeline. A network engineer and a developer preparing for this exam need materially different plans, and starting with a generic study guide wastes the advantage your background already gives you.
Get hands on an actual API early. Cisco maintains public DevNet sandbox environments, and an afternoon making real calls against a live platform teaches more about authentication, response codes, and payload structure than a week of reading. This is the single highest-value practical step available.
Finally, test under time pressure. With 90 to 110 questions in 120 minutes, pacing is a genuine factor, and scenario questions consume more time than recall items. Working through realistic 200-901 practice questions under the clock builds the rhythm and exposes domains where your understanding is thinner than it felt while reading.
“By the end of 2028, over 80% of all comprehensive network automation initiatives will have been shelved due to persistent skills scarcity and inadequate funding, up from less than 10% in 2024.”
Is the Certification Worth Earning?
The 200-901 credential is most valuable to network professionals whose roles are shifting toward automation, and to organisations moving network configuration into code. Its worth is tied directly to that industry transition — which is well underway rather than speculative, making the timing favourable.
The strongest argument is the skill combination it certifies. Engineers who understand networking deeply are common, and developers who write good code are common, but people genuinely fluent in both remain comparatively scarce. That intersection is where network automation roles sit, and it is precisely what this exam validates.
The preparation also has standalone value. Unlike credentials that test product trivia, this syllabus maps onto skills used daily in modern infrastructure work — APIs, version control, CI/CD, infrastructure as code. Even setting the certificate aside, an engineer who has genuinely learned this material is more capable than one who has not.
The honest caveat is scope. This is an associate-level credential, so it opens a path rather than completing one. It establishes that you can work in this space, and professional-level automation and infrastructure certifications build from there — much as foundational credentials such as CCST Cybersecurity career paths open their own tracks. As a first deliberate step into network programmability, it is well aimed.
Frequently Asked Questions About 200-901
How many questions are on the Cisco 200-901 exam?
The exam contains approximately 90 to 110 questions with a 120-minute time limit. Because the count varies, pace yourself against the clock rather than a fixed target. Scenario-based questions take noticeably longer than straightforward recall items.
What is the passing score for 200-901?
Cisco uses a scaled score, typically around 750 to 850 out of 1000, rather than a simple percentage. Because the exact threshold is not published as a fixed percentage, aim to score comfortably clear of borderline in practice rather than targeting a minimum.
How much does the 200-901 exam cost?
The exam costs $300 USD. That is the Cisco registration fee and should not be confused with third-party practice test products, which are priced separately and typically cost far less.
Do you need programming experience to pass 200-901?
No professional programming experience is required. You need to read and reason about code, understand Git basics, and work with data formats like JSON and YAML. Software Development and Design is 15% of the exam and tests literacy rather than the ability to build applications.
Do you need networking experience?
Some networking knowledge is genuinely necessary. Network Fundamentals is 15% of the exam, and networking context is assumed throughout the automation domains. Candidates from a pure software background should budget extra time here and study it early rather than last.
Which 200-901 domain is most heavily weighted?
Understanding and Using APIs and Infrastructure and Automation are tied at 20% each, together making up 40% of the exam. The remaining four domains are each 15%, making this an unusually evenly weighted blueprint with no domain safe to skip.
Which Cisco platforms does the exam cover?
The syllabus names Meraki, Catalyst Center, ACI, SD-WAN, and NSO. You are expected to understand what each platform does and how it is accessed programmatically, rather than to administer any of them in depth. Questions typically ask which platform fits a stated requirement.
Is Python required for the 200-901 exam?
Python is the practical language of the automation ecosystem and appears throughout study material. You should be able to follow a script that calls an API and processes the response. You are not required to write complex programs from scratch under exam conditions.
How long should you study for 200-901?
Six to ten weeks suits most candidates, depending heavily on background. Those already strong in either networking or software will move faster through half the blueprint. Audit which half is your gap first, because that determines your realistic timeline more than anything else.
Conclusion
The 200-901 exam is defined by its balance. Six domains, none above 20% or below 15%, split evenly between software practice and network infrastructure — which means your result is decided by whichever half you know least. Audit that honestly before you plan anything else.
Give APIs and automation the largest share of your attention, since together they are 40% of the marks and the most transferable content on the blueprint. Get hands on a real API early rather than reading about them. Learn the Cisco platforms by what problem each solves rather than by endpoint. Do that, and an evenly weighted exam becomes a straightforward one.
