How to Build a CCNA Study Plan

A complete 12-week CCNA study plan mapped to the 200-301 exam topics, with weekly goals, lab milestones, checkpoints and rules for adapting it to your life.

Liam Anderson6 July 2026 · 9 min read

Ask AIChatGPT Claude Gemini Copilot Perplexity Grok

Twelve-week CCNA study calendar with topic icons per week and highlighted checkpoints at weeks four, eight and eleven

A good Cisco Certified Network Associate (CCNA) study plan does three things: it walks the full 200-301 exam topics list in a deliberate order, it attaches every topic to a week with a lab and a question set, and it builds in checkpoints that tell you — before exam day — whether the plan is working. Below is a complete 12-week template that does all three, followed by the rules for compressing it, stretching it or rebuilding it around your own constraints.

One boundary note so you use this page for the right job. This article is the schedule. The study methods it schedules — how to lab effectively, choosing theory resources, using questions without memorising them — are covered in how to study for the CCNA exam, and the question of how many total weeks someone with your background should budget is answered in how long it takes to prepare for CCNA. Twelve weeks at roughly ten hours a week suits a candidate with some IT exposure; adjust with the rules in the adaptation section rather than by guessing.

Before week one: three setup tasks

Download the official exam topics list. Get the current 200-301 exam topics (v1.1, in effect since 20 August 2024) from Cisco's certification site and keep it as your master checklist. Every plan item below should be traceable to a line on that list, and the list is the tiebreaker whenever a resource covers something the plan does not mention. Note the verbs Cisco uses per line — "configure and verify" lines need lab time, "explain" and "describe" lines need understanding only.
Pick your resources now, not weekly. One primary course or book confirmed as updated for the v1.1 revision (which added generative AI, cloud network management and machine-learning awareness, deeper spanning-tree protection features, and expanded automation and device-hardening content), Cisco Packet Tracer installed and tested, one flashcard app, and one practice-question source. Resource-shopping mid-plan is the most common way schedules silently die.
Block the hours in your calendar. This template assumes about ten hours a week: five or six weekday hours in short sessions, the balance in one longer weekend block for labs and reviews. Recurring calendar entries, agreed with the people you live with, outperform intentions.

The 12-week plan at a glance

Week	Focus	Lab milestone	Checkpoint
1	Networking models, components, cabling, TCP/UDP	Build a first two-switch, two-PC topology	—
2	IPv4 addressing and subnetting	Address a multi-subnet topology by hand	Daily subnetting drill begins
3	IPv6 addressing; endpoint and virtualisation basics	Dual-stack the week-2 topology	—
4	Switching: VLANs, trunking, inter-VLAN routing	Multi-switch VLAN build from a blank page	Checkpoint 1: first-quarter question set
5	Spanning tree + protection features, EtherChannel	Break-and-fix STP lab	—
6	Routing fundamentals, static routes, OSPF part 1	Static-routed three-router topology	—
7	OSPF part 2; first-hop redundancy concepts	Multi-area OSPF build and verify	—
8	IP services: NAT, DHCP, NTP, DNS, SNMP, syslog	NAT + DHCP on the running topology	Checkpoint 2: mid-plan timed half-exam
9	Security fundamentals: ACLs, device hardening, port security, VPN and wireless security concepts	ACL and hardening pass on every device	—
10	Wireless fundamentals; automation, programmability, AI and cloud management awareness	Wireless LAN build; read APIs/JSON topics to the topic-list verb	—
11	Full review sweep; weak-area repair	Rebuild the full end-to-end topology unaided	Checkpoint 3: full-length timed practice exam
12	Weak domains only; light review; rest	Short daily labs on weak areas only	Exam day

The order is deliberate: addressing before switching, switching before routing, everything before services and security (which are configured onto a working network), and the awareness-level automation, AI and wireless-theory material late, where its lighter cognitive load fits tired weeks. The running topology you start in week 1 grows every week, so by week 11 rebuilding it is a review of the entire syllabus.

The plan in detail, phase by phase

Phase 1 — Foundations (weeks 1–3)

The first three weeks feel slow and are the most important in the plan. Week 1 establishes the vocabulary of models, media and transport protocols; do not rush it, because every later explanation is written in these terms. Week 2 is subnetting, and it gets a special rule: from this week until exam day, a short daily drill — a handful of problems, a few minutes — stays in the plan no matter what else slips. Addressing fluency compounds across the entire exam. Week 3 extends the addressing to IPv6 and covers endpoint and virtualisation concepts from the topic list.

Weekly rhythm throughout the plan: new theory early in the week with closed-book notes, the same topics labbed by midweek, a topic-mode question set on the previous week's material at the weekend, and flashcards daily. If a week ends with theory unlabbed, the next week starts with the lab, not new theory.

Phase 2 — Switching (weeks 4–5)

Week 4 is VLANs, trunking and inter-VLAN routing — the first material where blank-page lab rebuilds (configuring from a topology diagram with no instructions) become essential. Week 5 covers spanning tree, including the protection features the v1.1 topics deepened — Root Guard, Loop Guard, BPDU Guard and BPDU Filter — plus EtherChannel, and introduces break-and-fix labs: misconfigure deliberately, then troubleshoot from symptoms.

Checkpoint 1 (end of week 4): answer a mixed question set covering weeks 1–4. Below roughly two-thirds comfortable, insert a consolidation week before phase 3 — better to run a 13-week plan than to build routing on unstable switching.

Phase 3 — Routing (weeks 6–7)

