CompTIA N10-009 Cheat Sheet: Networking, Subnetting, and Switching

CompTIA N10-009 cheat sheet covering addressing, subnetting, switching, routing, wireless, and troubleshooting.

Use this cheat sheet for last-mile review, not first exposure. It works best after the lesson pages already make sense and you want the biggest Network+ distinctions on one screen before mixed review or exam day.

PBQ: Performance-based question that asks you to apply network logic instead of only recognizing a term.

SLAAC: Stateless address autoconfiguration, an IPv6 method where hosts build addresses from router advertisements.

CIDR: Prefix-length notation such as /27 or /64 used to describe a network boundary.

Fast lane picker

If the question is really about… Go first to… Strongest first move
devices, protocols, media, topologies, or IP behavior 1. Concepts classify the layer before naming the tool
routing, VLANs, wireless deployment, or cable installs 2. Implementation identify the boundary that traffic must cross
monitoring, documentation, DR, or management access 3. Operations decide whether the clue is operational, not packet-level
segmentation, identity, access control, or attack prevention 4. Security place the control at the right point in the path
symptoms, tool choice, or fault isolation 5. Troubleshooting prove the fault domain before changing anything

Quick elimination flow

    flowchart TD
	  A["Read the requirement or symptom"] --> B["Classify it: path, service, security, or operations"]
	  B --> C["Name the layer or boundary that owns the clue"]
	  C --> D["Eliminate answers that act at the wrong layer"]
	  D --> E["Pick the simplest answer that directly fits the requirement"]

N10-009 answer sequence

Use this when the stem mixes path, service, security, or operations clues.

    flowchart TD
	  S["Scenario"] --> L["Classify the layer"]
	  L --> B["Name the boundary that owns the clue"]
	  B --> R["Check routing, policy, or physical path"]
	  R --> V["Verify with the simplest direct fix"]

What to notice:

  • most Network+ misses start with bad classification, not a forgotten acronym
  • the wrong answer is often a real technology that acts too early, too late, or at the wrong boundary
  • the simplest direct fix is usually stronger than the fanciest one

Ports and protocols that matter

Service or protocol Default port(s) What the exam is usually testing Easy confusion
SSH 22 secure remote administration Telnet because both are terminal access
Telnet 23 insecure legacy remote access SSH
DNS 53 name resolution DHCP because both are basic network services
DHCP 67/68 address assignment and lease options DNS
HTTP / HTTPS 80 / 443 web transport, secure vs insecure TLS offload questions that sound like routing questions
SMTP 25 message transfer between mail systems IMAP or POP3, which are mailbox retrieval
IMAP / POP3 143 / 110 mailbox retrieval behavior SMTP
SNMP 161/162 monitoring and traps Syslog because both support operations visibility
RADIUS 1812/1813 AAA for network access, common in Wi-Fi and NAC TACACS+ because both support centralized AAA
TACACS+ 49 device-administration AAA with strong command accounting RADIUS
RDP 3389 remote desktop access SSH or VNC
SIP 5060/5061 VoIP call setup RTP, which carries media rather than signaling

High-confusion network pairs

Pair Keep this distinction clear
switch vs router a switch forwards inside a Layer 2 segment, a router moves traffic between Layer 3 networks
NAT vs PAT NAT is the broader translation concept, PAT is many-to-one translation using ports
ACL vs firewall ACLs are simpler stateless permit/deny rule sets, firewalls usually add deeper inspection and policy context
DHCP vs DNS DHCP gives clients network configuration, DNS translates names into addresses
RTO vs RPO RTO is acceptable restore time, RPO is acceptable data-loss window
MTTR vs MTBF MTTR is average repair time, MTBF is average time between failures
out-of-band vs in-band management out-of-band survives production path failure, in-band shares the normal network
latency vs packet loss latency is delay, packet loss is missing data that usually forces retransmission
threat vs vulnerability threat is the danger or actor, vulnerability is the weakness it can exploit

