Best Courses to Prepare for CCNA: A Study Plan for Networking Jobs

If your goal is to pass CCNA and get a first role in network engineering, you need more than theory: mapped learning, repeated labs, practice tests, and a portfolio that proves you can troubleshoot live networks. This guide turns that into an exact plan.

Below you'll find what employers actually test for, how to align course modules to CCNA exam domains, a weekly study schedule with lab tasks, recommended tools and home-lab setups, and interview-ready steps you can take next. Where it helps, I’ll point out how the Coursera courses CCNA: Network Security, Automation, and Troubleshooting and Software Development Practices fit into the plan.

What CCNA employers test for today (topics and skills)

Employers hiring for junior network engineering roles typically look for a mix of foundational networking knowledge, hands-on configuration and troubleshooting skills, and basic security and automation familiarity. The CCNA aligns well with these expectations because it tests the same domains.

Key areas employers and interviewers probe:

• Network fundamentals: OSI/TCP-IP models, subnetting, IPv4/IPv6 addressing and basic routing concepts.
• Network access and switching: VLANs, trunking (802.1Q), STP basics, switch port security and common Layer 2 troubleshooting.
• IP connectivity and routing: static routing, OSPF single-area basics, route selection, and verifying routing tables.
• IP services: DHCP, NAT, basic QoS concepts, and DNS troubleshooting.
• Security fundamentals: access control lists (ACLs), device hardening basics, VPN concepts at a high level, and common threats.
• Automation and programmability: configuration management concepts, basic scripting (often Python), using APIs/automation tools to push or validate configs.
• Practical troubleshooting: methodical command-line troubleshooting, interpreting logs and packet captures, isolation and repair steps under time pressure.
• Soft skills: clear verbal explanation of troubleshooting steps, written summaries of incidents, and the ability to follow change-control processes.

How to map course modules to CCNA exam domains

When you pick courses to prepare for CCNA, map each course module to one or more CCNA domains so you don't waste time repeating content or missing gaps. Use the CCNA domains: Network Fundamentals, Network Access, IP Connectivity, IP Services, Security Fundamentals, Automation and Programmability as your checklist.

Example mappings to the two Coursera courses mentioned:

• CCNA: Network Security, Automation, and Troubleshooting (Coursera, all levels) — maps directly to Security Fundamentals, Automation and Programmability, and Troubleshooting practice. Use this course for hands-on labs about ACLs, device hardening steps, scripted verification, and structured troubleshooting workflows.
• Software Development Practices (Coursera, all levels) — maps to Automation and Programmability. Use it for version control (Git), testing approaches, code quality, and build/deploy basics so your automation scripts are maintainable and interview-ready.
• For Network Fundamentals, Network Access, IP Connectivity, and IP Services: pick courses or modules that include CLI configuration labs, OSPF examples, VLAN/trunking setups, DHCP/NAT labs, and packet-capture analysis. If a course has lab images or sandbox access, prioritize those modules.

Weekly study plan with practice and labs (12-week plan)

Below is a 12-week, lab-first plan you can adapt to part-time study. Aim for consistent daily blocks (for example 1–2 hours on weekdays, longer sessions on weekends). Replace course/module names with the specific lessons you choose, but follow the sequence: fundamentals → access & routing → services → security → automation → intensive troubleshooting and exam practice.

Each week includes goals, core lab tasks, and practice checks.

• Week 1 — Foundation and subnetting
• Goals: Review OSI/TCP-IP models, binary math, IPv4/IPv6 addressing and subnetting.
• Labs/tasks: Create subnets for small designs, calculate hosts and ranges, practice with subnetting drills and small Packet Tracer or GNS3 topologies.
• Check: Do timed subnetting problems and explain each step aloud.
• Week 2 — Switching and VLANs
• Goals: VLAN concepts, trunking (802.1Q), switchport modes, basic STP behavior.
• Labs/tasks: Build a 3-switch topology, configure VLANs, trunks, and inspect MAC tables. Simulate link failure and observe STP convergence behaviors if possible.

