People love to say the CCNA takes three to six months. It can. But I did it in six weeks of focused evenings and weekends while holding down a full-time job, and I want to lay out exactly what I did each week — not a vague "study hard," but the actual weekly plan, hour by hour, including the mistakes.
A caveat before we start: I wasn't a total networking newbie. I'd done a bit of help-desk work and understood IP addresses. If you're starting from absolute zero, add two weeks. But the structure below holds regardless of pace.
The 200-301 is a single, broad exam — roughly 120 minutes, a mix of multiple choice, drag-and-drop, and simulation questions, and it covers six domains. Cisco doesn't publish an official passing score (it's scaled, but ~825/1000 is the commonly cited bar). Here's how I attacked it.
Week 1 — Network Fundamentals (the foundation everything stands on)
This domain is 20% of the exam and it underpins all the others, so I refused to rush it. The OSI and TCP/IP models, cabling, IPv4 and IPv6 addressing, and — the big one — subnetting.
I spent four evenings here. Three were just subnetting drills until I could carve a network into subnets in my head without a calculator. This is non-negotiable. If you can't subnet fast, the simulation questions will eat your clock alive. I did probably 200 subnetting problems this week alone.
By Friday I could look at a /27 and instantly tell you it gives 30 usable hosts. That fluency paid off every single week after.
Week 2 — Network Access (switching, VLANs, the layer-2 world)
Another ~20%. VLANs, trunking (802.1Q), EtherChannel, spanning tree protocol, and wireless fundamentals. This is where Cisco's command-line interface starts mattering. I fired up a network simulator and actually configured VLANs, set up trunk ports, and watched STP elect a root bridge.
The mistake I made: I tried to memorize commands instead of understanding the why. Halfway through the week I switched to "what problem does this solve" and everything got easier. Spanning tree stops loops. Trunks carry multiple VLANs. EtherChannel bundles links. Once the purpose clicked, the commands stuck.
Week 3 — IP Connectivity (routing — the heart of the exam)
25% — the biggest domain. Static routing, the routing table, OSPF, and default gateways. I gave this a full week and it deserved it. Understanding how a router picks a path (longest prefix match, administrative distance, metric) is the conceptual core of the whole cert.
OSPF was the boss fight. Single-area OSPF configuration, neighbor adjacencies, the DR/BDR election. I built a three-router topology in the simulator and didn't move on until I could configure OSPF from memory and explain why two routers weren't forming an adjacency (mismatched timers, usually).
Week 4 — IP Services + Security Fundamentals
These two domains together are about 25% (IP Services 10%, Security 15%). NAT, DHCP, NTP, SNMP, syslog, and QoS basics on the services side. Then access control lists, port security, DHCP snooping, and the AAA framework on the security side.
ACLs are where people lose points — standard vs extended, the implicit deny at the end, the order of evaluation. I drilled ACL scenarios until the implicit deny stopped surprising me. Security fundamentals also lean conceptual (threats, VPNs, wireless security like WPA2/WPA3), which made for a nice lighter mix after three heavy technical weeks.
Week 5 — Automation and Programmability + first full practice exams
The newest domain, ~10%. REST APIs, JSON, Ansible/Puppet/Chef at a conceptual level, controller-based networking (SDN), and Cisco DNA Center. It's not deep, but it's unfamiliar to old-school network folks, so don't skip it assuming it's filler.
This is also the week I started taking full, timed practice exams. My first one was a 71% — below passing, and honestly a gut-check. But the value wasn't the score, it was the map: it showed me my ACLs and OSPF troubleshooting were shakier than I thought. I ran a free CCNA practice test every other day and treated each one as a diagnostic, not a verdict.
Week 6 — Targeted review + simulation drilling
No new material. Pure reinforcement of weak spots. I went back to OSPF troubleshooting and ACLs — my two weakest areas from week 5's diagnostics — and hammered them. I also drilled the simulation-style questions specifically, because they're worth more points and take more time, so you want them to be automatic.
By midweek my practice scores were consistently in the mid-to-high 80s. I used ExamCert to keep pulling fresh question sets so I was testing actual understanding, not memorizing yesterday's answers. Two days before the exam I did one final full-length free 200-301 practice test, scored an 88%, and booked it for the next morning while the confidence was high.
What I'd tell my week-1 self
- Subnetting fluency is the single highest-leverage skill. Get fast early; it pays off all six weeks.
- Use a simulator constantly. Reading about VLANs teaches you nothing. Configuring them teaches you everything.
- Understand the why before the commands. Memorized commands evaporate under exam pressure; understood concepts don't.
- Start timed practice exams in week 5, not the night before. They're a map, not a final grade — use them to redirect your remaining study.
- Don't fear OSPF and ACLs — they fear preparation. They're where most people bleed points, which means mastering them is where you separate from the pack.
Six weeks is aggressive but absolutely doable if you're consistent and you front-load the fundamentals. The CCNA has a reputation for being brutal, and the breadth is real — but it's a fair exam that rewards understanding over memorization. Build a topology, break it, fix it, and drill questions relentlessly. Then go book your date before the self-doubt creeps back in.
Top comments (0)