DevNet Associate study materials
DevNet Associate study resources

DevNet Associate case studies

DevNet Associate · Put your knowledge to work in context.

The Cisco Certified DevNet Associate - exam code 200-901, often shortened to DEVASC - is an associate-level credential aimed at people who work where software development meets network infrastructure. It suits junior developers building against network APIs, network engineers moving into automation, and operations staff who script repetitive tasks. The DevNet Associate case studies are 5 cases and about 3,695 words.

1

Inventory Script That Returns a Different Number Every Run

You maintain a Python inventory script for 4,200 wireless access points behind a vendor REST API. Each call returns at most 500 objects plus a nextCursor field, and the API allows 100 requests per minute per token - a token your monitoring job also uses.

682 words, about 3 min
2

Reviewing a Merge Request on a 600-Line Network Script

A team of three network engineers maintains sync vlans.py , a 600-line single-file script that pushes VLAN definitions to 180 switches. The key function is def push(device, cmds, dry run=False, log=[]) .

713 words, about 4 min
3

Change-Alert Bot That Dies After an Hour

An internal Flask service polls DNA Center every five minutes, diffs the device list against the previous poll, and posts change alerts into a Webex space. It authenticates to DNA Center once at startup, stores X-Auth-Token in a module-level variable, and reuses it for the life of the process.

752 words, about 4 min
4

Public Webhook Receiver With Three Problems and One Deadline

A Flask app receives configuration-change webhooks from a SaaS platform and opens a ticket for each event. It runs on a public VM behind nginx: nginx terminates TLS and proxies to gunicorn in a container running as root.

758 words, about 4 min
5

240 Switches, no Failed Hosts, and 50 Unchanged Devices

An Ansible playbook pushes syslog and NTP settings to 240 IOS-XE switches with serial: 10 . The task uses ios command with a show run fragment, has ignore errors: true , and the final recap printed ok=240 failed=0 , yet post-change verification found about 50 switches still running the old syslog server.

790 words, about 4 min