Weekly study plan continued

Continue the schedule with routing, services, security, automation and consolidation weeks. Each week keep at least one small written artifact: network diagram, config snippet, or lab write-up you can show in interviews.

• Week 3 — IPv4 routing basics
• Goals: Static routes, default gateway, routing table basics.
• Labs/tasks: Configure static routes across a 3-router topology and verify reachability with traceroute and ping.
• Week 4 — OSPF essentials
• Goals: Single-area OSPF, neighbor relationships, LSDB basics.
• Labs/tasks: Configure OSPF on multiple routers, force SPF changes by bringing interfaces down and back up, and verify LSAs and routing changes.
• Check: Explain how OSPF chooses routes and identify when OSPF will not form neighbors (mismatched timers, network types).

Weekly study plan continued (IP services, security, automation, and exam prep)

Finish the plan by covering IP services, security fundamentals, automation, and then focus on full practice exams and labs.

• Week 5 — IP services
• Goals: DHCP, NAT basics, DNS troubleshooting methods.
• Labs/tasks: Deploy a DHCP server in a topology, configure PAT/NAT on an edge router and validate translations.
• Week 6 — Review and mixed troubleshooting
• Goals: Mix routing/switching/services in one lab and practice troubleshooting scenarios under time constraints.
• Labs/tasks: Introduce broken configs and timed exercises. Practice systematic troubleshooting: gather, hypothesize, test, resolve.
• Check: Record and time each troubleshooting session; aim to reduce time while keeping correct steps documented.

Weekly study plan continued

Cover the security and automation topics next, leveraging the Coursera courses where appropriate to build repeatable skills.

• Week 7 — Security fundamentals
• Goals: ACLs, device hardening basics, port security concepts.
• Labs/tasks: Apply standard and extended ACLs to filter traffic, secure switch ports, and demonstrate how ACLs affect routing and reachability.
• Suggested resource: Use CCNA: Network Security, Automation, and Troubleshooting modules that focus on ACLs and hardening to consolidate this week.
• Week 8 — Advanced security and troubleshooting
• Goals: Review security log basics, practice responding to simulated incidents, and combine with prior routing/switching knowledge.
• Labs/tasks: Generate logs by denying traffic with ACLs, capture packets for analysis, and document an incident timeline.

Weekly study plan continued

Automation weeks should focus on small, useful scripts and safe change workflows. The Software Development Practices course helps you follow good habits so your scripts are reliable and presentable to employers.

• Week 9 — Automation basics
• Goals: Learn how automation fits into networking: templated configs, verification scripts, and basic API calls.
• Labs/tasks: Write a simple script that logs into a device (or lab emulator), retrieves interface status, and stores output. Practice idempotent changes where possible.
• Suggested resource: Use Software Development Practices to learn version control and testing habits for your scripts.
• Week 10 — Automation testing and repo building
• Goals: Put scripts into version control, add simple tests or assertions, and document usage in a README.
• Labs/tasks: Create a GitHub repo with your automation scripts, sample configs, and lab diagrams to present to interviewers.

Weekly study plan final weeks (intensive practice and exam simulation)

The final two weeks are for consolidation: full-lab builds that combine domains, timed practice exams, and polishing your interview materials.

Focus on active recall, hands-on fixes, and the artifacts you'll show in interviews.

• Week 11 — Full scenario labs
• Goals: Build multi-vendor-looking topologies (even in emulation), stitch services and security together, and perform end-to-end troubleshooting.
• Labs/tasks: Create incidents that require you to check VLANs, routing, NAT, and ACLs together. Write up a short incident report for each scenario.
• Week 12 — Mock exam and interview prep
• Goals: Take full practice exams, review weak areas, and rehearse technical explanations.
• Tasks: Schedule at least two timed practice exams, review every incorrect answer with labs, and prepare 3–5 concise lab demos and a 60–90 second verbal walkthrough of each for interviews.

Recommended courses