CCNA study hours: turn your real week into an exam date that holds

"Pass CCNA in 30 days" plans are written by people who already work with networks. They collapse in week two for everyone else, and the candidate blames himself rather than the plan. This guide starts from your calendar instead.

How many hours does CCNA really take?

Cisco does not publish a study-hour figure. CredenTrek uses 120 to 200 hours, including labs, as a working assumption. Move towards 120 if you already work with networks. Move towards 200 or beyond if subnetting and the command line are new to you.

Your first practice test tells you where you stand. If you cannot subnet an address without a calculator, add hours before you do anything else.

How should you split the hours across domains?

Split your total in proportion to the weights of your version, then move hours towards the topics you rated lowest. For a 150-hour v2.0 plan the starting point looks like this.

For v1.1, use the v1.1 weights: 20, 20, 25, 10, 15 and 10 per cent.

Which weekly track is yours?

Pick the track that matches your real weekly time, not your best week. If you are not sure, use the lower number: a plan you can keep beats a plan you admire.

How do hours become a date?

Divide your total hours by your weekly hours, then add roughly one buffer week for every eight weeks of plan. At 150 hours:

Karim, a help desk technician in the book, had 10 hours a week and planned 150 hours for v2.0. That gave him 15 weeks plus two buffer weeks. He booked for week 18, after his third practice exam came in well above his earlier ones.

Now check the answer against the calendar. A v1.1 plan has to finish, with a spare week or two for a retake, before 2 February 2027. The version rule shows how to do that in five minutes.

What goes in each of the four stages?

CCNA rewards practice at the command line, so labs and question sets deserve a large share of your hours.

• Stage A, foundation (about 10 per cent). Rate yourself on every topic, take a diagnostic practice test and install your lab. For 150 hours that is about 15 hours.
• Stage B, first coverage (about 45 per cent). Work through your course once, with a lab for every topic. About 68 hours.
• Stage C, practice (about 30 per cent). Troubleshooting labs, subnetting drills, question sets by domain and a review of every wrong answer. About 45 hours.
• Stage D, simulation (about 15 per cent). Full timed practice exams and light revision. About 22 hours.

Practice and simulation take almost half the plan. If your schedule slips, cut from Stage B's reading, not from Stage C's labs.

What should your lab look like?

Cisco recommends Packet Tracer or Cisco Modeling Labs for hands-on practice. Build one small network early: two switches, two routers, VLANs, a trunk, OSPF and a few hosts. Then break it on purpose and fix it, because v2.0 rewards troubleshooting.

A simple weekly rhythm: one lab per topic you cover, one fault introduced and fixed per week, and five minutes of subnetting drills most days. At least a third of every week should be in the lab, more if you are on the light track.

How will you know you are ready?

Readiness is a pattern, not a single score. Look for consistent results across two or three full practice exams, no domain far behind the others and confidence in a timed simulation. You should be able to subnet any address in under a minute.

Book when that pattern holds, not after one good result. The cost and booking guide covers the next step. Appendix B of CredenTrek For Cisco CCNA has the weekly plan template to fill in, with your version, track, total hours and stage dates.