Network automation has moved from "future skill" to "current requirement" faster than most network engineers expected. Job postings for senior network engineers increasingly list Python, Ansible, and REST API experience alongside routing protocol knowledge. Cisco's DevNet certification track was created specifically for this transition — for network professionals who need programming and automation skills, and for developers who need networking context.
Here's what DevNet actually certifies and whether it belongs in your career plan.
The DevNet Certification Track
Cisco's DevNet track runs parallel to traditional networking certifications:
| Level | Certification | Code |
|---|---|---|
| Associate | DevNet Associate | 200-901 DEVASC |
| Professional | DevNet Professional | 350-901 DEVCOR |
| Expert | DevNet Expert | Lab exam |
| Specialist | Multiple | Various |
DevNet Specialist exams focus on specific platforms: Cisco DNA Center Automation, Cisco IoT, Cisco Meraki solutions, and others. They can be pursued independently without the Associate or Professional credential.
DevNet Associate (200-901 DEVASC): What It Covers
The 200-901 exam is the widest-scope exam in the DevNet track. It tests whether you can work at the intersection of software development and network infrastructure.
| Domain | Weight |
|---|---|
| Software Development and Design | 15% |
| Understanding and Using APIs | 20% |
| Cisco Platforms and Development | 15% |
| Application Deployment and Security | 15% |
| Infrastructure and Automation | 20% |
| Network Fundamentals | 15% |
Infrastructure and Automation at 20% is the domain most relevant to network engineers. It covers:
- Network automation concepts (IaC, idempotency, source of truth)
- Ansible for network configuration (playbooks, inventory, modules)
- Python for network automation (Netmiko, NAPALM, nornir)
- Terraform basics for infrastructure provisioning
Understanding and Using APIs at 20% requires genuine API literacy:
- REST API concepts (HTTP methods, status codes, authentication)
- Parsing JSON and XML responses
- Using tools like Postman or curl to interact with APIs
- WebSocket and streaming APIs
Python Requirement
DevNet Associate requires Python programming ability. Not advanced programming — but you need to be able to read Python code, write simple scripts, handle API responses, and debug common errors.
The exam doesn't require memorizing Python syntax, but it does present Python snippets and ask what they do. Candidates who have never written Python code before need 4-6 weeks of Python basics before starting DEVASC content.
Recommended Python for networking resource: Kirk Byers' Python for Network Engineers (free online) is specifically designed for network engineers without programming backgrounds. It covers the Python needed for network automation without unnecessary computer science theory.
The Cisco Platform Coverage
DEVASC tests Cisco's management and automation platforms:
Cisco DNA Center (now Cisco Catalyst Center): intent-based networking management platform. The exam tests the REST API — how to query device inventory, deploy configurations, retrieve telemetry, and interact with the intent API.
Cisco Meraki: cloud-managed networking platform with a REST API for automation. The exam tests the Dashboard API — querying device status, pushing configuration, retrieving client information.
Cisco NSO (Network Services Orchestrator): service orchestration platform. The exam covers YANG data models, NETCONF protocol, and how NSO uses these to abstract network configuration.
WebEx APIs: collaboration platform APIs for bot development and messaging automation. Lighter coverage than network platforms.
DevNet Professional (350-901 DEVCOR)
The DEVCOR exam goes significantly deeper than DEVASC. It's a 120-minute, 90-question exam that requires genuine software development capability applied to network infrastructure.
| Domain | Weight |
|---|---|
| Software Design | 20% |
| Using APIs | 20% |
| Cisco Platforms | 20% |
| Application Deployment and Security | 15% |
| Infrastructure | 25% |
Infrastructure at 25% is the largest domain. It tests:
- Infrastructure as Code with Terraform at a configuration level (not just concepts)
- Containerization and orchestration (Docker, Kubernetes) in network automation context
- CI/CD pipeline design for network changes
- Network telemetry (YANG, gNMI, streaming telemetry)
Software Design Depth
DEVCOR tests software design patterns that are new territory for network engineers:
- Design patterns: Singleton, Factory, Observer — conceptual understanding of when to use each
- Async programming: Python asyncio, handling concurrent API calls
- Testing: unit testing, mocking API responses, test-driven development concepts
- Git: branching, merging, pull requests — collaborative development workflows
"The jump from DevNet Associate to Professional is larger than most candidates expect. Associate tests whether you can use APIs and write basic scripts. Professional tests whether you can design systems that use APIs — handling errors, rate limiting, pagination, authentication token refresh, and concurrency. Those are software engineering skills, not networking skills." — Hank Preston, Cisco Developer Advocate
DevNet vs Traditional Networking Certifications: Who Should Take Which
DevNet and traditional Cisco certifications aren't competing — they're complementary. The combination of networking depth (CCNP) and automation skills (DevNet) is more valuable than either alone.
Network engineer pursuing automation skills: CCNP Enterprise → DevNet Associate → DevNet Professional. The networking knowledge from CCNP gives context to automation tasks. DevNet skills enable you to automate what you understand manually.
Developer entering network automation: DevNet Associate → DevNet Professional. The DevNet track includes Network Fundamentals (15% of DEVASC) to give developers the networking context their code will operate in.
DevOps engineer working with network infrastructure: DevNet Associate is often sufficient. The professional level is more valuable if you're designing the automation systems rather than operating them.
What DevNet doesn't replace: Traditional Cisco networking knowledge. DevNet certifications don't test routing protocols, VLANs, or troubleshooting skills. A DevNet-only engineer can write a Python script to push OSPF configuration but may not understand whether the OSPF configuration is correct for the topology. The combination of CCNA/CCNP networking knowledge with DevNet automation skills is the career-differentiated profile.
Hands-On Lab Access for DevNet
Unlike traditional Cisco certifications where Packet Tracer is sufficient, DevNet requires real API access and automation tool environments.
Cisco DevNet Sandboxes (free): Cisco provides free, reserved cloud labs with running instances of DNA Center, Meraki, NSO, and other platforms. Each sandbox has an API endpoint you can query for practice. Sandboxes are reserved through developer.cisco.com — some are always-on, others require booking.
Cisco DevNet Learning Labs (free): step-by-step tutorials integrated with sandboxes. Each learning lab walks through a specific API operation with instructions and a live environment. Complete these in order for the DEVASC domains.
The Cisco DevNet Associate DEVASC study guide (Pearson): covers all exam domains with Python code examples. More useful than generic study guides because the examples are written for the exam's specific API and platform content.
Is DevNet Worth It Without Cisco Equipment?
The question candidates ask: if I work in an AWS environment or a non-Cisco shop, does DevNet add value?
DevNet Associate: the programming, API, and automation concepts tested in DEVASC are platform-agnostic. REST APIs, Python scripting, Ansible, and Git skills apply equally to Cisco, Juniper, AWS, or any other platform. The Cisco-specific platform section (15%) is the only section that requires Cisco-specific knowledge.
DevNet Professional: more Cisco-specific. DNA Center, NSO, and YANG/NETCONF are Cisco-centric tools that may not apply to non-Cisco environments.
Bottom line: DEVASC has broader applicability than its "Cisco" branding suggests. DEVCOR is more Cisco-specific and more valuable when Cisco platforms are part of your actual work.
Python Skills Tested on DevNet Associate: What the Exam Actually Requires
DevNet Associate Python requirements are frequently mischaracterized as "you just need to know basic Python." The exam requires specific Python skills applied to network automation contexts.
What DEVASC Tests in Python
The exam presents Python code and asks candidates to identify what it does, predict output, or identify errors. Topics include:
Data types and structures:
- Dictionaries — critical for working with JSON API responses
- Lists and list comprehensions
- String formatting (f-strings, .format())
Control flow:
- Loops iterating over API response data
- Conditional logic for error handling
Functions and modules:
- Defining and calling functions with parameters
- Importing standard library modules (json, requests, os)
API interaction with the requests library:
import requests
response = requests.get('https://api.example.com/devices',
headers={'X-Auth-Token': token})
data = response.json()
This pattern — authenticating, making a GET request, parsing JSON — appears throughout DEVASC questions.
Error handling:
- HTTP status code checking (
response.status_code == 200) - try/except blocks for API errors
- Handling pagination in API responses
Network-Specific Python Libraries
The infrastructure and automation domain tests three libraries that don't appear in general Python courses:
Netmiko — SSH connections to network devices using screen-scraping:
- Connects to Cisco, Juniper, and other devices via SSH
send_command()for show commands,send_config_set()for configuration- When to use vs API-based approaches: Netmiko works on devices without REST APIs (older IOS, non-Cisco equipment)
NAPALM (Network Automation and Programmability Abstraction Layer with Multivendor support):
- Vendor-neutral library providing the same function calls across Cisco IOS, Juniper Junos, Arista EOS
get_interfaces(),get_bgp_neighbors(),get_facts()return structured data regardless of underlying platform- Key advantage for multi-vendor environments — one code base manages heterogeneous networks
Nornir — parallel task execution for large-scale network automation:
- Runs tasks across hundreds of devices simultaneously using threads
- Integrates with Netmiko and NAPALM
- When to use: automating changes across large networks where running Netmiko serially would take too long
| Library | Use Case | Interaction Method | Data Format |
|---|---|---|---|
| Netmiko | SSH to any device | Screen-scraping | Raw CLI text |
| NAPALM | Multi-vendor abstraction | SSH + API | Structured Python dicts |
| Nornir | Parallel execution framework | Varies (uses other libs) | Varies |
| Requests | REST API calls | HTTP | JSON/XML |
YANG Data Models and NETCONF/RESTCONF: What DevNet Depth Actually Means
YANG, NETCONF, and RESTCONF appear on DEVASC but at a lower depth than on DEVCOR. Understanding the distinction prevents both over-studying and under-preparing.
YANG Data Models
YANG (Yet Another Next Generation) is a data modeling language that describes the structure of network configuration data. Think of it as a schema that defines what parameters a router interface can have.
What DEVASC tests:
- What YANG models are and why they exist (standardize network configuration data structures)
- Key YANG constructs: modules, containers, lists, leafs, leaf-lists
- How to read a simplified YANG model and understand what it describes
What DEVASC does NOT test:
- Writing YANG models from scratch
- Complex YANG features (augmentation, deviation, groupings in depth)
A YANG container for interface configuration looks like this conceptually:
container interface {
leaf name { type string; }
leaf description { type string; }
leaf ip-address { type inet:ipv4-address; }
}
The exam tests recognizing this structure, not authoring it.
NETCONF
NETCONF is an IETF protocol for network configuration management that uses YANG data models as its data format. It communicates over SSH using XML.
Key NETCONF concepts for DEVASC:
- Operations:
get,get-config,edit-config,commit,lock,unlock - Datastores: running (active config), candidate (staged config), startup (boot config)
<filter>elements to retrieve specific configuration subtrees
RESTCONF
RESTCONF is NETCONF's REST API equivalent — it exposes YANG-modeled network configuration over HTTP using JSON or XML. Easier to work with than NETCONF for developers familiar with REST APIs.
"NETCONF and YANG are the foundation of network programmability. The entire model-driven telemetry movement — gNMI, gRPC streaming, OpenConfig — builds on the concept of structured data models for network state. Network engineers who understand YANG models can navigate any modern programmable platform. Those who learn only screen-scraping and CLI automation are building on sand." — Jason Edelman, founder of Network to Code and author of Network Programmability and Automation
Career Paths and Salary Data for Network Automation
The salary differential between traditional network engineering and network automation roles is significant and growing.
Job Titles and Market Positioning
Traditional Network Engineer: configures and troubleshoots network devices manually. Routing, switching, firewall management. Tool: CLI.
Network Automation Engineer: writes code to automate network configuration, change management, and compliance checking. Tools: Python, Ansible, Terraform, Git, Cisco NSO.
Infrastructure as Code Engineer: defines network and compute infrastructure in version-controlled code. Works across network, compute, and cloud. Tools: Terraform, Ansible, Python, cloud-specific tools.
Site Reliability Engineer (SRE) — Network Focus: combines software engineering practices with network operations. Incident response automation, monitoring system development, change velocity improvement.
Approximate Compensation Ranges (US, 2024 market)
| Role | Years Experience | Approximate Salary Range |
|---|---|---|
| Network Engineer (no automation) | 3-5 years | $75,000-$100,000 |
| Network Engineer (Python + Ansible) | 3-5 years | $90,000-$120,000 |
| Network Automation Engineer | 3-5 years | $110,000-$145,000 |
| Sr. Network Automation Engineer | 7+ years | $140,000-$180,000 |
| Network SRE | 5+ years | $150,000-$200,000+ |
Data from job postings on LinkedIn and Indeed, cross-referenced with compensation surveys from Network Collective and the NANOG community, represents ranges rather than guarantees.
The DevNet certification's role in this market: DEVASC and DEVCOR signal that a network engineer has invested in automation skills. They don't guarantee a salary increase, but they support the career positioning required to move from traditional networking roles to automation-focused roles.
Which Certifications Stack Best
For network automation career advancement, the most effective combination is a deep networking credential (CCNP Enterprise or CCNP Data Center) paired with DevNet certifications:
- CCNA → established networking foundation
- Python basics (Kirk Byers' course or equivalent) → programming prerequisite
- DevNet Associate → validates programming + networking intersection
- CCNP Enterprise (ENCOR) → deep networking knowledge
- DevNet Professional → advanced automation and system design
This sequence takes approximately 2-3 years of dedicated part-time study and positions candidates for senior network automation or infrastructure-as-code roles.
DevNet Associate Exam: Domain-by-Domain Preparation
Exam format: 120 questions, 120 minutes, multiple choice and multiple select. Cost: $330. Validity: 3 years.
DevNet Associate covers six domains:
| Domain | Weight | Core Topics |
|---|---|---|
| Software Development and Design | 15% | Software design patterns, version control (Git), test-driven development |
| Understanding and Using APIs | 20% | REST principles, HTTP methods, authentication (OAuth, API keys), API documentation |
| Cisco Platforms and Development | 15% | DNA Center API, Meraki API, Webex API, NSO (Network Services Orchestrator) |
| Application Deployment and Security | 15% | Containers (Docker), CI/CD concepts, security in development |
| Infrastructure and Automation | 20% | Ansible, Terraform, configuration management concepts |
| Network Fundamentals | 15% | Networking protocols supporting programmability |
The APIs domain (20%) requires hands-on practice: reading API documentation and making curl requests is not sufficient preparation for this domain. Candidates who build Python scripts that call real Cisco APIs — even simple ones like listing DNA Center sites or retrieving Meraki network information — understand the request-response cycle at the depth exam questions test.
The Infrastructure and Automation domain (20%) tests Ansible and Terraform at a conceptual and basic-usage level for DevNet Associate. The exam tests whether you can read an Ansible playbook and understand what it does, or identify what a Terraform module does based on its resource blocks — not whether you can write production-grade automation.
Building a DevNet Study Lab
The barrier to DevNet lab practice is lower than candidates expect. Cisco provides free access to most platforms the exam tests:
Cisco DevNet Always-On Sandboxes (free, no reservation needed):
- Cisco IOS XE on CSR1000v: SSH and REST API access to a Cisco router
- Cisco DNA Center: full GUI and API access to a network management controller
- Cisco Meraki: API access to a simulated Meraki organization
- Open NX-OS (Nexus switch emulator): SSH and RESTCONF access
The 30-minute lab exercise that builds API fluency: using the always-on DNA Center sandbox, write a Python script that:
- Authenticates and receives a token (POST request to auth endpoint)
- Retrieves the list of managed devices (GET with authentication header)
- Prints device hostnames and types
This exercise touches every concept the exam tests about REST APIs: authentication flow, HTTP methods, headers, JSON response parsing. Candidates who complete this exercise understand API concepts operationally rather than just theoretically.
Network Automation Career Paths
Traditional vs automation-hybrid roles: network engineers who add automation skills don't typically transition entirely into software engineering. They occupy network automation engineer and NetDevOps engineer roles that combine deep networking knowledge with sufficient programming skills to build and maintain automation tooling.
The rare engineer profile DevNet targets: someone who understands why OSPF neighbor adjacency fails and can also write the Ansible playbook to remediate it at scale. This combination is genuinely scarce and commands premium compensation.
Job titles: Network Automation Engineer, NetDevOps Engineer, Infrastructure Automation Engineer, Network Reliability Engineer, Cloud Network Engineer.
Salary context: network automation engineers in US markets earn $110,000-$160,000 at mid-senior levels — roughly $20,000-$30,000 above equivalent traditional network engineers. The premium reflects the combination of networking depth and automation capability that makes these engineers able to operate at scale in a way that pure networking or pure automation specialists cannot.
"DevNet certification proves you can speak both languages — networks and code. That's genuinely rare. A network engineer who can write Python scripts to pull information from the network, spot anomalies, and push configurations back via API is worth considerably more than either a pure network engineer or a pure Python developer without networking knowledge." — Hank Preston, Cisco developer advocate and DevNet Associate Official Cert Guide author
See also: CCNA study guide: what to know before you start, CCNP Enterprise: how to prepare for the core and concentration exams
References
- Cisco. DevNet Certifications — Overview and Exam Topics. Cisco DevNet, 2024. https://developer.cisco.com/certification/
- Preston, Hank. DevNet Associate DEVASC 200-901 Official Cert Guide. Cisco Press, 2020. ISBN: 978-0136642312. (Official Cisco Press guide from Cisco's own developer advocate)
- Byers, Kirk. Python for Network Engineers. PyNEng, 2024. https://pyneng.readthedocs.io (Free online resource specifically for network engineers learning Python)
- Cisco. DevNet Sandbox — Free Cisco API Labs. Cisco DevNet, 2024. https://developer.cisco.com/site/sandbox/ (Free reservable lab environments for all Cisco DevNet platforms)
- Cisco. DevNet Learning Labs — Step-by-Step API Tutorials. Cisco DevNet, 2024. https://developer.cisco.com/learning/labs/ (Free structured tutorials integrated with sandbox environments)
- Boson Software. ExSim-Max for Cisco DevNet Associate 200-901. Boson, 2024. https://www.boson.com (Practice exam platform with DEVASC-specific question bank)
Frequently Asked Questions
Do I need to know Python for the DevNet Associate exam?
Yes. The exam presents Python code snippets and asks what they do. You need to read Python, understand basic data structures (lists, dictionaries), handle JSON responses, and write simple scripts. Complete beginners need 4-6 weeks of Python basics before starting DEVASC content.
Is DevNet Associate useful if I don't work with Cisco equipment?
Mostly yes. REST APIs, Python automation, Ansible, Git, and Infrastructure as Code concepts are platform-agnostic — they apply to any vendor or cloud environment. The Cisco-specific platform section is only 15% of the exam. DevNet Associate signals automation skills that are broadly applicable.
What free labs are available for DevNet preparation?
Cisco DevNet provides two free resources: DevNet Sandboxes (reservable cloud environments with running DNA Center, Meraki, NSO instances for API practice) and DevNet Learning Labs (step-by-step tutorials integrated with sandbox environments). Both are available at developer.cisco.com.
What is the difference between DevNet Associate and DevNet Professional?
DevNet Associate tests whether you can use APIs and write basic automation scripts. DevNet Professional tests whether you can design automation systems — handling concurrent API calls, rate limiting, error recovery, CI/CD pipeline design, and Terraform IaC at a configuration level. The professional level requires genuine software engineering skills.
Should I pursue DevNet or CCNP first?
CCNP first for network engineers. DevNet automation skills are most effective when applied to networking knowledge you already have — you can't automate network configurations you don't understand. Network engineer who can automate is more valuable than developer who knows network APIs without networking context.