Use a compressed N10-009 review sheet for high-confusion terms, protocol distinctions, and troubleshooting shortcuts.
Use this page for compressed review after you already know the lessons. It is designed to keep the biggest Network+ distinctions visible when question wording starts to blur together.
ACL: Access control list, a rule set that allows or denies traffic or access attempts.
SLAAC: Stateless address autoconfiguration, an IPv6 mechanism for hosts to build their own addresses from router advertisements.
Use the cheat sheet when you need to:
flowchart TD
A["Read the symptom or requirement"] --> B["Is this about layer/path, service, security, or operations?"]
B --> C["Name the likely fault domain or design domain"]
C --> D["Throw out answers from the wrong layer"]
D --> E["Pick the simplest answer that directly fits the clue"]
What to notice:
| If the question is really about… | Go first to… |
|---|---|
| layers, devices, protocols, addressing, or topology | 1. Networking Concepts |
| routing, VLANs, wireless deployment, or installs | 2. Network Implementation |
| documentation, monitoring, services, management, or DR | 3. Network Operations |
| identity, segmentation, attacks, or hardening | 4. Network Security |
| symptom analysis, tool choice, and fault isolation | 5. Network Troubleshooting |
| Pair | Keep this distinction clear |
|---|---|
| switch vs router | switch forwards inside a Layer 2 domain, router moves traffic between Layer 3 networks |
| NAT vs PAT | NAT is the broader translation concept, PAT is address sharing by translating ports too |
| SSH vs Telnet | both are management protocols, but SSH protects the session with encryption |
| DHCP vs DNS | DHCP assigns addressing information, DNS resolves names to addresses |
| RTO vs RPO | RTO is restore time, RPO is acceptable data-loss window |
| latency vs packet loss | latency is delay, packet loss is missing data that often forces retransmission |
| threat vs vulnerability | threat is the danger or actor, vulnerability is the weakness |
| exploit vs impact | exploit is the attack method, impact is what got harmed |
| out-of-band vs in-band management | out-of-band stays available even when the normal production path is impaired |
| Symptom | First things to check |
|---|---|
| no link or unstable link | cable type, transceiver, interface counters, PoE, duplex, port status |
| local access works but remote access fails | gateway, route, ACL, NAT, DNS, VPN path |
| name-based access fails but IP access works | DNS records, resolver path, split-horizon assumptions |
| wireless feels slow or unstable | channel overlap, interference, signal strength, authentication or roaming design |
| only one user group is broken | VLAN assignment, SSID mapping, ACL, NAC, or DHCP scope boundaries |
| If the requirement is really about… | Strongest first fit |
|---|---|
| a stable branch with one obvious upstream path | static route and clear default path |
| many internal hosts sharing one public edge address | PAT |
| stopping unknown devices from joining the network | NAC |
| serving one client request to one backend | unicast |
| delivering to a subscribed group only | multicast |
| keeping a local default gateway available | FHRP |
When stuck, return to the troubleshooting methodology lesson. Many Network+ misses happen because the candidate changes something before proving the fault domain.