200-301 v2.0 — Cisco CCNA (200-301 v2.0) Exam Study Plan
Practical 7, 14, 30, and 60/90-day study plan for Cisco CCNA (200-301 v2.0) candidates, with labs, timed practice, and review routines.
How to use this Study Plan
This Study Plan is for candidates preparing for the real Cisco CCNA (200-301 v2.0), exam code 200-301 v2.0. It is designed to turn your remaining study time into a practical schedule that includes concept review, subnetting practice, hands-on lab work, troubleshooting, security review, automation basics, timed mock exams, and missed-question review.
Use the plan that matches your available time and your current readiness. If you are unsure, start with a diagnostic quiz and a small lab before choosing a schedule.
Which plan should you use?
| Time remaining | Best for | Daily time target | Main goal | Risk level |
|---|---|---|---|---|
| 7 days | Candidates who already studied and need final review | 2 to 4 hours | Tighten weak areas, timed practice, command recall, exam pacing | High if starting from scratch |
| 14 days | Candidates with networking background or prior CCNA study | 2 to 3 hours weekdays, longer weekend blocks | Rapid domain review plus labs and mocks | Moderate to high |
| 30 days | Candidates with basic networking knowledge but incomplete preparation | 90 minutes to 2.5 hours | Balanced concept review, subnetting, labs, troubleshooting, timed exams | Moderate |
| 60/90 days | Candidates starting early or rebuilding fundamentals | 45 to 90 minutes most days, longer lab blocks weekly | Full preparation path with repeated practice cycles | Lower if consistent |
If you have one week left and have not built or troubleshot basic Cisco-style labs, do not try to learn every topic from zero. Focus on the highest-value fundamentals: IP addressing, routing behavior, VLANs, trunking, OSPF basics, ACL logic, NAT concepts, wireless concepts, device security, and command interpretation.
Core CCNA preparation priorities
Do not study Cisco CCNA (200-301 v2.0) as a memorization exam only. You need to recognize designs, interpret outputs, choose commands, troubleshoot symptoms, and apply networking concepts under time pressure.
| Skill area | What to practice | Proof you are ready |
|---|---|---|
| IP addressing and subnetting | IPv4 subnet masks, host ranges, route summarization basics, IPv6 format and routing concepts | You can solve common subnetting questions quickly without overthinking |
| Network fundamentals | OSI/TCP-IP models, switching vs routing, cabling, interface behavior, MTU concepts, duplex/speed basics | You can explain why traffic does or does not cross a boundary |
| Switching and network access | VLANs, trunks, native VLAN concepts, STP behavior, EtherChannel, port security, wireless architecture | You can read switch output and find VLAN/trunk/STP problems |
| IP connectivity | Static routes, default routes, route selection, OSPF basics, first-hop behavior, IPv4/IPv6 routing tables | You can predict forwarding decisions from a routing table |
| IP services | DHCP, DNS, NAT, NTP, SNMP, syslog, QoS concepts where relevant | You can match services to symptoms and verify configuration intent |
| Security fundamentals | ACLs, secure management, AAA concepts, device hardening, Layer 2 security, VPN concepts | You can evaluate basic access rules and management-plane exposure |
| Automation and programmability | Controller-based networking, APIs, JSON, REST concepts, configuration management ideas | You can interpret basic automation terminology and data formats |
| Troubleshooting | Show commands, symptoms, elimination logic, layer-by-layer analysis | You can state the likely fault and the next verification command |
Daily practice rhythm
Use the same rhythm most days. Consistency matters more than occasional long sessions.
90-minute weekday rhythm
| Time | Activity | Notes |
|---|---|---|
| 10 min | Subnetting warm-up | Mix masks, usable ranges, route matching, IPv6 recognition |
| 20 min | Concept review | One focused topic only |
| 30 min | Hands-on lab or command-output review | Build, verify, break, and fix |
| 20 min | Practice questions | Topic-specific, not always random |
| 10 min | Missed-question log | Record why you missed it and what to review next |
2.5-hour extended rhythm
| Time | Activity |
|---|---|
| 15 min | Subnetting and route-selection drill |
| 35 min | Learn or review one objective area |
| 45 min | Lab, packet walk, or troubleshooting scenario |
| 35 min | Practice questions |
| 20 min | Missed-question review and flashcard cleanup |
| 10 min | Plan tomorrow’s weak-area task |
Weekly rhythm
| Day type | Best use |
|---|---|
| Weekday short session | Subnetting, one topic, short practice set |
| Weekday longer session | Lab and troubleshooting |
| Weekend block | Timed mock, deeper lab, full missed-question review |
| Day after mock | Review only; do not immediately take another full mock |
Start with a diagnostic
Before beginning any plan longer than 7 days, take a diagnostic set. It does not need to be a full mock exam, but it should cover multiple CCNA areas.
Diagnostic setup
| Step | Action | Output |
|---|---|---|
| 1 | Take a mixed practice set under time limits | Baseline accuracy and pacing |
| 2 | Do a small lab: VLANs, trunk, router-on-a-stick or inter-VLAN routing concept, static/default routing, basic verification | Hands-on baseline |
| 3 | Review all misses | Weak-area list |
| 4 | Sort misses by category | Study priorities |
| 5 | Choose the plan below | Schedule that fits your actual readiness |
Miss categories to track
| Category | Meaning | Fix |
|---|---|---|
| Concept gap | You did not know the rule or behavior | Relearn the topic, then answer 10 focused questions |
| Command gap | You knew the idea but not how to verify or configure | Run or read the relevant show/config commands |
| Troubleshooting gap | You could not isolate the fault | Use layer-by-layer analysis and write the next command |
| Subnetting gap | You lost time or made arithmetic errors | Daily short drills until automatic |
| Misread | You knew it but missed a keyword | Slow down and underline requirements in practice |
| Pacing issue | You ran out of time | Timed sets and skip/return strategy |
Missed-question review method
A missed question is useful only if you convert it into a repeatable lesson.
Error log format
| Field | What to write |
|---|---|
| Date | When you missed it |
| Topic | Example: OSPF neighbor state, ACL direction, trunking, NAT, DHCP |
| Question type | Concept, command, troubleshooting, scenario, subnetting |
| Why I missed it | Be specific: “forgot longest prefix match,” not “routing” |
| Correct rule | One sentence |
| Verification command or clue | Example: show ip route, show interfaces trunk, ACL hit count |
| Retest date | 24 to 72 hours later |
| Status | Open, improved, mastered |
Review cycle
- Review missed questions within 24 hours.
- Re-answer similar questions after 48 to 72 hours.
- Convert repeated misses into a mini-lab or command-output drill.
- Retire an error only when you can explain the rule without looking it up.
- In the final week, review the error log daily.
Hands-on lab rotation
Use Cisco Packet Tracer, Cisco Modeling Labs, real equipment, or another appropriate lab environment. The tool matters less than repeated configuration, verification, and troubleshooting.
| Lab type | What to build or analyze | Verification focus |
|---|---|---|
| Basic device setup | Hostnames, interfaces, passwords, SSH management concepts | Management reachability and secure access basics |
| VLAN and trunking | Multiple VLANs, access ports, trunk links, native VLAN awareness | VLAN membership and trunk status |
| STP and EtherChannel | Redundant links, STP root behavior, bundled links | Loop prevention and link aggregation state |
| Inter-VLAN routing | Router-on-a-stick or Layer 3 switching concept, depending on lab capability | Default gateway and VLAN-to-VLAN reachability |
| Static/default routing | Multiple routers, static routes, default route, route failure | Routing table interpretation |
| OSPF basics | Single-area OSPF concepts, neighbor formation, advertised networks | Neighbor status and route learning |
| ACLs | Standard/extended ACL logic, placement concepts, direction | Permit/deny behavior and hit counts |
| NAT concepts | Inside/outside logic and translation behavior | Translation and reachability symptoms |
| IP services | DHCP, DNS/NTP/syslog/SNMP concepts where labbed or reviewed | Service role and verification clue |
| Automation basics | Read JSON, identify REST/API concepts, controller-based networking terms | Data format and architecture recognition |
Command-output checklist
Know what these commands are used for and what key clues to look for in output.
show ip interface brief
show ipv6 interface brief
show running-config
show vlan brief
show interfaces trunk
show spanning-tree
show etherchannel summary
show ip route
show ipv6 route
show ip ospf neighbor
show access-lists
show ip nat translations
show cdp neighbors
show lldp neighbors
show logging
Do not just memorize commands. Practice answering:
- What is working?
- What is missing?
- Which layer is failing?
- What is the next best verification step?
- Which configuration line is likely causing the symptom?
When to use timed mock exams
Timed mocks are for readiness and pacing, not for learning every new topic. Use them after you have completed enough review to make the result meaningful.
| Plan | First timed mock | Second timed mock | Final timed mock |
|---|---|---|---|
| 7 days | Day 1 diagnostic or Day 2 | Day 4 or Day 5 | Optional light mock or timed set on Day 6 |
| 14 days | Day 1 or Day 2 | Day 8 or Day 9 | Day 12 |
| 30 days | End of Week 2 | End of Week 3 | Day 26 or Day 27 |
| 60 days | Around Day 21 to 28 | Around Day 42 to 49 | Final 7 to 10 days |
| 90 days | Around Day 30 to 40 | Around Day 60 to 70 | Final 7 to 10 days |
Mock exam rules
- Review every missed and guessed question before taking another mock.
- Do not take full mocks on back-to-back days unless you are only testing stamina.
- Track pacing by section or time block.
- Mark guessed-correct questions as review items.
- Stop using mocks as your main study tool if you keep missing the same topic. Return to targeted review and labs.
7-day final review plan
Use this if your exam is in one week. This is a final review plan, not a complete first-time CCNA course.
| Day | Focus | Study actions | Output |
|---|---|---|---|
| 1 | Baseline and triage | Take a timed mixed diagnostic. Review all misses. Build a weak-area list. | Top 5 weak topics |
| 2 | IP addressing and routing | Subnetting drills, route selection, static/default routes, OSPF basics, IPv6 route recognition | Faster route and subnet decisions |
| 3 | Switching and wireless | VLANs, trunks, STP, EtherChannel, port security, wireless architecture and access concepts | Clean switch troubleshooting notes |
| 4 | IP services and security | DHCP, DNS, NAT, NTP, syslog, SNMP concepts, ACLs, secure management, AAA concepts | ACL and service symptom review |
| 5 | Automation and weak labs | REST/API/JSON/controller concepts, plus labs for weakest network topic | Final weak-area corrections |
| 6 | Timed practice and error log | Take a timed mock or long timed set. Review misses deeply. No broad new content. | Final error log |
| 7 | Light final review | Subnetting warm-up, command checklist, flashcards, missed-question log. Stop heavy studying early. | Calm, organized exam plan |
7-day rules
- Stop adding new material after Day 5 unless it fixes a repeated critical miss.
- Prioritize questions you missed twice.
- Do at least one hands-on or command-output review daily.
- Keep subnetting short and daily.
- Do not spend the final night rebuilding your entire study plan.
14-day focused plan
Use this if you have some networking background, have studied CCNA before, or can commit focused time each day.
| Day | Focus | Tasks |
|---|---|---|
| 1 | Diagnostic | Mixed timed set, small lab, error log setup |
| 2 | IPv4 subnetting and fundamentals | Subnet masks, host ranges, route matching, OSI/TCP-IP, Ethernet basics |
| 3 | IPv6 and routing table logic | IPv6 address types, default routes, longest prefix match, forwarding decisions |
| 4 | VLANs and trunks | Access/trunk ports, VLAN membership, trunk symptoms, command-output review |
| 5 | STP, EtherChannel, Layer 2 security | STP behavior, root concepts, bundled links, port security concepts |
| 6 | Wireless and network access review | AP/WLC concepts, WLAN security concepts, roaming and architecture terms |
| 7 | IP connectivity lab day | Static/default routing, OSPF basics, neighbor and route verification |
| 8 | Timed mock and review | Take timed mock or long timed set; review every miss |
| 9 | IP services | DHCP, DNS, NAT, NTP, syslog, SNMP, QoS concepts where relevant |
| 10 | Security fundamentals | ACLs, secure management, AAA concepts, device hardening, VPN concepts |
| 11 | Automation and programmability | Controller-based networking, APIs, REST, JSON, automation terminology |
| 12 | Timed mock | Full timed practice; build final weak-area list |
| 13 | Weak-area sprint | Review only the top weak topics; run targeted labs |
| 14 | Final review | Error log, command checklist, subnetting, pacing plan; no heavy new content |
14-day emphasis
Spend the most time on topics that combine concepts with troubleshooting:
- VLAN/trunk mismatches
- STP and EtherChannel state
- Route selection
- OSPF neighbor and route learning basics
- ACL direction and placement
- NAT inside/outside logic
- DHCP and default gateway symptoms
- Secure management and access control
- API/JSON/controller terminology
30-day balanced plan
Use this if you want a realistic one-month path with enough time for labs, review, and timed practice.
Weekly structure
| Week | Main goal | Topics | Practice output |
|---|---|---|---|
| 1 | Build foundations | Network fundamentals, IPv4/IPv6, subnetting, basic routing logic | Daily subnetting, baseline lab, first error log |
| 2 | Network access and IP connectivity | VLANs, trunks, STP, EtherChannel, wireless, static routing, OSPF basics | Switching and routing labs |
| 3 | Services, security, automation | DHCP, DNS, NAT, NTP, syslog, SNMP, ACLs, device security, automation basics | Security/service drills and first timed mock review |
| 4 | Exam readiness | Mixed practice, troubleshooting, weak-area review, final mocks | Stable pacing and reduced repeat misses |
30-day schedule
| Days | Focus | What to do |
|---|---|---|
| 1 | Diagnostic | Mixed quiz, small lab, error log |
| 2-3 | Network fundamentals | Models, Ethernet, cabling, interface states, switching vs routing |
| 4-6 | IPv4 subnetting | Masks, host ranges, VLSM-style reasoning, route matching |
| 7 | IPv6 basics and weekly review | IPv6 format, address types, route recognition, review Week 1 misses |
| 8-10 | VLANs and trunks | Configure and verify VLANs, trunking, native VLAN concepts |
| 11-12 | STP and EtherChannel | Root behavior, blocked ports, bundle verification, failure symptoms |
| 13 | Wireless | AP/WLC concepts, WLAN security and architecture terms |
| 14 | Week 2 lab review | Combined switching lab and missed-question review |
| 15-17 | IP routing | Static/default routes, routing table decisions, OSPF basics |
| 18 | Timed mock 1 | Full or long timed set; review thoroughly |
| 19-20 | IP services | DHCP, DNS, NAT, NTP, syslog, SNMP concepts and symptoms |
| 21-22 | Security fundamentals | ACLs, secure management, AAA concepts, port security, VPN concepts |
| 23 | Automation | APIs, REST, JSON, controller-based networking, automation use cases |
| 24 | Troubleshooting day | Mixed fault isolation: Layer 1 through Layer 4 reasoning |
| 25 | Timed mock 2 | Measure pacing and repeated misses |
| 26-27 | Weak-area sprint | Only top weak topics; targeted labs and focused question sets |
| 28 | Command-output review | Read show outputs and predict faults |
| 29 | Final timed set | Shorter timed set or full mock if stamina/pacing needs confirmation |
| 30 | Final review | Error log, subnetting, commands, rest plan |
30-day time allocation
| Activity | Recommended share |
|---|---|
| Concept review | 30% |
| Hands-on labs and command output | 30% |
| Practice questions | 25% |
| Missed-question review | 15% |
If you skip the missed-question review, the plan becomes less effective. The error log is where improvement compounds.
60/90-day full preparation path
Use this path if you are starting early, new to networking, returning after a long break, or want a less compressed schedule.
Phase plan
| Phase | 60-day path | 90-day path | Focus | Deliverable |
|---|---|---|---|---|
| 1 | Days 1-10 | Days 1-15 | Foundations and diagnostic | Baseline score, error log, basic topology lab |
| 2 | Days 11-20 | Days 16-30 | IP addressing and network fundamentals | Fast subnetting and route-selection confidence |
| 3 | Days 21-32 | Days 31-50 | Switching, VLANs, trunks, STP, EtherChannel, wireless | Network access lab portfolio |
| 4 | Days 33-42 | Days 51-65 | Routing and IP connectivity | Static/default/OSPF troubleshooting drills |
| 5 | Days 43-50 | Days 66-75 | IP services and security | ACL, NAT, DHCP, secure management review |
| 6 | Days 51-55 | Days 76-82 | Automation and programmability | API/JSON/controller terminology confidence |
| 7 | Days 56-60 | Days 83-90 | Final readiness | Timed mocks, weak-area sprint, final review |
Phase details
Phase 1: Foundations and diagnostic
| Task | Completion standard |
|---|---|
| Take a baseline mixed practice set | You know your weak domains |
| Build a simple two-switch/two-router or equivalent topology | You can verify interfaces and reachability |
| Start subnetting drills | You can complete short drills without looking up mask charts every time |
| Create error log | Every miss has a cause and retest date |
Phase 2: Addressing and fundamentals
Practice daily:
- IPv4 subnet masks and host ranges
- Longest prefix match
- Default gateway behavior
- ARP and basic forwarding logic
- IPv6 address recognition
- Interface status interpretation
- Basic Ethernet and wireless terminology
Phase 3: Network access
Lab repeatedly:
- VLAN creation and port assignment
- Trunk configuration and verification
- Native VLAN and allowed VLAN symptoms
- STP root and port role concepts
- EtherChannel state and mismatch symptoms
- Port security concepts
- Wireless architecture and security concepts
Phase 4: IP connectivity
Focus on reading and predicting routing behavior:
- Static routes
- Default routes
- Floating static route concept
- OSPF basics
- Neighbor formation clues
- Routing table interpretation
- IPv6 routing recognition
Ask on every routing scenario: “Which route wins, and why?”
Phase 5: IP services and security
| Topic | Practice method |
|---|---|
| DHCP | Identify client, relay, server, gateway, and addressing symptoms |
| DNS | Know the role and common failure impact |
| NAT | Inside/outside logic and translation symptoms |
| NTP | Time synchronization purpose and verification concepts |
| Syslog/SNMP | Monitoring and management use cases |
| ACLs | Direction, order, implicit deny, placement logic |
| Secure management | SSH, local users, management access, password handling concepts |
| AAA | Authentication, authorization, accounting roles |
| Layer 2 security | Port security and common access-layer protections |
Phase 6: Automation and programmability
Keep this practical and vocabulary-driven unless your weak-area results demand more depth.
Review:
- Controller-based networking concepts
- Northbound and southbound API ideas
- REST concepts
- JSON structure
- Automation benefits and risks
- Configuration management concepts
- AI-enabled network operations concepts where included in current Cisco exam topics
Phase 7: Final readiness
In the final phase:
- Take one or two timed mocks.
- Review every missed and guessed item.
- Repeat the top 3 weak labs.
- Stop broad new learning.
- Use short, high-confidence review sessions.
- Protect sleep and exam-day logistics.
Troubleshooting practice framework
Use the same troubleshooting sequence in labs and practice questions.
| Layer or area | Ask | Example clue |
|---|---|---|
| Physical/interface | Is the interface up and correct? | Down/down, admin down, speed/duplex issue |
| VLAN/access | Is the endpoint in the right VLAN? | Wrong access VLAN |
| Trunking | Are VLANs carried between switches? | Missing allowed VLAN or trunk not formed |
| STP/EtherChannel | Is the path blocked or bundle broken? | Unexpected STP state or suspended member |
| IP addressing | Is the address/mask/gateway correct? | Host in wrong subnet |
| Routing | Is there a route back? | One-way reachability |
| Services | Is DHCP, DNS, NAT, or NTP involved? | Address missing, name fails, translation absent |
| Security | Is traffic filtered or management blocked? | ACL order/direction issue |
| Automation/management | Is the controller/API/data format understood? | JSON or REST concept confusion |
Final-week rules
The last week should reduce uncertainty, not create new confusion.
Stop adding new material
| Time remaining | New material rule |
|---|---|
| 7 days | Add only critical missing topics |
| 5 days | Stop broad new learning |
| 3 days | Review error log, commands, subnetting, and weak labs only |
| 1 day | Light review only; no full-day cram |
Final-week checklist
- I can complete routine subnetting questions without long pauses.
- I can read a routing table and explain the selected path.
- I can identify common VLAN, trunk, STP, and EtherChannel symptoms.
- I can explain OSPF neighbor and route-learning basics.
- I can apply ACL order, direction, and implicit deny logic.
- I can explain NAT, DHCP, DNS, NTP, syslog, and SNMP at a practical level.
- I can recognize secure management and AAA concepts.
- I can interpret common Cisco show-command output.
- I can explain controller-based networking, APIs, REST, and JSON basics.
- I have reviewed every repeated missed-question pattern.
- I have a pacing strategy for the real exam.
Exam-readiness checks
You are likely ready when most of the following are true:
| Readiness area | Target behavior |
|---|---|
| Accuracy | You are consistently meeting or exceeding your practice provider’s readiness benchmark |
| Pacing | You finish timed practice without rushing the final questions |
| Subnetting | You solve common subnetting and route-matching items quickly |
| Labs | You can build and verify basic switching/routing scenarios without constant notes |
| Troubleshooting | You can identify the next best verification step |
| Commands | You recognize the purpose of common show commands |
| Weak areas | Your repeated misses are decreasing |
| Confidence | You can explain why wrong answers are wrong, not just why one answer is correct |
Avoid using a single mock score as your only readiness measure. Combine timed performance, error-log trends, lab confidence, and command-output interpretation.
If you are behind schedule
Use triage instead of panic.
| Problem | What to do |
|---|---|
| Too many weak topics | Pick the top 3 most repeated misses and fix those first |
| Subnetting is slow | Do 10 to 15 minutes daily, not one long cram session |
| Labs take too long | Use smaller labs focused on one failure at a time |
| Mock scores are flat | Stop taking mocks temporarily and review missed-question patterns |
| Automation feels unfamiliar | Focus on terminology, JSON recognition, REST/API concepts, and controller roles |
| Security questions are inconsistent | Rebuild ACL logic: order, direction, source/destination, implicit deny |
| Routing questions are slow | Practice routing table decisions and longest prefix match daily |
Practical next step
Choose your time path, take a diagnostic set, and create your missed-question log today. Then begin the first scheduled study block with one focused topic, one hands-on or command-output task, and a short timed practice set.