200-901 study scenarios: three starting points
The right way to study for 200-901 depends on which side of the network-and-software divide you come from. The exam lasts 120 minutes, is graded pass or fail, and weights six domains almost evenly: APIs (20%) and infrastructure and automation (20%) lead, while software development, Cisco platforms, deployment and security, and network fundamentals are 15% each. Because no domain is below 15%, nobody can skip a side, and each starting point leaves a different hole to fill.
Example profiles, not real people. The profiles below are illustrative planning examples built from the official exam outline. They are not reviews or reports of anyone’s result.
The network engineer who has never written code
Starting point. This profile configures switches and routers by hand and is comfortable with VLANs, addressing, DHCP, DNS and NAT. It has not used Python, Git or containers, and reads JSON or YAML only as something other people produce.
Where the time goes. Domain 6 (network fundamentals, 15%) is largely already done, and most of the networking parts of domains 3 and 5 are familiar in concept. The hours belong to domain 1 (software development and design, 15%), domain 2 (APIs, 20%) and the deployment topics in domain 4 (15%): Python basics, Git, HTTP methods and status codes, Dockerfiles and CI/CD stages.
The trap. Reading about programming instead of typing it. The exam asks you to interpret short Python, a unified diff, a Dockerfile and an Ansible playbook, and recognition from reading alone is too shallow for items that change one line and ask for the result.
Suggested order. Data formats and Python, Git, the requests library and HTTP, then platform APIs, then deployment and automation artefacts, with a quick network refresher last.
Planning assumption. The site’s study plan says that with no programming background the four-week timeline should be doubled. A reasonable planning assumption is eight weeks at 8 to 10 hours, spending the added weeks on Python basics. This is a planning figure, not a guarantee.
The developer who has never configured a network
Starting point. This profile writes code and uses REST APIs, JSON and Git daily, and has probably met Docker and a CI pipeline. Subnet masks, VLANs, NAT and the control, data and management planes are unfamiliar.
Where the time goes. The software-heavy domains, 1 and 2 (35% together), can be compressed to a skim. The time goes to domain 6 (15%), which is a full networking primer in miniature, and to domain 3 (15%), the platform list: Meraki, Catalyst Center, ACI, SD-WAN, NSO and the collaboration and security products, each with its own authentication method and object hierarchy. That is a memory task, not a coding task.
The trap. Assuming that the networking domain is small enough to guess. At 15% it is the same size as software development, and scenario items ask you to diagnose a blocked port or a NAT problem. A developer who skips it gives away 15% of the paper.
Suggested order. Network fundamentals first, because platform APIs make more sense once you know what a VLAN or a device inventory is, then Cisco platforms, then infrastructure and automation (20%), then a fast review of APIs and Git.
Planning assumption. The study plan suggests compressing weeks 1 and 2 for developers. About three to four weeks at 8 to 10 hours a week is a reasonable assumption, with the extra time on domains 6 and 3.
The CCNA holder who wants the automation badge
Starting point. This profile holds or has recently studied the CCNA and has run small scripts or Ansible at a basic level. The networking content is known; the programming is partial.
Where the time goes. On domain 5 (infrastructure and automation, 20%) and domain 2 (APIs, 20%), where the exam reads NETCONF and RESTCONF replies, YANG models and playbooks. Domain 6 is revision. The CCNA does not teach HTTP status codes, authentication methods or the platform catalogue, so domain 3 is largely new as well.
The trap. Over-trusting the networking credential. The 200-901 vs CCNA comparison describes the overlap between the two exams as small, and a CCNA holder who treats this as a light top-up tends to underprepare the 40% in APIs and automation.
Suggested order. Start with one practice pass to find the weakest domain, then APIs and the platform list, then automation artefacts, with network fundamentals as a final refresh.
Planning assumption. About three weeks at 8 to 10 hours a week is a reasonable assumption, with most hours on domains 2, 3 and 5.
The three 200-901 profiles compared
| Profile | Front-loaded domains | Main risk |
|---|---|---|
| Network engineer, no code | 1, 2 and 4 (Python, Git, HTTP, Docker) | Reading code without writing it |
| Developer, no networking | 6, then 3 and 5 | Guessing the 15% networking domain |
| CCNA holder | 2, 3 and 5 | Treating the exam as a top-up |
How to check which 200-901 profile fits before booking
Take the free 20-question practice test cold and compare the domain scores rather than the total. Read the sample questions and ask whether you could write the requests call and read the Dockerfile without help. If the weak domain is on the software side, use the doubled plan; if it is on the network side, shorten domains 1 and 2. The exam format page explains the name change from DevNet Associate and the six weights, and the 4-week study plan gives the week-by-week structure. The networking associate exam is covered in the 200-301 hub.