DevNet Associate (DEVASC) Exam Guide: What the Former Exam Covered and How to Prepare for Its Successor
The former Cisco DevNet Associate exam validated entry-level ability to develop software, use APIs, work with Cisco platforms, secure applications, and automate infrastructure. It served developers, network engineers, and automation practitioners who needed to connect code with network and security systems. Cisco changed the track on February 3, 2026: DEVASC became part of the CCNA Automation path, and the successor is 200-901 CCNAAUTO, Automating Networks Using Cisco Platforms. This guide helps you decide whether your preparation should follow the unchanged DEVASC content or the current certification name and booking information.
Is DEVASC still the exam name?
No. Cisco states that the DevNet certification track transitioned to the CCNA, CCNP, and CCIE Automation track effective February 3, 2026. The former DevNet Associate certification became CCNA Automation, while the successor exam is 200-901 CCNAAUTO, titled Automating Networks Using Cisco Platforms. Before scheduling, verify the current exam record rather than searching only for the former DEVASC label.
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 understanding the subject matter, but it does not make the old name the correct assumption for registration, delivery details, or certification status.
The practical decision is straightforward: use the DEVASC topics to organize study, then use Cisco’s current CCNA Automation exam page for the name and any time-sensitive booking information. Passing 200-901 CCNAAUTO earns the CCNA Automation certification and can also count toward recertification goals, according to Cisco.
What happened to existing DevNet certifications?
Cisco states that active DevNet certifications were automatically migrated to the corresponding Automation certifications on February 3, 2026. Candidates holding an active credential should therefore check their Cisco certification account for the resulting designation instead of assuming that the former title remains current.
Who should use this preparation path?
This subject area suits candidates who can combine basic programming with networking and platform operations. It is particularly relevant to software developers working with Cisco services, network engineers adding automation skills, and infrastructure practitioners who need to consume APIs, write Python scripts, and reason about application security.
The former exam assessed software development and design, API usage, Cisco platforms and development, application development and security, and infrastructure and automation. The blueprint also included Network Fundamentals as one of its six domains. You do not need to treat the exam as a pure programming test or a traditional routing exam; preparation must connect both sides.
A useful readiness test is whether you can explain what a script is doing, identify the correct API interaction, interpret an HTTP response, and recognize how an automated change affects infrastructure. If one of those steps is unfamiliar, begin with that weakness rather than starting with product names.
What background is useful?
Cisco’s listed topics point toward practical familiarity with Python, REST APIs, authentication, webhooks, HTTP response codes, and network concepts. The blueprint also referenced Cisco SDKs and several Cisco platforms. Candidates may come from different technical backgrounds, so use the official topic list to locate gaps rather than treating an informal prerequisite list as an admission requirement.
What skills did the blueprint measure?
The DEVASC v1.1 blueprint grouped the content into six domains: Software Development and Design, Understanding and Using APIs, Cisco Platforms and Development, Application Development and Security, Infrastructure and Automation, and Network Fundamentals. These labels are more useful than a product-only study plan because they show the range of decisions the candidate must make.
Cisco’s release notes state that all exam domains remained identical compared with v1.0, although some tasks changed for product naming, end-of-life products, and Terraform use. Use the current official topic document as the controlling study outline, especially where older notes or courses use outdated product names.
The blueprint is a map of examinable skills, not a promise that every product receives equal attention. Read each task, turn it into something you can explain or perform, and record the evidence you have for readiness. A completed product-name checklist is not a substitute for understanding the underlying automation pattern.
Software Development and Design
This domain carried 15% of the former DEVASC blueprint. Study data types and structures, control flow, functions, modules, error handling, testing, version control, and the design choices that make automation maintainable. Practice reading short Python fragments and predicting their behavior before you run them.
The important preparation decision is whether you are learning syntax in isolation. Instead, write small scripts that accept input, validate it, call a service, handle failure, and return a useful result. That sequence ties programming concepts to the automation work the wider blueprint describes.
Understanding and Using APIs
Understanding and Using APIs carried 20% of the former DEVASC blueprint. This is the largest percentage explicitly identified in the supplied DEVASC exam-topics evidence, so it deserves early attention. Work with REST requests, resources, methods, headers, payloads, authentication, response codes, pagination, and webhooks.
Cisco’s blueprint specifically included API styles, API authentication, HTTP response codes, REST API requests, webhooks, and Python scripts using the requests library. Do not memorize isolated status-code definitions. Build a request, inspect its response, decide whether the result is success or failure, and determine what the client should do next.
Cisco Platforms and Development
The blueprint included Python scripting with Cisco SDKs and knowledge of Cisco platforms such as Meraki, Cisco DNA Center, ACI, Cisco SD-WAN, NSO, Webex, Firepower, Umbrella, and ISE. The study challenge is breadth: learn the purpose and automation interface of each named platform without pretending that one product behaves like all the others.
Create a comparison sheet with four columns: platform purpose, object or resource being automated, access method, and an example of a safe operation. Keep product facts tied to the official topic document and current Cisco terminology. Where a platform has changed naming or lifecycle status, follow the current blueprint rather than an old tutorial.
Application Development and Security
This domain requires more than making a request succeed. Prepare to reason about input validation, secrets, authentication, authorization, transport protection, logging, dependency risk, and the consequences of exposing an API token. Pair each coding exercise with a security review: what is trusted, what is sensitive, and what should be rejected or recorded?
A common mistake is to study security as a list of acronyms after finishing development. Put security into every practice script. Keep credentials outside source code, validate data before using it, distinguish authentication from authorization, and consider how errors might reveal implementation details. These are preparation practices, not claims about the wording of live questions.
Infrastructure and Automation
Infrastructure and Automation connects code to repeatable changes across systems. Study automation workflows, configuration data, orchestration concepts, source control, testing, idempotent behavior, and the role of tools named in the current blueprint. The v1.1 release notes specifically mention updates involving Terraform use, so older material should be checked for alignment.
Practice by describing a change before implementing it: desired state, inputs, dependencies, validation, rollback or recovery, and evidence that the change worked. This approach prevents a frequent error—equating a successful command with a reliable automation process.
Network Fundamentals
Network Fundamentals is one of the six official domains. Review the concepts needed to understand automated network behavior: addressing, transport, common protocols, routing and switching roles, network services, and the relationship between a client, an API, and the managed device or platform.
Do not leave networking until the final week because the exam’s automation questions depend on it. When an API call fails, you should be able to separate a coding error from authentication failure, DNS trouble, transport failure, or an incorrect network assumption.
How should you sequence your study?
Begin with APIs and Python, then connect those skills to Cisco platforms, security, infrastructure automation, and network fundamentals. This order follows the dependencies between the topics: you need to understand a request before using an SDK, and you need networking and security context before diagnosing an automation failure.
Use the official v1.1 blueprint as a task checklist. For every task, mark one of three states: can explain, can perform, or needs work. The third category should drive your next lab. A topic is not ready merely because you have watched a lesson or copied a code sample.
Because Cisco says the former content remains unchanged under the CCNA Automation version, you can retain useful DEVASC notes while replacing obsolete labels and checking product-specific material. Do not, however, assume that an old scheduling page, language statement, or delivery description is current.
A six-stage study cycle
Stage one is orientation. Download and read the official exam-topics document, list the six domains, and identify which topics you have encountered in real work. Mark unfamiliar product names and programming concepts separately; they require different kinds of study.
Stage two is Python. Review variables, collections, conditionals, loops, functions, modules, exceptions, file handling, and testable structure. Write small programs without relying on copy-and-paste. Your goal is to read and modify automation code confidently.
Stage three is API work. Use a safe practice service or an approved lab environment to send requests with Python’s requests library. Inspect methods, URLs, headers, payloads, authentication behavior, response codes, and returned data. Add a webhook or event-driven exercise if your environment supports one.
Stage four is platform mapping. Study the purpose of the Cisco platforms named in the blueprint and connect each to its API, SDK, or automation role. Avoid trying to memorize every command. Build enough conceptual distinction to choose the appropriate platform or interface in a scenario.
Stage five is secure automation. Refactor your scripts to remove embedded secrets, validate inputs, handle errors, record useful logs, and avoid unsafe assumptions. Add tests for both expected responses and failure paths.
Stage six is integration and review. Take a small end-to-end task—such as retrieving information, filtering it, making a controlled change, and verifying the result—and explain every step. Then revisit the blueprint and close any remaining ‘needs work’ entries.
What should a practical lab contain?
A useful lab has an input, a decision, an API interaction, an error path, and a verification step. For example, a script might accept a resource identifier, authenticate safely, retrieve structured data, check the response, apply a permitted change, and confirm the resulting state. The value comes from the reasoning around the workflow, not from its size.
Keep a short lab record. Note the endpoint or SDK method, required authentication, expected response, failure symptoms, and the test that proves the desired result. This record becomes a revision tool and exposes gaps that passive reading hides.
Use environments you are authorized to access. Never experiment against production infrastructure simply to create a more realistic exercise. A controlled sandbox, mock service, or documented learning environment is sufficient for practicing request construction, parsing, validation, and error handling.
How can you study the Cisco platform breadth?
Use a platform matrix rather than separate piles of notes. For each platform named in the blueprint, write what it manages, why an automation client would contact it, which interface or SDK is relevant, and what kind of result the client should validate. This keeps product study tied to decisions instead of turning into disconnected memorization.
Review the official topic page and v1.1 document together when a course uses an older product name or an obsolete example. Cisco’s release notes explicitly identify naming, end-of-life product, and Terraform-related task updates. That is a reason to verify material, not a reason to discard the whole study plan.
Which exam details can you rely on?
The former DEVASC exam was numbered 200-901, associated with Cisco Certified DevNet Associate, and listed with a duration of 120 minutes. Cisco’s exam overview also described it as available in English. Those facts describe the former exam record; they should not be silently presented as current booking terms for 200-901 CCNAAUTO.
For the current exam name, Cisco identifies 200-901 CCNAAUTO as Automating Networks Using Cisco Platforms. Confirm current registration, delivery options, language availability, identification rules, and other scheduling details on Cisco’s live exam page before making a booking. The supplied evidence does not establish updated values for those operational details.
Do not plan around an assumed score, question count, price, or delivery format. None of those details is established by the supplied research. Treat third-party listings as leads only and verify any time-sensitive claim with Cisco.
What is the safest scheduling workflow?
First confirm that the target is 200-901 CCNAAUTO rather than the former DEVASC name. Next open Cisco’s current CCNA Automation exam page and check the available registration path and conditions. Finally compare the booking information with your own preparation status, work commitments, and access to a suitable testing environment.
Schedule only after you can explain the blueprint domains and demonstrate the core workflow in practice. A calendar date can create useful discipline, but it cannot replace missing API, Python, security, or networking skills. If the official page changes, let that page override older notes.
What mistakes waste preparation time?
The most expensive mistake is studying an outdated exam identity. Candidates can spend time searching for former DEVASC registration details when Cisco has moved the track to CCNA Automation. Resolve the naming issue first, then use the unchanged content statement to preserve relevant study work.
Another mistake is treating the blueprint as a product catalog. Knowing that Meraki, Cisco DNA Center, ACI, Cisco SD-WAN, NSO, Webex, Firepower, Umbrella, and ISE appear in the blueprint is not the same as knowing how automation interacts with them. Build comparisons and workflows instead of collecting product definitions.
A third mistake is overfitting to code memorization. A copied request can work while the candidate remains unable to explain authentication, response handling, data validation, or recovery. Rewrite examples, change inputs, introduce a controlled failure, and explain why the client behaves correctly.
Do not ignore networking because the target has ‘developer’ in its former name. API calls depend on network services and transport behavior, and infrastructure automation changes systems that have operational consequences. Conversely, do not assume networking knowledge makes Python and API practice unnecessary.
Finally, avoid exam dumps, leaked questions, and promises that memorization guarantees a pass. They do not build transferable troubleshooting skill and may leave you unprepared for a changed or updated assessment. Use the official blueprint, authorized learning resources, and your own lab evidence.
How do you know a topic is really ready?
Ask yourself to perform three actions without a script copied from a lesson: explain the concept in plain language, implement or inspect a small example, and diagnose one plausible failure. If you can only recognize a definition, keep studying. If you can perform the task but cannot explain the security or network impact, add review rather than marking it complete.
What should you do in the final review?
The final review should expose weak links, not introduce an entirely new syllabus. Re-read the six domain names, revisit every blueprint task marked ‘needs work,’ and run a small integrated lab. Concentrate on explaining choices: why this method, this authentication approach, this data structure, this validation rule, and this verification step.
Create a one-page recall sheet from your own notes. Include API methods and response handling, Python constructs you frequently confuse, security checks, platform distinctions, infrastructure workflow stages, and network concepts that affect troubleshooting. Keep it concise enough to test memory, then verify it against the official sources rather than treating it as authoritative.
In the last study session, stop expanding the product list. Resolve terminology conflicts, confirm the current exam name, gather identification and scheduling information from Cisco, and prepare the environment or logistics required by the official delivery route. The purpose of the final session is confidence in decisions, not more passive reading.
What are the next actions after reading this guide?
Open Cisco’s current CCNA Automation page and confirm the target exam identity. Download the DEVASC v1.1 topics document, list the six domains, and label each task as can explain, can perform, or needs work. Start with API and Python gaps, then build one secure, testable automation workflow that touches the concepts you intend to retain.
After that baseline, revisit Cisco’s release notes for terminology and task updates, especially if your materials predate v1.1. Keep your study evidence in a single document: lab results, failed assumptions, corrected notes, and questions for further research. This gives you a defensible basis for deciding when to schedule rather than relying on familiarity with course screens.
Which Cisco sources should anchor your plan?
Use the official exam-topics page and the DEVASC v1.1 blueprint for scope. Use Cisco’s transition announcement and CCNA Automation exam page for the current certification name and successor exam. Use the former exam overview only for clearly labeled historical details, such as the former number, duration, and language statement.
The sources below are the evidence base for this guide. Recheck the live Cisco pages before registration because certification names, scheduling information, and delivery conditions can change.
Source-use note
The former DEVASC material remains useful for content planning because Cisco states that the content was unchanged in the CCNA Automation version. The current exam page remains the authority for what a candidate should select when scheduling. Keeping those two uses separate prevents a valid study blueprint from becoming an outdated registration instruction.
Conclusion
Prepare for the skills, but schedule against the current certification record. The former DEVASC blueprint gives you a practical structure: Python and software design, API use, Cisco platform development, secure application work, infrastructure automation, and network fundamentals. Cisco’s transition information says that this content continues under 200-901 CCNAAUTO, while the credential is now CCNA Automation. Build and troubleshoot small, secure workflows, verify every topic against the official blueprint, and confirm current booking details before you commit to an exam date.
