How to Pass the CCNA: 90-Day Study Plan

Most people who fail the CCNA do not fail because the material is too hard. They fail because they studied randomly: three weeks deep in subnetting videos, then a detour into OSPF, then panic-cramming ACLs the weekend before. A CCNA study plan fixes the order and the pace, and 90 days is enough time to do it properly while working a full-time job.

This plan schedules the whole 200-301 v1.1 blueprint week by week over 13 weeks, using the free guides, hands-on labs, and practice tests in our CCNA series. Every line links the exact resource for that day, and there is a printable planner PDF at the end so the schedule can live on your desk instead of in a browser tab.

Put this plan together in July 2026 around the series content that is live right now; every linked guide and lab below is free.

Is the CCNA hard?

The CCNA is an entry-level certification with a professional-sized syllabus. No single topic on it is difficult in isolation. The difficulty comes from breadth (six domains covering everything from cabling to automation) and from time pressure, because 100-plus questions in 120 minutes leaves no room to derive subnet math from first principles. Cisco does not publish pass rates, but the two failure patterns are consistent across every study forum: candidates who cannot subnet quickly, and candidates who read everything but never touched a router CLI.

Both problems are schedule problems. Subnetting speed comes from small daily practice over weeks, not a heroic weekend. CLI comfort comes from labbing every configure-and-verify topic as you learn it. The plan below bakes in both, and budgets roughly 100 to 150 total hours: 60 to 90 minutes on weekdays plus a longer lab session on weekends.

How the 90 days are structured

The plan runs in three 30-day phases: fundamentals and IP addressing first, then switching and routing (the two heaviest domains), then services, security, and a full review. Three rules hold the whole thing together.

1. Read, then lab, then quiz. Every configure-and-verify topic gets all three passes. Reading alone creates recognition, not recall, and the CCNA tests recall under time pressure.
2. Ten subnetting problems a day, every day, from week 3 onward. Non-negotiable. Subnetting shows up inside questions from every domain, and fluency is what buys you time for the hard questions.
3. A practice test closes each of the four biggest domains. Fundamentals, Network Access, IP Connectivity, and Security each end with a checkpoint. Score under 80% and you loop back before moving on, because moving forward on a weak foundation is how week 12 panic happens.

You need a lab environment from week 2. Both platforms are free: GNS3 (you supply your own Cisco images) or Cisco’s Packet Tracer. The CCNA labs hub covers both platforms and indexes every lab this plan assigns, with solution configs on GitHub.

Days 1-30: fundamentals, IP addressing, and the CLI

Month one builds the vocabulary and the two skills everything else depends on: subnetting and basic IOS navigation. Day 1 is deliberately light. Read what the certification actually tests, then book a test date about 13 weeks out. A booked date converts a vague intention into a deadline.

The week 3 subnetting block is where most plans quietly die, so treat those four days as protected time. The goal by day 21 is a /26 or /28 breakdown in under a minute, and the only route there is repetition.

Days 31-60: switching and routing, the heavy middle

Network Access and IP Connectivity together carry 45% of the question weight, and nearly every topic in this month is configure-and-verify. This is the month where the read-lab-quiz rule earns its keep. Every lab below has a matching solution config in the labs repo, but build from a blank canvas first and only diff against the solution when stuck.

Close the month with two days of IP connectivity troubleshooting drills and the Domain 3 practice test. Domain 3 is the largest on the blueprint, so scoring low here is normal on the first pass. Loop back over the routing labs rather than pushing into month three with a routing gap.

Days 61-90: services, security, and the review that gets you over the line

Month three covers the remaining three domains, then spends the final week consolidating instead of learning anything new. That final week matters more than any single topic in it.

Domain 6 is the one stretch where the series leans on your book instead of a hands-on lab, because automation and AI questions on the current blueprint are conceptual rather than configure-and-verify. Know what REST APIs, Ansible and Terraform are for, how controller-based networking differs from device-by-device management, and where AI fits in network operations. That depth is enough for its roughly 10% weight.

Get the printable 90-day planner

The whole schedule above fits on one printable page: 13 week cards with day ranges, the daily rules, and space to tick things off. Stick it next to your monitor and the plan survives contact with a busy week far better than a bookmark does.

What to do when you fall behind

You will fall behind at some point; a 13-week plan always collides with real life. The recovery move is to cut scope, not quality. Skip a concept-only topic and catch it in week 13, but never skip a lab, and never skip the daily subnetting. If you land more than a full week behind by day 60, push the test date back two weeks rather than compressing the review. Moving the date costs you two weeks; failing costs the full $300 (US) exam fee and a month of morale.

And if the schedule holds, resist the urge to move the date earlier. Day 85 to 89 consolidation is what turns 12 weeks of inputs into a pass, because retrieval under exam conditions is a different skill from recognizing material you have read. Ninety days of steady, ordered work beats six months of enthusiasm every time.