ExamSprintLab

200-901 study plan: pass in 4 weeks

Updated October 9, 2026

Four weeks is realistic for 200-901 if you can already read a little Python and you study 8 to 10 hours a week. The order matters: start with code, data formats and Git, move to REST APIs, which every later domain reuses, then cover Cisco platforms, and finish with deployment, automation and network fundamentals. If you have never programmed, double the timeline and spend the extra weeks on Python basics.

Before you start

  • Read the official exam topics once, end to end. The six domains and their sub-objectives are two to three pages.
  • Install Python 3, pip, Git and Docker on a machine you can break. A Linux shell is ideal, because the exam asks about bash.
  • Create a free Cisco account and look at the DevNet Sandbox. Always-on sandboxes let you call real APIs without owning any hardware.
  • Do one pass of the free practice test cold. The domain scores tell you where to spend time.

Week 1: software development and Git (15%) and the start of APIs

Goal: be comfortable with code, data formats and version control.

  • Data formats: write the same object in JSON, YAML and XML, then parse each into Python dictionaries and lists.
  • Python: functions, classes and modules, json and yaml loading, exceptions, and the unittest module.
  • Methods and patterns: TDD red, green, refactor; agile, lean and waterfall; MVC and Observer.
  • Git: clone, add, commit, push, pull, branch, merge, resolve a conflict, and read git diff.

Lab: a small Python script with two functions, a unit test for each, committed to a repository with a feature branch that you merge after creating and resolving a deliberate conflict.

Week 2: understanding and using APIs (20%)

Goal: construct a request from documentation and diagnose a response.

  • HTTP: methods, headers, query parameters, status code families and which codes you expect from each method.
  • Authentication: basic, bearer or custom token, and API keys, and where each one travels in the request.
  • Constraints: rate limiting, pagination, timeouts and retries.
  • Webhooks: how they differ from polling and what a receiver must do.
  • API styles: REST, RPC, synchronous and asynchronous.
  • The requests library: get, post, headers, params, json, timeout, raise_for_status() and .json().

Lab: call a public REST API from Python, add a header, handle a 404 and a 429, and page through a long list.

Week 3: Cisco platforms and development (15%) and infrastructure and automation (20%), part 1

Goal: know what each platform is for and how its API authenticates.

  • Network platforms: Meraki, Catalyst Center, ACI, Catalyst SD-WAN and NSO. Learn the object hierarchy and the typical call to list devices.
  • Compute, collaboration and security: UCS Manager, Intersight, Webex, CUCM with AXL and UDS, XDR, Firepower, Secure Connect, Secure Endpoint, ISE and Secure Malware Analytics.
  • Device level: NETCONF, RESTCONF, YANG models, and the programmability interfaces of IOS XE and NX-OS.
  • DevNet resources: which of Sandbox, Code Exchange, Learning Labs, forums and API documentation fits a given need.

Lab: reserve or use an always-on sandbox, get a token, and list devices or clients with Python. Then run a RESTCONF GET against a device and read the reply.

Week 4: deployment, automation, network fundamentals and review

Goal: read infrastructure artefacts and close the networking gap.

  • Deployment (15%): private, public, hybrid and edge; virtual machines, bare metal and containers; Dockerfile instructions; CI/CD stages; OWASP threats; secrets and encryption; bash commands.
  • Automation (20%): infrastructure as code, Ansible playbooks, Terraform, NSO, CML and pyATS, controller versus device management, unified diffs, code review and sequence diagrams.
  • Network fundamentals (15%): MAC and IP addressing, VLANs, subnet masks, DHCP, DNS, NAT, SNMP, NTP, common ports, the three planes and diagnosing a blocked port or NAT problem.

Review: take the practice test again mid-week and spend the last days on the lowest domain, using the domain guides in this section.

If you are already experienced

Network engineers can compress week 4 and spend the time on Python, Git and Docker, which are the usual gaps. Developers can compress weeks 1 and 2 and spend the time on network fundamentals and on the platform list, which is the part with the most facts to memorise. If you already hold the CCNA, see 200-901 vs CCNA for what carries over.

How to know you are ready

  • You can write a requests call with a header, a query string and error handling from memory.
  • You can say which HTTP status code a given failure produces and what to change in the request.
  • You can read a Dockerfile, an Ansible playbook and a unified diff and describe what each does.
  • You can name the authentication method and the main object for each Cisco platform in domain 3.
  • You score 80% or more on realistic practice questions twice in a row, on different sets.

Then book it. See the exam format for the mechanics and the exam day guide for the day itself.