Most people who fail to earn the CCNA do not fail because the material is too hard. They fail because they study without a plan: weeks of enthusiastic reading, a stall around spanning tree, a vague sense of “almost ready,” and an exam date that keeps slipping. This 90-day CCNA study plan fixes that. It breaks the 200-301 blueprint into thirteen focused weeks, pairs every topic with hands-on labs, and builds in review so you walk into the exam room confident rather than hopeful.
Before you start: is 90 days realistic?
Ninety days is an ambitious but achievable target for many candidates. Whether it is realistic for you depends on three things: your starting point, the time you can commit each week, and how consistently you can stick to the schedule.
- If you already work in IT, perhaps as a help desk technician or network administrator, you likely know some fundamentals already, and 90 days is very realistic.
- If you are new to networking, the plan still works, but expect some weeks to take longer. Extending to four or five months is perfectly fine.
- If your schedule is unpredictable, treat the weeks as phases rather than fixed dates and focus on completing each phase properly.
Plan for roughly eight to twelve hours of study per week: about an hour or two on most weekdays and a longer lab session at the weekend. That is a sustainable pace alongside a full-time job, and consistency beats intensity every time.
Understanding the CCNA 200-301 exam domains
The CCNA 200-301 blueprint is organized into six domains. Cisco publishes the full list of exam topics, including the relative weighting of each domain, on its official certification site. Blueprints are revised from time to time, so download the current version before you start and use it as your master checklist.
| Domain | What it covers |
|---|---|
| Network Fundamentals | Network components and topologies, cabling and interfaces, TCP and UDP, IPv4 and IPv6 addressing and subnetting, wireless principles, virtualization and switching concepts |
| Network Access | VLANs, trunking, Layer 2 discovery protocols, EtherChannel, Rapid PVST+ spanning tree, wireless architectures and access point modes, WLAN management access |
| IP Connectivity | The routing table, forwarding decisions, IPv4 and IPv6 static routing, single-area OSPFv2 and the purpose of first hop redundancy protocols |
| IP Services | NAT, NTP, DHCP and DNS, SNMP, syslog, QoS concepts, SSH remote access, TFTP and FTP |
| Security Fundamentals | Security concepts and programs, device access control, passwords and MFA, VPNs, ACLs, Layer 2 security features, AAA and wireless security |
| Automation and Programmability | The impact of automation, controller-based and software-defined networking, REST APIs, configuration management tools and JSON |
Two domains deserve special attention. Network Fundamentals is broad and underpins everything else; weak subnetting will cost you points across the whole exam. IP Connectivity is where routing logic lives, and it rewards genuine understanding over memorization.
Choosing your study resources
You do not need ten resources. You need a small, complementary set and the discipline to finish them. A strong toolkit looks like this:
- One primary text. An official certification guide or an equivalent comprehensive book that maps to the current blueprint. This is your reference for depth.
- One video course. Video is excellent for first exposure to a topic and for seeing configuration in action. Pick one reputable course and stick with it.
- A lab environment. Cisco Packet Tracer is free and handles most CCNA labs. Cisco Modeling Labs, GNS3 or EVE-NG add real images. Our guide to building a home network lab compares the options.
- Flashcards. A spaced repetition app is ideal for port numbers, command syntax, administrative distances and other facts that must be instantly recalled.
- Practice exams. Use a reputable practice exam product in the final weeks to measure readiness and find weak areas. Avoid “brain dumps,” which violate Cisco’s exam agreement and teach you nothing useful.
The daily and weekly routine
A repeatable routine removes the daily decision of “what should I study?” and keeps momentum through the tougher weeks. Here is a structure that works well:
Weekday sessions (about 60–90 minutes)
- Warm-up (10 minutes). Review flashcards and solve two or three subnetting problems.
- Learn (30–40 minutes). Read a chapter section or watch the related videos for the week’s topic.
- Lab (20–30 minutes). Immediately configure what you just learned, then verify it with show commands.
- Capture (5 minutes). Write down new commands and anything confusing, and turn key facts into flashcards.
Weekend session (about 3–4 hours)
- Build a larger lab that combines the week’s topics with earlier ones.
- Break it deliberately and troubleshoot it without looking at your notes.
- Review the week’s notes and answer practice questions on the topics.
- Re-read any section you could not explain clearly in your own words.
The 90-day plan, week by week
The table below is the heart of the plan. Each week has a domain focus, the specific topics to study, a lab focus and a milestone that tells you whether you are ready to move on. Week 13 covers the final days before the exam.
| Week | Domain focus | Topics | Lab focus | Milestone |
|---|---|---|---|---|
| 1 | Network Fundamentals | OSI and TCP/IP models, network components, topology architectures, cabling, interface errors, TCP vs. UDP | Basic device setup: hostname, passwords, banners, interface descriptions, saving configs | Navigate the IOS CLI modes comfortably |
| 2 | Network Fundamentals | Binary, IPv4 addressing, subnet masks, CIDR, private addressing, VLSM | Address a small multi-subnet network and verify connectivity | Subnet any /24 to /30 accurately in your head |
| 3 | Network Fundamentals | IPv6 addressing, address types, EUI-64, verifying IP settings on client operating systems, virtualization basics | Dual-stack a small network with static IPv6 addresses | Identify IPv6 address types at a glance |
| 4 | Network Access | Switching concepts, MAC learning, VLANs, access ports, voice VLANs, 802.1Q trunks, native VLAN, CDP and LLDP | Multi-switch VLAN network with trunks | Troubleshoot a broken trunk using show commands |
| 5 | Network Access | Rapid PVST+, root bridge election, port roles and states, PortFast, BPDU Guard, EtherChannel with LACP | Manipulate the root bridge; build and verify an EtherChannel | Predict which ports will block in a triangle topology |
| 6 | Network Access and Fundamentals | Wireless principles, RF basics, wireless architectures, AP modes, WLC connectivity, management access methods | Wireless controller and WLAN configuration in a simulator | Explain how an AP, WLC and switch ports work together |
| 7 | IP Connectivity | Routing table components, longest prefix match, administrative distance, metrics, IPv4 and IPv6 static, default and floating static routes | Three-router static routing lab with a floating backup route | Read a routing table and predict the forwarding decision |
| 8 | IP Connectivity | Single-area OSPFv2, router ID, neighbor adjacencies, DR and BDR, point-to-point networks, first hop redundancy concepts | OSPF network with broadcast and point-to-point links | Fix OSPF adjacency problems from show output alone |
| 9 | IP Services | Static NAT, NAT pools and PAT, DHCP server and relay, DNS, NTP, SNMP, syslog, QoS concepts, SSH, TFTP and FTP | Branch router with PAT, DHCP, NTP, syslog and SSH | Internet access from all VLANs through PAT |
| 10 | Security Fundamentals | Threats and mitigations, device hardening, passwords and MFA, AAA, VPN concepts, standard and extended ACLs, port security, DHCP snooping, DAI, wireless security | ACLs between VLANs; port security and DHCP snooping on access ports | Write and place an extended ACL correctly the first time |
| 11 | Automation and Programmability | Traditional vs. controller-based networking, SDN architecture, REST APIs, JSON, configuration management tools, other topics listed in the current blueprint | Read and edit JSON; make an API call to a sandbox or lab device | Explain control, data and management planes clearly |
| 12 | All domains | Full-length practice exams, targeted remediation of weak areas, flashcard review | Build a complete network from a blank config with no notes | Consistently strong practice scores across every domain |
| 13 | Final review | Light review, subnetting drills, command syntax, rest before exam day | Short troubleshooting drills only | Sit the exam |
How the phases fit together
The thirteen weeks fall naturally into four phases. Understanding the purpose of each phase helps you decide when to push on and when to slow down.
Phase 1: Foundations (weeks 1–3)
This phase is about addressing and models. It is tempting to rush it because the topics feel basic, but every later topic depends on it. The key output is subnetting fluency. If you cannot yet find the network, broadcast and host range for any address quickly, keep drilling with our step-by-step subnetting guide before you move on. Five minutes of subnetting practice every day for the rest of the plan will keep the skill sharp.
Phase 2: Switching and routing (weeks 4–8)
This is the core of the CCNA and where most of your lab time should go. VLANs and trunks lead into spanning tree and EtherChannel, then wireless, static routing and OSPF. The most common stall point is spanning tree, because it requires you to reason about a topology rather than recall facts. Draw every topology, mark the root bridge, root ports, designated ports and blocked ports by hand, then confirm your predictions in the lab. For extra depth on Layer 2 design, read our article on VLANs, trunking and inter-VLAN routing, and for routing, our OSPF fundamentals guide goes beyond the exam minimum.
Phase 3: Services, security and automation (weeks 9–11)
These domains contain many smaller topics, so the risk shifts from conceptual difficulty to breadth. Build a single “branch office” lab and keep adding to it: NAT, DHCP, NTP, syslog, SSH, ACLs and Layer 2 security. Seeing how services interact, for example how an ACL can accidentally block DHCP relay, is excellent exam preparation. For automation, focus on concepts and reading structured data. You will not be asked to write complex programs, but you should be comfortable with JSON, HTTP methods and how controllers differ from device-by-device management. Our network automation guide is a good primer if you want to go further.
Phase 4: Review and exam (weeks 12–13)
This phase converts knowledge into exam performance. Take a full-length practice exam under timed conditions at the start of week 12. Analyze every wrong answer and every lucky guess, then spend the rest of the week fixing those specific weaknesses in the lab and the book. Take a second practice exam at the end of the week to measure progress. Week 13 is for light review and rest, not cramming new material.
Labs that matter most
If you only have time for a limited number of labs, prioritize the ones that combine multiple topics and force you to troubleshoot. These cover a large share of the hands-on skills the exam expects:
- Multi-VLAN campus: two access switches and a distribution switch with VLANs, 802.1Q trunks, a deliberately chosen root bridge, an LACP EtherChannel, and SVIs for inter-VLAN routing.
- Router-on-a-stick branch: a router with subinterfaces for three VLANs, DHCP for each VLAN and PAT to an “internet” router.
- OSPF triangle: three routers running single-area OSPFv2 with loopbacks, manually set router IDs and one broadcast segment where you control the DR election.
- Static and floating routes: a primary path and a backup static route with a higher administrative distance that takes over when you shut the primary link.
- Secure access layer: port security, DHCP snooping, dynamic ARP inspection, SSH-only management with local or AAA authentication, and an extended ACL protecting a server VLAN.
- Dual-stack network: IPv6 addressing on all interfaces with static IPv6 routes, verified with ping and traceroute.
For every lab, follow the same rhythm: build it, verify it, document it, break it, fix it. The “break it” step is where most of the learning happens.
Final weeks and exam day
How you handle the last two weeks often decides the result. Prioritize sleep, steady review and confidence-building practice over panic-driven cramming.
Signs you are ready
- You score consistently well on reputable practice exams across all six domains, not just overall.
- You can subnet quickly and accurately without a calculator.
- You can build the multi-VLAN and OSPF labs from a blank configuration and troubleshoot them using show commands.
- You can explain why, not just what, for topics like spanning tree port roles, OSPF DR election and administrative distance.
On exam day
- Know the logistics. Cisco exams are delivered by Pearson VUE, either at a test center or online with remote proctoring. Read the identification and check-in requirements in your confirmation well in advance.
- Manage your time. Note the total time and number of questions at the start and check your pace periodically. Do not let one difficult simulation consume a disproportionate share of the clock.
- Answer every question. Cisco exams generally do not let you return to earlier questions, so make your best decision and move on.
- Read carefully. Watch for words like “not,” “best” and “most likely,” and check whether a question asks for one answer or several.
- Use your scratch space. Write out subnet calculations rather than doing them in your head under pressure.
Common pitfalls and how to avoid them
- Too many resources. Jumping between books and courses creates the illusion of progress. Choose one primary text and one course and finish them.
- Reading without labbing. If you have not configured it, you do not really know it. Every topic in the plan has a lab for a reason.
- Skipping review. Without spaced repetition, the material from week 2 will be fuzzy by week 10. Keep up with your flashcards daily.
- Ignoring weak domains. It is more enjoyable to practice what you already know. Practice exam results tell you where to spend time; listen to them.
- Studying alone with no feedback. A study partner, community or mentor catches misunderstandings you would never notice yourself.
- Letting a bad week end the plan. Missing a few days is normal. Pick up where you left off and adjust the schedule rather than starting over.
Key takeaways
- Ninety days is realistic for many candidates at around eight to twelve hours of study per week; extend phases where needed rather than rushing.
- Use the official CCNA 200-301 exam topics as your master checklist and confirm the current version and weighting before you begin.
- Keep resources focused: one primary text, one video course, a lab platform, flashcards and a reputable practice exam product.
- Follow a consistent routine of learn, lab, review, with a longer combined lab every weekend.
- Invest heavily in the foundations, especially subnetting, and in hands-on switching and routing labs.
- Use timed practice exams in the final phase to find and fix weaknesses, then rest before exam day.
A plan is only as good as your ability to stick to it, and having someone check your progress makes a big difference. If you want structured accountability, lab reviews and answers to your questions as you go, our 1:1 CCNA Mentorship Program pairs this approach with eight weeks of personal guidance. Have a question about your own timeline? Get in touch.