Addressing and path cues

Clue What it usually means Strongest first check
169.254.x.x APIPA self-assigned IPv4 address DHCP reachability or scope availability
127.0.0.1 local loopback only application or local stack test, not network reachability
::1 local IPv6 loopback same host-only meaning as 127.0.0.1
fe80::/10 IPv6 link-local same-link communication, router not required for neighbor discovery
client reaches by IP but not hostname naming problem, not routing first DNS records, resolver path, split-horizon assumptions
local access works, remote does not path issue beyond the local segment default gateway, route, ACL, NAT, VPN boundary
only one subnet or VLAN is broken boundary problem, not universal outage VLAN mapping, DHCP scope, interface routing, ACL boundary
stable host ordering required same entity must land together stable key, same subnet boundary, consistent path expectations

Wireless and access-control chooser

Requirement Strongest first fit Why
broad compatibility and acceptable modern security WPA2 still common, but weaker than WPA3 where supported
strongest current client security WPA3 stronger protections for supported clients
isolated guest access with web acceptance flow captive portal solves guest onboarding, not deep device trust
stop unknown devices before joining production NAC admission control is the key requirement
centralize user auth for Wi-Fi or VPN RADIUS common AAA backend for access decisions
device administration with detailed command accounting TACACS+ stronger fit for network admin access than endpoint access
long range but more interference risk 2.4 GHz better penetration, fewer clean channels
higher throughput with shorter practical range 5 GHz or 6 GHz more capacity, less legacy crowding

Operations and recovery cues

If the question mentions… Translate it to… Strongest first distinction
restore time RTO how fast the service must be back
acceptable data loss RPO how much data loss the business can tolerate
warm site vs cold site vs hot site DR readiness level cost vs recovery speed trade-off
baseline, threshold, alert, log, trap monitoring method decide whether the clue is visibility or root cause
out-of-band console or management network resiliency of administration useful when the production path is impaired
change record or rollback plan operations discipline safe change management, not troubleshooting improvisation

Quick symptom lens

Symptom First things to check Common trap
no link or unstable link cable type, duplex, speed, transceiver, PoE, port state blaming DNS for a physical issue
local network works but internet fails gateway, NAT, upstream route, WAN status changing client config when the edge path is broken
hostname fails but IP works DNS records, client DNS settings, resolver reachability restarting interfaces when name resolution is the real fault
wireless is slow or unstable channel overlap, interference, signal strength, authentication or roaming design treating every Wi-Fi issue as ISP latency
one role or user group is broken VLAN, SSID, ACL, NAC, or DHCP scope boundary assuming a whole-site outage
application is up but response is poor latency, packet loss, duplex mismatch, queueing, server-side bottleneck jumping straight to bandwidth upgrades

PBQ pattern reminders

  • map every interface, subnet, or SSID before changing anything
  • identify which evidence is proving a path issue and which evidence is proving a service issue
  • if a PBQ shows multiple devices, start from the failure boundary instead of reading every line left to right
  • on diagram questions, label gateways, VLAN boundaries, and management paths first
  • if two fixes both seem plausible, the one closest to the stated boundary is usually better

Last 15-minute review

Review this Because it fixes…
common ports and AAA protocols service-confusion misses
DHCP vs DNS vs gateway logic wrong fault-domain classification
NAT/PAT, VLAN, ACL, and FHRP roles design-choice misses
Wi-Fi bands and auth models wireless distractors that sound equally plausible
RTO/RPO and hot/warm/cold site terms operations-domain misses
troubleshooting methodology changing things before proving the problem

What strong answers usually do

  • classify the problem before naming the fix
  • choose the control that sits at the correct boundary
  • prefer the smallest design that directly meets the requirement
  • separate service problems from path problems
  • keep operations realism in mind when multiple answers sound technically possible

Quiz

Loading quiz…
Revised on Sunday, May 10, 2026