CCNA Study Schedule for Beginners

Picture a complete beginner — no IT job, no home lab, no idea what a subnet is — who wants the Cisco Certified Network Associate (CCNA) certification. The most common failure mode is not lack of effort; it is studying topics in the wrong order, because the 200-301 exam blueprint is not a teaching sequence. This article gives that beginner a 12-week schedule, roughly 10–12 hours a week, that puts the topics in a learnable order and tells you what to do each week.

Two honesty notes before the timetable. First, Cisco publishes no official study-hours figure; the 12-week/10-hour shape below sits inside the ~3–6 months part-time range commonly reported by the candidate community, and you should stretch it without guilt if life demands it. Second, the CCNA has no prerequisites — you can legitimately start from zero — but Cisco suggests a year or more of networking exposure, which is exactly the experience this schedule has to substitute for with deliberate lab time.

How this schedule is built

Three design rules drive the plan:

1. Concepts before configuration. Each block starts with theory, then immediately cements it in Cisco Packet Tracer — the free simulator from Cisco's Networking Academy — because beginners who delay labs until "after the reading" usually never catch up.
2. Spaced re-visits. Subnetting and routing reappear in later weeks on purpose. One pass is never enough for the topics the whole exam leans on.
3. A fixed weekly rhythm. Four sessions a week: two theory evenings (about 2 hours each), one lab evening (about 2–3 hours), and one longer weekend block (3–4 hours) mixing labs with review questions. Consistency beats marathon weekends.

The sequence follows the exam's six domains but reorders them for learning. If you want to know what each domain contains and how much of the exam it represents, the CCNA exam topics breakdown covers that; this article assumes the what and handles the when.

The 12-week CCNA schedule

Weeks 1–2: Network fundamentals, part one

Start with how networks actually move data: the OSI and TCP/IP models, Ethernet, switches versus routers, cabling and interface types, and TCP versus UDP. In your first lab sessions, do nothing more ambitious than building a two-PC-and-a-switch topology in Packet Tracer, assigning addresses and pinging between them. That tiny exercise teaches the simulator itself, which is a skill of its own.

• Theory: models, devices, cables, TCP/UDP
• Lab: install Packet Tracer, build and ping a minimal LAN
• Weekend: redraw the TCP/IP model from memory; explain each layer aloud

Weeks 3–4: IPv4 addressing and subnetting

Subnetting is the make-or-break fortnight. Spend both weeks on binary, IPv4 addressing, subnet masks and VLSM until you can produce network, broadcast and host-range answers on paper in under a minute each. Add IPv6 basics in week 4 — address types and simple interface configuration.

• Theory: binary maths, subnetting method, IPv6 address types
• Lab: re-address your week-2 topology into multiple subnets with a router between them
• Weekend: 50 subnetting drills; do not move on until your error rate is near zero

Beginners tempted to shortcut this block should not: almost every later week silently depends on it.

Weeks 5–6: Switching and VLANs

Now the network access domain: VLANs, trunking (802.1Q), inter-VLAN routing, and spanning tree — including the protection features the current v1.1 topics emphasise, such as Root Guard, Loop Guard, BPDU Guard and BPDU Filter. This is also the fortnight you learn Cisco IOS properly: configuration modes, saving configs, and the core show commands.

• Theory: VLANs, trunks, STP behaviour and guards
• Lab: two switches, two VLANs, a trunk, then router-on-a-stick inter-VLAN routing
• Weekend: break your own lab (shut a trunk, mismatch a VLAN) and repair it from show output

Weeks 7–8: Routing

The IP connectivity domain: how routers choose routes (longest prefix match, administrative distance, metric), static and floating static routes, then single-area OSPFv2 configuration and verification. By the end of week 8 you should be able to configure OSPF between three routers and explain every line of show ip route.

• Theory: route selection logic, static routing, OSPF neighbours and states
• Lab: three-router OSPF topology; deliberately break an adjacency and diagnose it
• Weekend: rebuild the whole weeks 5–8 network from a blank file, timed

Week 9: IP services and wireless

A consolidation week for the services domain: NAT/PAT, DHCP, DNS, NTP, SNMP and syslog, plus the wireless architecture and WLC concepts from the network access domain that did not fit the switching fortnight.

• Theory: each service's purpose and configuration depth per the blueprint
• Lab: add PAT to your topology's edge router; run DHCP for one VLAN
• Weekend: first light review sweep of weeks 1–8 notes

Week 10: Security fundamentals

Device hardening (SSH-only management, local accounts, ACLs), port security, AAA concepts, VPN types and the security-programme vocabulary the exam expects. Much of this is configuration you already half-know, applied with a security lens.

• Theory: security concepts and terminology
• Lab: harden every device in your practice topology; write and test two ACLs
• Weekend: flashcard sweep of security terms — this domain rewards precise vocabulary

Week 11: Automation, programmability and the newer topics

The final new-material week: REST APIs, JSON, controller-based and cloud-managed networking, configuration management concepts, and the topics version 1.1 added in August 2024 — generative AI and machine-learning awareness among them. Older free courses often predate these additions, so verify whatever resource you use covers v1.1, not the original 2020 topic list.

• Theory: automation concepts; read some JSON until it stops looking alien
• Lab: lighter this week — explore a controller demo or API walkthrough if your course includes one
• Weekend: full-length timed practice test, your first

Week 12: Review, simulate, decide

No new material. Re-drill your weakest domains from the week-11 test, take a second full-length timed practice test mid-week, and spend the weekend on final consolidation. How to score, interpret and squeeze study value from those tests is a discipline of its own, covered in the CCNA practice test strategy guide. The free 200-301 sample questions work for quick domain spot-checks, and subscribers can run fuller timed simulations for the two full-length sittings this week calls for.

At the end of week 12, run a formal readiness audit — the CCNA exam preparation checklist exists precisely for that decision — and if it passes, book with Pearson VUE. As of 2026 the exam costs US $300 (varies by country) and runs 120 minutes at a test centre or via OnVUE online proctoring.

Adjusting the pace: 16-week and 8-week variants

If 10–12 hours a week is unrealistic — full-time job, family, shift work — stretch to 16 weeks at 7–8 hours: give subnetting three weeks instead of two, split the routing block into static routing and OSPF fortnights, and keep the final two review weeks intact. A longer schedule that you actually follow beats a 12-week plan you abandon in week 5.

If you can commit 20+ hours a week — between jobs, on a break from study — an 8-week compression works by merging weeks 1–2 and 9–10 into single weeks. Do not compress the subnetting block or the final review week; those two are where compression quietly destroys pass chances.

For a broader look at how experience level changes total preparation time — including for readers who are not starting from zero — see how long it takes to prepare for the CCNA.