200-901
DevNet Associate (DEVASC)
DevNet Associate (DEVASC) Exam Guide: What Candidates Should Know and How to Prepare
The former Cisco DevNet Associate exam validated practical ability in software development, APIs, Cisco platforms, application security, infrastructure automation, and network fundamentals. It served candidates moving toward network automation and developer-focused Cisco work. Cisco has since transitioned the DevNet Associate track to CCNA Automation: effective February 3, 2026, the successor is 200-901 CCNAAUTO, Automating Networks Using Cisco Platforms. This guide helps you decide whether your preparation should target the current successor exam, use the former DEVASC blueprint as a study reference, or confirm an existing certification’s migration status.
Is DEVASC still the exam you should schedule?
Candidates should not treat DEVASC as a current scheduling name without checking Cisco’s current exam information. Cisco states that the former DevNet Associate certification became CCNA Automation on February 3, 2026, and identifies 200-901 CCNAAUTO, Automating Networks Using Cisco Platforms, as its successor. Before buying training or booking a test, verify the current exam listing and title on Cisco’s official certification pages.
What changed for the candidate
Cisco states that the DevNet certification track transitioned to the CCNA, CCNP, and CCIE Automation track effective February 3, 2026. Cisco also states that the content from the previous 200-901 DEVASC exam remains unchanged in the CCNA Automation version and that only the exam name was updated. That makes the former DEVASC blueprint useful for study planning, but the current registration decision belongs to the CCNA Automation path.
A candidate with an active DevNet certification should also check Cisco’s transition information rather than assuming a new examination is required. Cisco states that active DevNet certifications were automatically migrated to the corresponding Automation certifications on February 3, 2026. The official transition page is the appropriate place to confirm how that statement applies to an individual record.
What passing the successor exam represents
Cisco identifies passing 200-901 CCNAAUTO as earning the CCNA Automation certification. Cisco also states that the exam can count toward recertification goals. Those are current certification outcomes; the historical DEVASC name should be used to understand the earlier blueprint and terminology, not as a substitute for checking the present exam catalogue.
What skills did the former DEVASC blueprint measure?
The former exam was designed around the intersection of programming, network operations, and Cisco automation. Cisco described it as assessing software development and design, API usage, Cisco platforms and development, application development and security, and infrastructure and automation. The v1.1 blueprint also lists Network Fundamentals as one of six domains, so preparation needed both coding judgment and enough networking context to use automation correctly.
The six blueprint domains
Cisco’s DEVASC v1.1 blueprint lists Software Development and Design, Understanding and Using APIs, Cisco Platforms and Development, Application Development and Security, Infrastructure and Automation, and Network Fundamentals. Use these as study workstreams rather than six isolated subjects: an API exercise may require Python, authentication, HTTP interpretation, platform knowledge, and network reasoning at the same time.
The v1.1 release notes state that all exam domains remained identical compared with v1.0. However, some tasks were updated for product naming changes, end-of-life products, and Terraform use. A candidate using older books, videos, or notes should therefore compare the material with the official blueprint and release notes instead of assuming that every product reference remains current.
The two published domain weights
Cisco’s DEVASC exam-topics page assigned 15% to Software Development and Design and 20% to Understanding and Using APIs. These figures identify the published emphasis for those named domains; they do not justify treating the other domains as optional. Your study plan should allocate substantial practice to APIs while still covering the complete six-domain blueprint.
The API domain is especially broad in practical terms. Cisco’s blueprint included REST API requests, webhooks, HTTP response codes, API authentication, API styles, and Python scripts using the requests library. Study should therefore move beyond recognizing terms: you should be able to read a request, identify its authentication and response behavior, and explain what a script is doing.
Who benefits most from this certification path?
The material suits candidates who want to automate network and platform tasks with code, APIs, and Cisco development tools. It is relevant to an engineer adding programming to a networking background, a developer learning network infrastructure, or an automation practitioner who needs Cisco platform context. It is less suitable as a purely theoretical programming credential because the blueprint connects coding decisions to APIs, infrastructure, security, and network behavior.
A networking-first candidate
If you already understand routing, switching, addressing, and common network services, spend less time rereading familiar definitions and more time converting operational tasks into API calls or scripts. Your likely risk is not basic connectivity; it is misunderstanding authentication, data formats, error handling, or the boundary between a Cisco platform and the application consuming it.
Begin with a small automation workflow. Define the desired network or platform outcome, identify the API or SDK, inspect the returned data, and decide how the script should respond to failure. This sequence exposes gaps more effectively than watching disconnected programming lessons.
A developer-first candidate
If you are comfortable with Python and web services but have limited networking experience, reverse the emphasis. Build a compact foundation in network fundamentals before attempting platform automation. Learn what devices, controllers, policies, interfaces, and services represent so that an apparently valid API call can be judged against the network result it is supposed to produce.
Do not assume that successful code execution proves operational correctness. A script can authenticate and return a response while still addressing the wrong resource, applying an unsuitable change, or ignoring a failure condition. Pair each coding exercise with a short explanation of the network or platform state it is intended to change.
An existing Cisco professional
If you work with Cisco platforms already, identify which products you have used directly and which you only recognize by name. Cisco’s former blueprint referenced platforms including Meraki, Cisco DNA Center, ACI, Cisco SD-WAN, NSO, Webex, Firepower, Umbrella, and ISE, along with Python scripting and Cisco SDKs. Use that list to expose unfamiliar platform concepts, not to memorize product labels without understanding their automation role.
How should you organize the blueprint into study work?
Organize preparation around repeatable technical actions: design a small program, call an API, interpret the result, secure the application, automate infrastructure, and explain the network context. This approach prevents the common mistake of studying each product or keyword as a separate fact list. Keep one evidence table with the blueprint task, your confidence, a practice task, and the source or lab used to close the gap.
Software Development and Design
This domain calls for disciplined programming decisions rather than syntax recall alone. Practice decomposing a task into inputs, processing, outputs, and failure paths. Review data structures, reusable functions, modular code, version-control concepts, and the behavior you expect when an external service returns incomplete or unexpected data.
A useful exercise is to take a manual network operation and write a design note before writing code. State the resource being changed, the data required, how the script authenticates, what a successful response means, and how the script should report an error. Then implement only the smallest useful version.
Understanding and Using APIs
Treat APIs as an end-to-end workflow. Practice constructing REST requests, selecting methods, supplying headers and parameters, parsing response data, and interpreting HTTP response codes. Add webhooks and API styles to the same study cycle so you understand both client-initiated requests and event-driven communication.
Use Python’s requests library for focused exercises, as it appears in the former blueprint. For each exercise, record the endpoint purpose, authentication method, request body, expected response, and safe handling of unsuccessful responses. This creates a reusable troubleshooting reference and reveals whether you understand the interaction or are merely copying a request.
Cisco Platforms and Development
Study Cisco platforms by capability and automation interface. For every platform named in your materials, identify what it manages, which kind of developer or operator uses it, what an API or SDK contributes, and what information a script would need. This is more durable than memorizing a long catalogue of product descriptions.
The platform list in Cisco’s former blueprint spans cloud-managed networking, controllers, security products, collaboration, and orchestration. That breadth means your preparation should compare roles: a controller may expose centralized policy and inventory, while an orchestration or security platform may expose different resources and workflows. Keep those distinctions explicit in your notes.
Application Development and Security
Secure automation code must protect credentials, validate inputs, handle failures, and avoid exposing sensitive response data. Practice identifying where secrets live, how authentication is passed, what should be logged, and which inputs require validation. Security study should be attached to every API or application exercise rather than postponed until the end.
Review the difference between an application that works in a controlled example and one that is safe to reuse. Ask whether credentials are hard-coded, whether an error leaks sensitive information, whether a webhook can be trusted, and whether a request could make an unintended change. These questions turn security from vocabulary into implementation judgment.
Infrastructure and Automation
Infrastructure automation requires you to connect desired state, tools, resources, and repeatability. Compare scripts, APIs, SDKs, configuration approaches, and infrastructure-as-code concepts in terms of what each is responsible for. The v1.1 release notes specifically mention Terraform use among task updates, so older preparation resources should be checked for current terminology and coverage.
Build one workflow that can be run more than once without producing an uncontrolled result. Decide what the script or tool should do when the target already matches the desired state, when a dependency is unavailable, or when only part of the change succeeds. Those decisions are central to reliable automation and are more valuable than a one-time demonstration.
Network Fundamentals
Network fundamentals provide the diagnostic context for automation. Review addressing, connectivity, common protocols, device and controller roles, and the network effects of a configuration change. You do not need to separate this knowledge from development: use it to explain why an API request, policy, or automation task should produce a particular operational result.
For each networking concept, connect a symptom to a likely layer or dependency. If an API call fails, distinguish authentication, authorization, transport, endpoint, payload, and target-state problems. If a call succeeds but the intended service does not work, inspect the network and policy assumptions rather than treating the HTTP response as the final answer.
What study sequence works best?
A practical sequence is foundation, API mechanics, Cisco platforms, secure application behavior, infrastructure automation, and integrated review. Start with a diagnostic rather than a long reading phase. Mark each blueprint task as can explain, can perform with notes, or cannot yet perform. Then spend most study time converting the last two categories into observable work products.
Phase one: establish the baseline
Read the official blueprint and map every task to a note, example, or lab. Do not begin by collecting numerous courses. First identify whether your largest gap is Python, networking, HTTP and APIs, Cisco platforms, or automation design. This diagnosis determines the order of study and prevents a networking expert from overinvesting in familiar material.
Create a glossary only for terms you can explain in a technical sentence. For example, do not record “webhook” as a definition alone; note who sends it, what event triggers it, what the receiver must validate, and how failure might be handled.
Phase two: build one API habit
Use a single repeatable worksheet for API practice: purpose, method, endpoint, authentication, headers, parameters, body, response code, returned data, and error handling. Apply it to several examples, then reproduce the workflow in Python with the requests library. The goal is to make request analysis automatic without reducing the subject to memorized syntax.
Add a webhook exercise after ordinary request-and-response work. Explain the difference in control flow and identify the security checks required before accepting an event. This contrast helps you reason about API styles and event-driven behavior instead of treating every integration as the same pattern.
Phase three: connect code to Cisco platforms
Choose platform examples that expose different automation models, then compare them in writing. For each one, describe the managed object, the API or SDK boundary, the authentication approach presented in the documentation, and the operational result. Avoid trying to build a large production system; a small, well-explained workflow gives better evidence of understanding.
When a product reference comes from an older resource, check the v1.1 release notes for naming, end-of-life, and Terraform-related updates. This is particularly important when a course uses screenshots or terminology from an earlier blueprint version.
Phase four: integrate and troubleshoot
Finish with mixed scenarios rather than domain-by-domain quizzes alone. Start from a desired outcome, select a platform or API, write a request or script outline, identify security controls, and diagnose at least one failure. Explain your reasoning aloud or in writing. Integrated practice shows whether the domains are connected in your understanding.
Keep an error log with four fields: the mistaken assumption, the evidence that disproved it, the corrected rule, and a new exercise. Revisit the log at the end of each study session. Repeated errors often reveal a missing mental model, while isolated syntax errors usually need only targeted practice.
What should a weekly study plan contain?
Use a study cycle that produces something testable each week: one blueprint review, one coding or API task, one Cisco platform comparison, one security check, and one mixed troubleshooting exercise. Adjust the time spent according to your diagnostic results, but do not let a strong programming background eliminate network fundamentals or let platform familiarity replace hands-on API reasoning.
A repeatable session format
Begin by recalling a blueprint task without notes. Next, read or review only the material needed for that task. Then perform a small lab or code exercise. Finally, write a short explanation of the result and one failure mode. This sequence separates recognition from competence and gives you a record of what still needs work.
Keep the environment simple enough that you can identify the cause of a result. Too many simultaneous tools, products, or dependencies make troubleshooting ambiguous. Start with a request you can inspect, a response you can parse, and a clearly stated expected outcome before adding complexity.
How to decide when a topic is ready
A topic is ready for review when you can explain its purpose, select an appropriate technique, carry out a small example, and diagnose an ordinary failure without immediately consulting a solution. If you can only recognize a definition or reproduce a copied command, mark the topic as unfinished.
Use the official blueprint as the completion checklist. A polished lab that covers only APIs is not evidence that the full exam scope is covered. Conversely, a short exercise can be sufficient when it demonstrates several connected tasks and you can explain every design and security choice.
Which preparation mistakes waste the most time?
The most costly mistakes are studying the old exam name without checking the current successor, memorizing platform names, treating HTTP status codes as isolated facts, and postponing security and networking until the final review. Correct these by anchoring every study activity to an official blueprint task and a practical decision that you can explain or demonstrate.
Mistake: using outdated material uncritically
The former DEVASC blueprint remains relevant because Cisco says its content remains unchanged in the CCNA Automation version, but Cisco also documents updates involving product naming, end-of-life products, and Terraform use. Compare older resources with the official v1.1 blueprint and release notes. Replace stale terminology in your notes instead of learning two conflicting versions.
Mistake: confusing a successful request with a successful solution
An HTTP response is evidence about a request, not automatically proof that the intended network or application outcome occurred. Check the method, endpoint, authentication, payload, returned object, and resulting state. Practice explaining what you would inspect next when the request succeeds but the service behavior remains wrong.
Mistake: avoiding hands-on work
Reading about APIs and SDKs can build vocabulary but does not reveal whether you can select fields, parse data, handle errors, or protect credentials. Make each major topic produce an artifact: a request worksheet, a short script, a platform comparison, a threat checklist, or a troubleshooting note.
Mistake: preparing by memorizing leaked material
Exam dumps and leaked questions are not a reliable preparation strategy and do not demonstrate the skills described by Cisco’s blueprint. They can also leave major gaps in coding, API interpretation, security, and networking. Use official topics, legitimate learning resources, and original practice tasks instead; no memorization source guarantees a pass.
What delivery details are officially evidenced?
The available Cisco overview describes the former 200-901 DEVASC exam as a 120-minute exam available in English. Those details belong to the former DEVASC exam overview. Because Cisco has transitioned the track and renamed the successor as 200-901 CCNAAUTO, confirm current delivery, language, registration, and scheduling information on the current Cisco exam page before making a booking decision.
How to use the old duration in planning
The former 200-901 DEVASC duration was 120 minutes, but it should be treated as historical delivery evidence rather than assumed current scheduling information for CCNAAUTO. You can still use timed practice to build concise reading and troubleshooting habits, while relying on Cisco’s current listing for the actual exam appointment details.
Do not convert a practice score into a predicted result unless Cisco provides an official scoring interpretation. Instead, review whether you missed a question because of a knowledge gap, a misread requirement, an API or code interpretation error, or poor time allocation.
How should you make the final scheduling decision?
Schedule only after you have checked the current Cisco exam title and confirmed that your study materials match the successor’s published scope. Your readiness decision should rest on evidence from mixed practice: you can explain the six domain areas, work through API behavior, connect Cisco platforms to automation tasks, apply security reasoning, and use network fundamentals to troubleshoot the result.
A final readiness review
First, revisit every task in the official blueprint and label it strong, review, or weak. Second, complete an integrated exercise without following a step-by-step solution. Third, review your error log and verify that each repeated mistake now has a corrected rule. Fourth, check the current Cisco page for the exam name and administrative details before scheduling.
If one domain remains weak, do not automatically restart the entire course. Select the smallest set of exercises that addresses the gap, then retest it in a mixed scenario. This keeps the final phase focused on decisions and execution rather than passive repetition.
What to do after booking
Once scheduled, freeze the scope of your preparation. Use the official blueprint as the authority, keep practice tasks short and varied, and stop adding unrelated tools merely because they appear in community discussions. Reserve the final review for API workflows, security checks, platform distinctions, network reasoning, and the personal error log.
If your certification record or transition status is the reason for taking the exam, resolve that administrative question with Cisco before studying around an assumption. The distinction between a historical DEVASC record, an automatically migrated certification, and a new CCNA Automation attempt affects the action you need to take next.
Where should candidates verify the details?
Use Cisco’s current exam page for the successor exam and Cisco’s transition announcement for the change from DevNet Associate to CCNA Automation. Use the former exam overview, exam-topics page, v1.1 blueprint, and release notes to understand the historical DEVASC scope and organize study. These sources should take priority over undated summaries or copied training pages.
Official source checklist
The current Cisco CCNA Automation exam page identifies 200-901 CCNAAUTO as Automating Networks Using Cisco Platforms and describes the certification outcome. The Cisco transition announcement explains the February 3, 2026 change, the unchanged content statement, and certification migration. The former DEVASC overview supplies the historical exam identity and delivery details.
The former exam-topics page supplies the published domain emphasis and examples such as REST requests, webhooks, HTTP response codes, authentication, requests, Python, SDKs, and Cisco platforms. The v1.1 blueprint lists the six domains, while the release notes explain that domain identities remained the same even though selected tasks were updated.
Conclusion
DEVASC preparation is now best understood as preparation for the current CCNA Automation successor, using the former DEVASC blueprint as the evidence base for the unchanged technical scope Cisco describes. Confirm the exam name and administrative details first, then study through integrated tasks: design code, use APIs, understand Cisco platforms, secure applications, automate infrastructure, and apply network fundamentals. Your next action is to open the official blueprint, mark your weakest domain tasks, and build a small practice sequence that produces evidence of what you can actually do.