Seven weeks at 10-12 hours a week is a realistic target for Network+ N10-009 if you're coming in with some IT background. If you've never looked at a subnet mask before, plan on nine or ten. If you're already in a help desk or junior admin role, you can probably compress this to five.
This Network+ study plan is the version I'd actually hand someone sitting down to start today. It's built around one non-negotiable habit (daily subnetting), a scored practice exam at the midpoint, and the assumption that you'll adjust the weekly hours based on where you're weakest. Not every week gets equal treatment here — some are genuinely lighter lifts than others.
The Exam, Briefly
N10-009 is 90 questions in 90 minutes, 720/900 to pass. Multiple choice plus performance-based questions (PBQs) where you'll drag-and-drop, configure, or troubleshoot something on a simulated network. Five domains:
- Networking Concepts (23%)
- Network Implementation (20%)
- Network Operations (18%)
- Network Security (21%)
- Network Troubleshooting (18%)
The weights matter because they'll shape where you spend your time. Domain 1 is the biggest and also the foundation for everything else, which is why the plan front-loads it.
One note about PBQs: they feel heavier than multiple choice questions and people burn too much time on them. We'll come back to that.
Week 1: OSI, TCP/IP, Ports and Protocols
Start with the OSI model and don't move on until you can draw all seven layers from memory and say what happens at each one. If that sounds excessive, it isn't — a huge percentage of Network+ questions are layer-aware even when they don't mention OSI directly. "This device operates at layer 3" is a phrase you need to understand instantly.
TCP/IP model next. Common ports and protocols after that: HTTP/80, HTTPS/443, SSH/22, FTP/20-21, DNS/53, DHCP/67-68, SMTP/25, POP3/110, IMAP/143, RDP/3389, SNMP/161-162, LDAP/389, LDAPS/636. Memorize at least the top 25. Build flashcards, drill them on your commute, whatever works. You want these to come back in half a second on exam day, not five.
TCP vs. UDP — know when each shows up and why. If you can explain why DNS queries use UDP but zone transfers use TCP, you understand this at the level the exam wants.
End the week with 50+ practice questions scoped to this material. Aim for 75% or better before moving on. If you can't hit that, you're not ready for Week 2 — spend another two or three days here.
Week 2: Addressing, Subnetting, Routing Basics, Wireless
This is the week that most candidates underestimate and then regret. The content area is broad — IPv4 classes and CIDR, private vs. public ranges, routing fundamentals, switching basics, wireless standards (802.11a/b/g/n/ac/ax) — but the thing that actually matters is subnetting.
Starting this week, subnetting becomes a daily habit. Thirty minutes every day, no skipping. Not "most days." Every day through the rest of the plan.
Why subnetting gets its own section
Subnetting is the single most reliable predictor I've seen for whether someone passes Network+. Not because it's a huge percentage of the raw question count, but because (a) it shows up in places you don't expect, including troubleshooting scenarios and PBQs, and (b) candidates who can't do it quickly under pressure eat their entire time budget on a handful of questions and panic on the rest.
Here's what happens to people who "know" subnetting but haven't drilled it: they see a /27 question, mentally start converting, realize they're second-guessing themselves, flag it to come back, and lose five minutes they'll never get back. Multiply that by three or four subnetting questions plus a PBQ that requires calculating a usable host range, and now they're taking the last 20 questions at a near-sprint.
So: drill until it's automatic. Here's what "automatic" looks like in practice:
- You see
192.168.10.0/26and immediately know the subnet mask is 255.255.255.192, the increment is 64, and there are 62 usable hosts. No conversion, no pencil work. - You can VLSM a given range into the smallest possible subnets without thinking about it.
- You can identify which subnet an IP belongs to faster than you can read the question.
Tools: a subnetting simulator (there are free ones), pencil-and-paper drills, and timed practice sets. Don't skip paper — the exam won't give you a calculator, and muscle memory on paper is different from clicking through a tool.
One pattern I see a lot: people build a subnetting cheat sheet, reference it for a week, and then never stop referencing it. The cheat sheet is a learning tool, not a crutch. Hide it by the end of Week 2.
Everything else this week (routing, switching intro, wireless) is lighter. Get the concepts. Run 100+ questions over the domain, subnetting-heavy. 90% or better on subnetting questions before you move to Week 3. If you're not there, extend this week — don't carry the weakness forward.
Week 3: Network Implementation
Routing protocols (OSPF, BGP, RIP, EIGRP), VLANs and trunking, switch port security, wireless deployment, WAN technologies (MPLS, Metro Ethernet, PPP), QoS, redundancy.
The trap in this domain is memorizing protocol facts without understanding when each one gets used. The exam tests scenarios — "A small branch office needs..." or "A multi-site enterprise with..." — and if you just memorized that OSPF is a link-state protocol, you'll miss questions that want you to choose it over EIGRP for a specific reason. Know distance-vector vs. link-state, know why BGP exists and where it lives, know why anyone would still run RIP in 2026 (mostly they wouldn't, but the exam doesn't always live in 2026).
75+ questions this week. Accuracy target is lower than Week 2 — 70% is fine. This domain is scenario-heavy and the scenarios feel unfamiliar until you've seen a few dozen.
Week 4: Network Security
Attacks, firewalls, VPNs, AAA, hardening, 802.1X, port security. This is 21% of the exam so it gets real time.
For every attack type — DDoS, MITM, DNS poisoning, ARP poisoning, VLAN hopping, evil twin, brute force, social engineering — know three things: what it is, how it's executed at a network level, and what control stops it. The exam often asks the third question, and if you can only answer the first, you're guessing.
Encryption: IPsec, TLS, SSL (and why SSL is deprecated but still shows up). Know which protocols operate at which layer, what modes IPsec has (transport vs. tunnel), and what problem each VPN type solves.
85+ questions. Security questions are wordy — the scenario often matters more than the specific technical detail. Slow down and read the question twice before picking.
Week 5: Operations + First Full-Length Practice Exam
Network Operations is a lighter domain conceptually — SNMP, syslog, NetFlow, IPAM, documentation standards, change management, backup and DR, policies and compliance. Most of it is "you know what good IT practice looks like." SNMP gets tested harder than the rest, so spend extra time on OIDs, traps, and community strings vs. SNMPv3 security.
But the main event this week is the practice exam. Full 90 questions, 90 minutes, no notes, no pauses, no checking your phone. Treat it like the real test. Take it somewhere quiet.
Score it honestly. If you're above 75%, you're on track. If you're below 65%, the problem is almost always one or two weak domains, not a general knowledge gap — figure out which, and weight Weeks 6 and 7 accordingly. If you're between 65% and 75%, you're probably fine but don't get complacent.
Another pattern worth mentioning: people who delay their first full-length practice exam usually delay booking the real test too. It's avoidance. Take the practice exam at the scheduled time even if you don't feel ready — that feeling of unreadiness is exactly what the test is for.
Week 6: Troubleshooting
Command-line tools are the backbone of this domain. ping, traceroute/tracert, nslookup/dig, netstat, ipconfig/ifconfig, arp, route, tcpdump, Wireshark basics. For each, know what it does, what its output looks like, and what problem you'd use it to diagnose. The exam likes to show you a partial output and ask what it tells you.
The troubleshooting methodology itself — identify the problem, establish a theory, test the theory, establish a plan, implement, verify, document — gets tested directly. Know the steps cold and in order. "What's the next step after you've tested a theory of probable cause?" is a gimme if you know the sequence and a coin flip if you don't.
Wireless troubleshooting, cable issues, performance problems, hardware vs. software faults fill out the rest. 80+ questions, focused on scenarios. Read the scenarios slowly — troubleshooting questions often bury one detail that changes the whole answer.
Week 7: Consolidate, Drill, and Two More Practice Exams
The last week is not about learning new material. It's about closing gaps and building exam-day endurance.
Daily: thirty minutes of subnetting (still — all the way to exam day), two hours rotating through whichever domains you scored weakest on, and at least two full-length practice exams spread across the week. Your target on those is 80% or better. If you're hitting that consistently, you're ready. If you're stuck at 72-76%, go back and look at which question types you're missing — usually it's a specific subtopic, not the whole domain.
A few things to verify before exam day:
- Subnetting doesn't require thinking. You just do it.
- You can identify the OSI layer any given technology operates at.
- You know why security controls exist, not just what they are.
- You can walk through the troubleshooting methodology without looking it up.
- You've seen enough PBQ-style questions that the format doesn't surprise you.
On the PBQ question: some people do them first, some save them for last. The argument for doing them last is that they eat time unpredictably and you want the MCQs banked before you touch one. The argument for doing them first is that you're fresher. I lean toward saving them for last, but if you've practiced both, pick the approach that felt better in your practice exams and stick with it. Don't change strategies on exam day.
What Usually Goes Wrong
A few patterns that show up over and over:
People skip the daily subnetting because they "get it." They don't. They understand it, which isn't the same as being able to do it in 45 seconds under pressure. By the time they realize this on the first practice exam, they've lost three weeks of reps.
People front-load all their studying into weekends. Two 6-hour Saturday sessions is worse than six 1-hour weekday sessions, and it's not close. Short, frequent exposure beats cramming on almost every topic in this exam.
People fail a practice exam and conclude they need another month. Usually what they need is to review the specific questions they missed, not start over. One bad practice score in Week 5 is normal. If your Week 7 scores are still in the 60s, then yes, push the exam date — but not before.
Closing Out
Seventy to eighty-four hours over seven weeks is a real commitment, but it's one of the more approachable IT certifications once you've scoped the work. The candidates I've seen struggle most weren't the ones who didn't know enough — they were the ones who hadn't practiced under realistic conditions, especially subnetting and PBQs.
If you haven't benchmarked yourself yet, that's worth doing before you commit to a schedule. A diagnostic test will tell you which domains need the most time, which means you can compress or extend specific weeks instead of guessing. LearnZapp has a free Network+ diagnostic that runs through all five domains and gives you a per-domain breakdown — no signup, no commitment, takes about 20 minutes: Take the Network+ diagnostic.
Then pick your start date, block the calendar, and start drilling subnets.