CompTIA Network+ (N10-009) FAQ

Network+ questions usually reduce to three moves: identify the right layer, pick the right tool, and avoid changing the network before you have evidence.

What does Network+ (N10-009) actually cover?

CompTIA positions N10-009 as the current Network+ V9 exam. The objective areas span networking concepts, implementation, operations, security, and troubleshooting, so the exam is broader than memorizing ports and cable types. It expects you to read a symptom, decide which layer you are really working in, and choose the least-wrong action with the right protocol, tool, or control.

How long is the exam and how many questions?

CompTIA lists 90 minutes, a maximum of 90 questions, and a mix of multiple-choice plus performance-based questions (PBQs). The current published passing score is 720 on a 100-900 scale.

What do Network+ PBQs usually test?

PBQs usually test applied reasoning, not raw memorization. Common patterns include:

• reading a small topology and identifying the broken path
• matching symptoms to the right layer and tool
• configuring or validating VLAN, routing, wireless, or security choices
• interpreting command output such as ipconfig, ping, tracert, dig, or switch/router status

If a PBQ is slow, flag it and return after you have banked the easier multiple-choice points.

How deep does subnetting go?

Deep enough that you should be fast with it. Expect to identify:

• network address
• broadcast address
• usable host range
• whether two hosts share a subnet
• whether the default gateway is valid for that host

You do not need exotic edge cases to pass, but you do need /24 through /30 patterns to feel automatic under time pressure.

Do I need to memorize ports and protocols?

Yes, but the exam rewards functional recall more than isolated flashcard trivia. You should know the high-yield set well enough to use it in a scenario:

• DNS 53
• DHCP 67/68
• HTTP 80
• HTTPS 443
• SSH 22
• SMB 445
• RDP 3389
• NTP 123
• SNMP 161/162
• RADIUS 1812/1813

If a question says “host can reach the IP but not the name,” the real win is recognizing DNS quickly, not just remembering that the number 53 exists.

How should I think about VLANs, trunks, and STP?

Treat them as a set, not as isolated definitions.

• Access port: carries one VLAN for an endpoint.
• Trunk: carries multiple VLANs between switches, APs, or router-on-a-stick links.
• Allowed VLANs: define which VLANs can traverse that trunk.
• STP: protects the switching domain from loops and broadcast storms.

A classic trap is choosing Layer 3 routing before you confirm the endpoint is on the right access VLAN or the VLAN is even allowed across the trunk.

How much wireless detail matters?

Enough to make a good design or troubleshooting decision:

• when 2.4 GHz is crowded and why 5 GHz or 6 GHz is often better
• why 1/6/11 matter for 2.4 GHz
• when WPA2-Enterprise or WPA3-Enterprise with 802.1X is the right choice
• why WPS is a bad security choice
• how channel width, interference, and client capability affect real throughput

The exam is more interested in practical wireless judgment than in reciting marketing speeds.

Does cloud and virtual networking show up?

Yes. The current objective summary explicitly includes cloud concepts such as VPC-style isolation, network security groups, gateways, virtualization, elasticity, and scalability. The questions are usually still networking questions first. You are expected to reason about segmentation, routing, DNS, and reachability whether the environment is on-prem or virtualized.

Which tools should I recognize?

At minimum, be comfortable choosing between:

• ipconfig or ip a for interface configuration
• ping for basic reachability and loss
• tracert or traceroute for path visibility
• nslookup or dig for DNS
• tcpdump or Wireshark for packet capture awareness
• cable testers, tone generators, loopback plugs, and Wi-Fi analyzers for physical and wireless troubleshooting

The exam often tests the best next tool, not every possible tool.

What are the most common Network+ traps?

• Solving an application symptom before checking physical and data-link basics
• Ignoring DNS when IP connectivity works
• Confusing a trunk problem with a routing problem
• Treating Wi-Fi theoretical throughput as expected user throughput
• Forgetting that APIPA means “DHCP path problem” before it means “replace the NIC”
• Picking a security control that is weaker than the environment requires

What is a good study plan for Network+?

A focused 4-5 week plan works for many learners:

• Week 1: OSI, ports, IPv4, subnetting, DHCP, DNS
• Week 2: switching, VLANs, trunks, routing, NAT, cloud networking concepts
• Week 3: wireless, cabling, fiber, security controls, AAA
• Week 4: operations, documentation, monitoring, troubleshooting, first full mock
• Week 5: PBQ drills, miss-log review, second full mock, lighter recall sets

Keep a short miss log. Convert every recurring mistake into a one-line rule such as “IP works but name fails means DNS before gateway replacement.”

What is a smart next certification after Network+?

That depends on direction:

• Security path: Security+
• Support/infrastructure path: Server+, Linux+, or vendor-specific admin certs
• Cloud path: AWS, Azure, or Google Cloud entry-level tracks
• Operations path: Network automation, DevOps, or security operations fundamentals

Network+ is strongest when you treat it as a foundation, not a stopping point.

Quiz