Two full weeks on how routers choose paths: routing table logic, static and default routes, then OSPF across two weeks because it rewards depth — neighbour relationships, areas, cost, verification commands. First-hop redundancy concepts close week 7. This is the phase where earlier subnetting drills pay off visibly; addressing mistakes are the classic source of broken routing labs.

Phase 4 — Services and security (weeks 8–9)

Week 8 configures the everyday services onto your running topology: NAT, DHCP, NTP, DNS concepts, SNMP and syslog. These topics are frequently neglected as "boring" and are a cheap source of exam marks. Week 9 is security fundamentals: access control lists, device hardening (SSH, passwords, port security) applied to every device you have built so far, plus the concept-level security, VPN and wireless-security material.

Checkpoint 2 (end of week 8): sit a timed half-length practice session under exam conditions. You are testing stamina and timing as much as knowledge. Score it by topic area and write down your two weakest — they get priority in week 11.

Phase 5 — Breadth topics (week 10)

Wireless fundamentals plus the automation, programmability and v1.1 AI and cloud-management awareness content. Most of this is "explain/describe" material: study it with notes and flashcards to the exact verb on the topic list, and resist over-investing lab time here at the expense of the configuration domains.

Phase 6 — Review and land the plane (weeks 11–12)

Week 11 has two jobs: rebuild your full topology from scratch without notes (an end-to-end syllabus review disguised as one lab), then sit Checkpoint 3 — a full-length, fully timed practice exam. ExamPractice's CCNA 200-301 practice tests include a timed simulation mode suited to exactly this dress rehearsal; free samples let you preview the format earlier in the plan. Analyse the result by domain, not by total score — a strong average hiding one collapsed topic area is not a pass signal, and Cisco publishes neither the question count nor the passing score, so domain coverage is the only readiness measure available to you.

Week 12 deliberately contains no new material: short daily sessions on the checkpoint-identified weak areas, flashcard maintenance, one light final lab, and genuine rest the day before. Confirm your booking logistics — Pearson VUE test centre or OnVUE online proctoring — well before the day.

Adapting the template to your situation

A plan you copied is a draft; these rules make it yours.

Compressing to 8 weeks (for candidates already working with networks): merge weeks 1–3 into one, halve phase 2, keep both routing weeks, merge weeks 8–9, and never cut the three checkpoints or week 12's review. Compress content, not verification.
Stretching to 16–20 weeks (for complete beginners or five-hour weeks): give phases 1–3 the extra time — foundations, switching and routing are where beginners stall — and add a fourth checkpoint after phase 1. Keep the daily subnetting drill from week 2 regardless of length; a longer calendar makes decay the bigger enemy.
When life interrupts: shift the whole plan rather than skipping a week's content. A skipped topic does not disappear; it resurfaces as a weak domain in week 11 with less time to fix it.
When a checkpoint fails: insert repair time immediately after the checkpoint instead of hoping the final review absorbs it. The checkpoints exist precisely so that bad news arrives while it is still cheap; on a US $300 exam with a five-calendar-day wait and a full fee on retakes, week-11 evidence is far cheaper than an exam-day surprise.
Booking the exam: a practical trigger is a solid Checkpoint 2 — book at that point for roughly four weeks out, and let Checkpoint 3 confirm the date. Candidates who wait to "feel ready" before booking tend to drift into month five of a 12-week plan.

Readiness checklist for the final week

Enter week 12 able to tick every line below; any unticked line names your remaining study.

I can subnet quickly and accurately, IPv4 and IPv6, without a reference.
I can rebuild the full course topology — VLANs, trunks, STP with protection features, EtherChannel, OSPF, NAT, DHCP, ACLs, hardening — from a diagram alone.
I can troubleshoot a broken lab from symptoms, not just build from clean.
I have sat at least one full-length timed practice exam and reviewed every incorrect answer's explanation.
No topic area on my last practice exam was dramatically weaker than the rest.
I can explain the awareness-level topics — automation, programmability, AI, cloud management, wireless concepts — in my own words.
My exam is booked, and I know the test-centre or OnVUE requirements for the day.

Frequently asked questions

Should the plan change if I can study full-time?

Compress calendar weeks, not the structure: full-time study can run each "week" in two to three days, completing the plan in about a month, but keep the checkpoint order and the untouched final review phase. What full-time schedules must add is variety within the day — theory, lab and questions rotated — because eight straight hours of one activity retains poorly.

What if my course's chapter order differs from this plan?

Follow your course's order for theory if reordering it is awkward, but keep this plan's milestones: subnetting drills from early on, blank-page labs per configuration topic, and the three checkpoints at quarter, half and final positions. The checklist you track against is always Cisco's official topics list, not either ordering.

Do rest days belong in a study plan?

Yes, structurally. One full day off per week and a light final week are load-bearing parts of this template, not slack. Plans without recovery produce the mid-plan collapse where a candidate disappears for three weeks and restarts from week 1.

Where does the CCNP fit into this plan?

Nowhere yet — finish the CCNA first. When you are certified and wondering about next steps, the decision has its own articles: what comes after CCNA compares the options, and the CCNA-to-CCNP timing question is covered separately.

Make the plan boring and the result interesting

The template above is not clever, and that is the point: a fixed topic order that builds one growing lab, a weekly rhythm that never lets theory escape its lab and its question set, three checkpoints that force the truth out early, and a final week that repairs instead of crams. Print the 12-week table, adjust it with the adaptation rules once, put the hours in your calendar, and then stop redesigning it — from week 1 onwards, the only job is showing up for the next session. Twelve weeks of that is what a CCNA pass usually looks like from the inside.

Exam facts in this guide were checked against official certification-provider pages on 30 August 2026. Fees, exam codes and policies change — confirm on the provider’s own site before you book.