Most of the CompTIA Network+ N10-009 exam tips you'll find online are fine in a generic way — read the objectives, know the ports, do practice questions. Not wrong, but not particularly useful either. The people I've watched fail Network+ rarely failed because they didn't know what an OSI layer was. They failed because they couldn't subnet under pressure, or they burned twelve minutes on a single PBQ and ran out of time, or they studied the whole objectives list evenly when two topics carry most of the actual weight.
So this post is less of a comprehensive objectives walkthrough and more a list of things I wish people understood before they sat down at the Pearson VUE center. Some of it is domain-specific. Some of it is about how the exam actually behaves.
The exam format, in one paragraph
Up to 90 questions, 90 minutes, passing score is 720 out of 900 (roughly 83%, not 80% — people get this wrong all the time). Mix of multiple choice and performance-based questions, with PBQs typically showing up in the first handful of questions. No penalty for guessing, so never leave anything blank. One minute per question is the math, but you won't actually spend that — the MCQs go faster and the PBQs eat into your budget hard. More on that below.
What actually matters: subnetting and PBQs
If you only take two things from this post, take these.
Subnetting shows up everywhere on N10-009. Not just in questions that obviously ask you to subnet — you'll see it embedded in troubleshooting scenarios, in PBQs where you have to assign addresses, in questions where the "trick" is noticing that the host is actually in a different subnet than the gateway. If you can't do subnetting in your head (or at least on the back-of-envelope scratch paper they give you) in under 90 seconds, you will bleed time on the exam.
I've seen people score in the mid-80s on practice tests and still fail because they were slow at subnetting. The practice tests don't stress you on timing the way the real exam does. One pattern worth watching for: if you're using a subnet cheat sheet during practice, you haven't actually learned it yet. You've learned how to look things up.
Do 50+ subnetting problems without a reference. Keep going until it's muscle memory — CIDR to subnet mask, network address, broadcast address, usable host range, all of it. This is the single highest-ROI skill on the exam.
PBQs are the other thing people misjudge. N10-009 usually drops 1–3 of them, and they load first. This is a trap. If you spend 20 minutes on the first PBQ, you've now given yourself about 70 minutes for 85+ remaining questions, and you're already in a bad headspace. Skip any PBQ that's eating you up. Flag it. Come back at the end. The MCQs are faster and more predictable, and every MCQ you answer is worth roughly the same points as a PBQ chunk.
A few more things about PBQs specifically:
- Read the whole scenario and the whole question before you click anything. Some PBQs lock your answer after a single interaction.
- If the PBQ is a simulated terminal or config screen, check what commands are available first. You don't have to use all of them.
- If you're genuinely stuck, eliminate obviously wrong choices and go. An 80% guess that moves you forward beats a perfect answer that costs ten minutes.
The five domains, weighted honestly
Official weightings:
| Domain | Weight |
|---|---|
| 1.0 Networking Concepts | 23% |
| 2.0 Network Implementation | 20% |
| 3.0 Network Operations | 18% |
| 4.0 Network Security | 21% |
| 5.0 Network Troubleshooting | 18% |
Here's how I'd spend study time, which is not proportional to the weights.
Domain 1 (Networking Concepts) gets the most weight and contains subnetting, ports, and the OSI model. Probably 30–35% of your study time. This is where you build the mental scaffolding the other domains hang off of.
Domain 4 (Network Security) is surprisingly deep for an exam that isn't Security+. You need to know firewall types, VPN protocols, common attacks, and authentication protocols cold. The overlap with Security+ content is real — if you've already passed Security+, this domain is almost free.
Domain 5 (Troubleshooting) isn't hard in terms of content, but it rewards people who've actually used the tools. If you've never run tracert or looked at netstat -an output in the wild, spend a weekend in a lab or in any Windows/Linux VM playing with these. Reading about them doesn't stick.
Domain 2 (Implementation) and Domain 3 (Operations) are mostly memorization — cable standards, 802.11 flavors, SNMP versions, documentation practices. Go wide, not deep. These are where most questions have a clear right answer if you've seen the term before.
Domain 1 specifics worth calling out
The OSI model gets tested more than you'd think, and not just "name Layer 3." You'll get scenario questions: a device can't resolve a domain name — what layer is the problem at? (Layer 7 in practice, because DNS is an application-layer protocol, even though a lot of people want to say Layer 3.) Know what lives where, not just the mnemonic.
Port numbers. There's no way around memorizing these. Focus on the ones below and you'll cover most of what the exam asks:
- 20/21 FTP, 22 SSH/SFTP, 23 Telnet, 25 SMTP
- 53 DNS, 67/68 DHCP, 69 TFTP
- 80 HTTP, 110 POP3, 143 IMAP, 443 HTTPS
- 161/162 SNMP, 389 LDAP, 636 LDAPS
- 445 SMB, 3389 RDP, 3306 MySQL
You probably don't need SIP (5060) or the obscure database ports for Network+ specifically, but they don't hurt.
TCP vs UDP comes up in a way that trips people up. Know not just the difference but which protocols use which. DNS is mostly UDP (53) but uses TCP for zone transfers. NTP is UDP. VoIP signaling is TCP-ish, media is UDP. The exam likes questions where the wrong answer is "DNS uses TCP" and you need to catch it.
Domain 4 notes
The thing that surprises people about Network+ security is how much it expects you to know about authentication protocols. RADIUS vs TACACS+ comes up often. Know that RADIUS uses UDP, encrypts only the password, and is an IETF standard. TACACS+ uses TCP, encrypts the entire session, and is Cisco's thing. This is a frequent question pattern.
Firewall types also get tested more subtly than you'd expect. Stateless filters based on headers only. Stateful tracks connection state. Next-gen adds application awareness and often IDS/IPS features. The exam loves "which firewall would you deploy for X" scenarios.
VPN protocols: know IPsec (and roughly how IKE/ESP fit in), SSL/TLS VPN, and that PPTP is deprecated and insecure. You don't need to be able to configure a site-to-site tunnel, but you should know which protocol fits which scenario.
Domain 5: the tools you need hands-on time with
Reading about ping is not the same as actually using it. Same for every tool in this domain. If I had to rank the ones worth practicing with:
ping and tracert/traceroute first — know how to interpret the output, not just run the commands. A traceroute that dies at hop 7 tells you something different than one with high latency at hop 2.
nslookup and dig next. You need to understand what an A record vs a CNAME vs a PTR record is, and how to query each.
ipconfig and ifconfig/ip — use them regularly. Know what /all, /release, and /renew do.
netstat — run netstat -an on your own machine. See what's actually listening. It'll make the exam questions click in a way no textbook can.
CompTIA's troubleshooting methodology (identify the problem → theory of probable cause → test → plan of action → implement → verify → document) will almost certainly show up in at least one question. Just memorize the order.
Study timeline, briefly
If you have A+ or a year of IT experience: 5–8 weeks at 10–15 hours per week is realistic. Less if you work in networking already. More if you're coming in cold.
The ratio that works: spend the first 60% of your time learning, the last 40% doing practice questions and full-length timed tests. A lot of people invert this and spend too long in reading/video mode, which feels productive but isn't. You learn what you can recall under pressure, and reading doesn't train recall.
If you want the detailed breakdown, the Network+ week-by-week study plan has the structure I'd follow. And if you're still deciding which cert to start with, A+ vs Network+ covers the first-cert decision.
Practice tests: read the explanations
This is the most wasted part of most people's prep. People take a practice test, check the score, and move on. The score is the least valuable thing about a practice test.
Spend 30 minutes reviewing every question you got wrong and every question you got right for the wrong reason (guessed and happened to pick correctly). Write down the concept you missed. If the same concept shows up twice in your wrong-answer list, that's a signal to go back and study it — not re-do practice questions.
One pattern worth noting: practice tests from Wiley and similar publishers tend to run a touch harder than the real exam for MCQs, and a touch easier for PBQs. So if you're scoring 78%+ on full-length practice tests with proper explanations, you're in shape. Scoring 85%+ means you're probably ready to book the test. (Related read: practice tests vs the real exam for a deeper look at where they diverge.)
Exam day, short version
Get there 30 minutes early. The check-in process at Pearson VUE is genuinely slow, and being rushed into the testing room does not help your test-taking.
On the exam: skip hard PBQs on the first pass, answer every MCQ quickly on your first instinct, flag anything you're not sure about, come back. You'll usually have 10–15 minutes at the end to revisit flagged questions and the hard PBQs with a clear head. That time is more valuable than the equivalent time spent agonizing upfront.
Don't change answers unless you have a specific reason. First instinct is usually right, and second-guessing is how people talk themselves into wrong answers on questions they originally got correct.
For general exam-day logistics (check-in, what to bring, how results work), the CompTIA exam day guide covers it.
If you're a few weeks in and wondering whether you're actually on track, the fastest way to find out is a full-length diagnostic. Most people are wrong about where their weak spots are — they think they're weak on security and it turns out they're actually bleeding points on subnetting under time pressure, or vice versa.
LearnZapp has a free Network+ diagnostic — no signup, covers all five domains, gives you a per-domain breakdown so you know where to spend the next few weeks. Worth twenty minutes before you lock in the rest of your study plan.