CCNA Study Plan

Choose the exam version first

Cisco has announced that CCNA 200-301 v1.1 has a last test date of February 2, 2027, and v2.0 begins February 3. Before following any schedule, decide which version you are preparing for and use its official topic list. A study guide tied to an earlier blueprint may still teach foundational skills, but it can emphasize retired tasks or miss new ones. Record the version and date in your notes.

This plan is a framework rather than a promise about how many weeks every candidate needs. Someone who configures switches and routes at work may need review and exam practice; a beginner may need to learn networking basics first. Use a diagnostic to estimate the gap and scale the plan to your weekly availability.

Start with a diagnostic

Take a short mixed set covering Network Fundamentals, Network Access, IP Connectivity, IP Services, Security Fundamentals, and Automation and Programmability. The goal is not to predict a Cisco passing score, which is not published as a fixed number. Instead, record what you could explain, what you guessed, and what you could not reason through.

Sort errors into useful categories: subnet calculation; device or interface role; VLAN/trunk behavior; route selection; service function; ACL evaluation; wireless security; or controller/API concepts. Also note whether a miss came from knowledge, calculation, configuration, or careless reading. A log that says 'IP Connectivity weak' is less helpful than 'selected default route despite more-specific prefix' because the latter tells you what to practice.

An eight-week schedule for a part-time learner

If you have only three hours per week, extend this plan to sixteen weeks or more rather than trying to squeeze each lab into a rushed session. If you can devote ten hours weekly and already know the fundamentals, you can compress it, but retain cumulative review. Calendar length should follow the time required to demonstrate understanding, not a marketed study guarantee.

A weekly rhythm that builds retention

1. Begin a session by writing what you remember about the current topic without notes.
2. Read or watch one lesson tied to an official task, then verify unclear behavior in Cisco or protocol documentation.
3. Configure a small topology or work a written scenario. Predict the output before running commands.
4. Review each practice answer, including correct guesses, and write one reusable rule for mistakes.
5. Revisit older topics after several days and mix them into later practice.

Spaced recall helps because networking topics connect. A learner may master a static route in week four but forget the subnet boundary that determines whether its next hop is reachable. Briefly revisit addressing and VLAN paths while studying routing. This prevents knowledge from remaining isolated in a single chapter.

Build labs around questions

A lab should answer a question. For example: which traffic crosses a trunk when VLAN 20 is removed from the allowed list? What happens when a host's mask changes from /24 to /25? Why does a more-specific route beat a default route? How does the first matching ACL entry affect a packet? Create the smallest topology needed, predict the behavior, run the test, and explain any difference.

Network simulators can be effective for foundational CCNA practice. Physical equipment can provide realism but brings cost, space, power use, and compatibility considerations. A simulator's limitations should be checked for the task you are practicing. Neither a lab nor a simulator proves that the official exam will use the same interface or item type; the public exam page does not promise a particular live simulation format.

Study the high-weight domains without skipping others

IP Connectivity is 25% of the current v1.1 blueprint. Network Fundamentals and Network Access are each 20%, Security Fundamentals 15%, IP Services 10%, and Automation and Programmability 10%. A rough schedule can allocate time proportionally, then adjust after diagnostics. If you are strong in routing, shift time to wireless or automation. If subnetting is shaky, invest in Fundamentals even if a question bank labels it a separate topic.

The weights do not guarantee an exact number of items, and Cisco does not publish a fixed question count. Therefore, do not try to forecast how many errors a domain allows. The practical target is to handle representative tasks from each area and connect them in mixed scenarios.

Use practice tests in two phases

Early practice should be untimed enough to teach. Read explanations carefully and verify configuration behavior. Later practice should be timed for 120 minutes to build pacing and attention. Cisco's public materials do not publish an exact question count, so a third-party test with 100 questions cannot reproduce the official item count just by matching the duration.

A practice percentage is not an official pass prediction. Cisco does not publish a fixed cutoff, and test providers may score their own question sets differently. Track fresh-set performance, time management, and recurring misses. When answers become familiar, change the scenario or tool instead of celebrating a memorized score.

Readiness checkpoints

At the midpoint, try to explain and configure a simple two-VLAN topology with a trunk and routed gateway. Calculate a subnet, interpret a route table, and identify whether a host issue is addressing, switching, routing, or DNS. Later, use an ACL and a basic JSON or API exercise to cover security and automation. A candidate who can explain the why, not only type a command, is better prepared for variations.

In the final week, do one full timed mixed practice session and review all weak areas. Confirm that your materials match the selected version and that you have a test appointment, acceptable identification, and a plan for getting to the test center or setting up online. Avoid buying multiple new resources at the last minute. Use the remaining time to reinforce known gaps and preserve rest.

If your exam date is near the version change

A candidate taking v1.1 near February 2, 2027 should consider the five-day failed-retake wait and appointment availability before placing a first attempt at the end of the window. A later appointment uses v2.0, for which the corresponding published topic list should guide study. The retake wait is a minimum, not an assurance that a slot exists on the earliest day.

A two-hour weekly plan might reserve one session for learning and one for retrieval or practice. On the learning session, cover a small set of objectives and verify them through documentation or a lab. On the practice session, solve fresh tasks, review errors, and revisit earlier domains. If your schedule allows more, add time for subnet calculations and configuration. If work or family limits study, extend the calendar instead of pretending the same content fits into fewer hours.

At the end of the first cycle, take a cumulative check across all six domains. If the errors remain concentrated in one area, repeat the relevant module with different scenarios. If mistakes are scattered, improve basic reading and troubleshooting procedure: identify source, destination, layer, evidence, and constraint. In the last week, keep practice mixed and confirm appointment details. The v1.1/v2.0 boundary means your final review must match the exam code and date on the booking.

Reviewing answers can take longer than answering questions, and that time is valuable. Explain why each wrong option fails; if it could work under a different topology or requirement, write down what condition would make it correct. That contrast improves flexibility. Do not count a correct guess as mastery. Re-test it later with a new prefix, VLAN number, or route table.

A two-hour weekly plan might reserve one session for learning and one for retrieval or practice. Cover a small set of objectives and verify them through documentation or a lab. On the practice session, solve fresh tasks, review errors, and revisit earlier domains. If your schedule allows more, add subnetting and configuration. If work or family limits study, extend the calendar instead of pretending the same content fits into fewer hours.

At the end of the first cycle, take a cumulative check across all six domains. If errors remain concentrated in one area, repeat the relevant module with different scenarios. If mistakes are scattered, improve the basic troubleshooting procedure: identify source, destination, layer, evidence, and constraint. In the last week, keep practice mixed and confirm appointment details. Your final review must match the exam code and date on the booking.

Reviewing answers can take longer than answering questions, and that time is valuable. Explain why each wrong option fails; if it could work under a different topology or requirement, write down what condition would make it correct. Do not count a correct guess as mastery. Re-test it later with a new prefix, VLAN number, or route table.