Study guide
Choosing the Right Tool by Symptom PBQs
CompTIA Network+ N10-009
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
Current Exam Facts and Applied Networking Judgment Official Domain Weights and an 8-12 Week Study Plan How to Use Labs, Practice, and PBQ Workflow Missed-Question Notebook and Final Readiness Metrics
2 Domain 1: Networking Concepts (23%)
OSI and TCP/IP Models with Device and Protocol Mapping Networking Appliances and Where They Operate Ports and Protocol Decision Table Traffic Types and Encapsulation Flow
3 Domain 1: Media, Connectors, Transceivers, and Network Architectures
Copper, Fiber, Coax, and DAC Media Connector and Transceiver Selection Network Topologies and Design Patterns Cloud and Virtual Networking Concepts
4 Domain 1: IP Addressing and Subnetting Mastery
IPv4 Classes, Private/Public, APIPA, and Loopback CIDR, VLSM, and Subnet Math IPv6 Address Types and Notation Routing Basics and Longest Prefix Match
5 Domain 2: Network Implementation - Routing
Static vs Dynamic Routing and Route Selection OSPF, EIGRP, and BGP Basics at Network+ Depth NAT/PAT, VIP/FHRP, and Subinterfaces Routing PBQs and Troubleshooting Route Table Clues
6 Domain 2: Network Implementation - Switching
VLANs, Access Ports, Trunks, and Native VLAN STP/RSTP Loop Prevention and Bridge Roles Port Aggregation/LACP, MTU, Jumbo Frames, and Interface Settings Switch Implementation PBQs and Common Misconfigurations
7 Domain 2: Network Implementation - Wireless and Physical Implementation
Wi-Fi Standards, Bands, and Channels SSID Security, Guest Networks, and Authentication Antennas, Coverage, Roaming, Interference, and Site Surveys Physical Installation Implications
8 Domain 2: Network Implementation - Services Implementation
DNS Record Types and Troubleshooting Cues DHCP, DHCPv6, SLAAC, Scopes, Leases, and Relay NTP, PTP, NTS, and Time-Sensitive Networking Service Implementation PBQs: DNS, DHCP, VLANs, and Firewall Direction
9 Domain 3 Part A: Network Operations Documentation and Governance
Physical, Logical, Rack, Cable, Wireless Diagrams, and IPAM Asset Inventory, Baselines, SLAs, SOPs, and Runbooks Change Management and Request Tracking Lifecycle, EOL, EOS, Decommissioning, and Configuration Management
10 Domain 3 Part B: Monitoring, Remote Access, and Resilience
SNMP, Flow, Syslog, Packet Capture, Log Aggregation, APIs, and Port Mirroring Baselines and Performance Metrics Remote Access, Management Paths, and Secure Admin Habits DR and HA Concepts: RPO, RTO, MTTR, MTBF, Sites, Failover, and Testing
11 Domain 4: Logical Security and Secure Access (14%)
Encryption in Transit, Encryption at Rest, PKI, and Certificates IAM, MFA, SSO, Directory Services, and AAA Authorization, Least Privilege, RBAC, Geofencing, and Time-Based Access VPNs and Secure Management Design
12 Domain 4: Segmentation, Risk, and Network Attacks (14%)
Segmentation for Guest, BYOD, IoT, IIoT, SCADA, ICS, and OT Risk, Compliance, Audit, Data Locality, PCI, and GDPR Network Attacks and Scenario Cues Attack-to-Mitigation PBQ Tables
13 Domain 4: Security Controls and Hardening (14%)
Firewalls, IDS, IPS, Security Zones, and Screened Subnets ACLs, Filtering, NAC, Hardening, and Key Management Deception Technologies and Physical Security Zero Trust, SASE, and Trusted or Untrusted Zone Decisions
14 Domain 5: Troubleshooting Methodology and Tools (24%)
Official Troubleshooting Methodology and Evidence Handling Command-Line Tools: ping, traceroute, nslookup, dig, ipconfig, ifconfig, ip, arp, netstat, ss, and route Packet, Protocol, and Wi-Fi Analyzers Choosing the Right Tool by Symptom PBQs
15 Domain 5: Physical, Interface, and Wireless Troubleshooting (24%)
Cable Issues: Type, Attenuation, Crosstalk, Termination, and TX/RX Interface Issues: Errors, Discards, Duplex, Speed, Port Status, and PoE Transceiver, Fiber, and Signal Strength Troubleshooting Wireless Troubleshooting: Interference, Channels, Roaming, RSSI/SNR, Security, and Captive Portals
16 Domain 5: Network Services, Switching, Routing, and Performance Troubleshooting (24%)
DHCP, DNS, NTP, and IP Addressing Issues VLAN, STP, Trunk, Native VLAN, and ACL Issues Routing, Default Gateway, Route Table, and NAT Issues Congestion, Latency, Jitter, Packet Loss, and Application Performance Clues
17 Performance-Based Question Labs
Subnetting and VLSM Design Lab VLAN, Trunk, Router-on-a-Stick, and Firewall Rule Lab Wireless Deployment and Troubleshooting Lab Monitoring, Log Triage, and Route or Service Troubleshooting Lab
18 High-Yield Reference and Final Study Plan
High-Yield Ports and Protocols Table Wi-Fi, Cabling, Connectors, and Transceivers Quick Table Acronyms and Command-Line Tool Quick Table Final 7-Day Review Plan and Readiness Checklist
19 Final Synthesis: Strategy, Remediation, and Readiness
Mixed-Set Decision Strategy for Qualifiers and Close Answers Missed-Question Remediation Notebook by Error Type Exam-Day Time Management and PBQ Order 100-Question Readiness Simulation Blueprint Mapped to N10-009 Weights
Choosing the Right Tool by Symptom PBQs
Key Takeaways Explain This Topic AI
Tool choice should follow the symptom, the scope, and the layer being tested.
Start with low-risk observation before disruptive changes unless urgency or safety requires action.
Use physical tools for cabling and signal issues, command-line tools for host and path questions, and analyzers for traffic evidence.
Performance-based questions reward matching symptoms to the fastest tool that proves or narrows the cause.
Good troubleshooting separates DNS, DHCP, routing, switching, wireless, firewall, and application symptoms instead of treating every issue as a generic outage.
Last updated: June 2026
Tool Selection by Symptom
Performance-based questions (PBQs) typically present several symptoms and a toolbox, then ask you to map tools to problems. The goal is to choose the tool that narrows the cause with the least unnecessary disruption. Think in layers, roughly bottom-to-top: physical media, the local host configuration, neighbor (ARP) resolution, name resolution, routing path, firewall policy, service availability, and finally application behavior. Because Domain 5 is 24% of N10-009 and PBQs weigh heavily in scoring, this skill is among the highest-value to drill.
Symptom-to-Tool Decisions
- Symptom Best first tool or source Why
- Link light is off after a cable move Cable tester or a known-good patch cable Tests the physical path
- Need to locate an unlabeled cable Toner and probe Traces cable identity
- Fiber link shows high errors Optical power meter or interface counters Checks light levels and error counts
- One PC has wrong IP settings ipconfig /all or ip addr Shows local address, mask, gateway, DNS
Client gets an APIPA (169.254) address DHCP logs, ipconfig /renew, switch port/VLAN check Narrows DHCP reachability
Hostname fails but IP works nslookup or dig Tests DNS resolution
Traffic leaves one site but never reaches another traceroute, routing table, firewall logs Narrows path and policy
- An application port appears closed ss, netstat, port test, firewall logs Checks the listener and filtering
- Intermittent TCP retransmissions Packet capture and interface counters Shows loss and errors
- Poor Wi-Fi in one area Wi-Fi analyzer or spectrum analyzer Shows signal, channel, and interference
Physical tools still appear on Network+. Cable testers, certifiers, tone generators, loopback plugs, optical power meters, OTDRs, and multimeters answer questions software commands cannot.
Common Physical and Infrastructure Tools
- Tool Best use
- Cable tester Continuity, shorts, opens, miswires, split pairs
- Cable certifier Validates a run against a standard (e.g., Cat 6 to 1000BASE-T)
- Toner and probe Finds and traces unlabeled copper cables
- Loopback plug Tests whether an interface can transmit and receive
- Optical power meter Measures fiber light levels (dBm)
- OTDR Locates fiber distance-to-fault and reflection events
- Multimeter Tests voltage or continuity where appropriate
- Environmental monitor Watches temperature, humidity, water, and power
Choose a cable certifier when the question asks whether cabling meets a standard for a given speed or category. Choose a toner and probe when the question asks which wall jack maps to which patch-panel port. Choose an optical power meter for fiber signal levels and an OTDR for distance-to-fault on fiber.
PBQ Decision Pattern
When a PBQ asks you to drag tools onto symptoms, apply this pattern:
Identify scope: one host, one VLAN, one site, one application, or all users.
Identify the likely layer: physical, data link, network, transport, name resolution, authentication, or application.
Pick the tool that directly observes that layer.
Avoid tools that only prove something unrelated.
Verify with a second source if the first result could be blocked or misleading (e.g., ICMP filtering).
Worked example: users in one conference room report wired connections fail while Wi-Fi works and other rooms are fine. Scope is one room; the layer is physical/data-link. Best checks are switch port status, the patch cable, the wall jack, VLAN assignment, and a cable test. Replacing the Internet firewall does not match the scope and is the trap answer. A second example: a single new fiber uplink shows intermittent CRC errors and link flaps while copper drops elsewhere are clean.
Scope is one fiber run at the physical layer, so an optical power meter (to check whether received light is within the transceiver's dBm range) and interface error counters come first, followed by an OTDR if a break or bend is suspected. Reaching for dig, ss, or a Wi-Fi analyzer here would prove nothing about the fiber. The discipline is always the same: let scope plus layer point to exactly one observing tool, then corroborate before changing anything.
Tool Choice Examples
- Scenario Best tool choice Poor first choice
- Can ping 8.8.8.8 but cannot browse by name nslookup or dig Replace all access points
- One new drop cannot negotiate 1 Gbps Cable tester or certifier Review DNS TTLs
Remote office has high latency across both ISPs traceroute, SD-WAN stats, counters Clear one user's browser cache
- Web server process may not be listening ss or netstat on the server Tone generator
- Suspected firewall block to TCP 443 Firewall logs and packet capture Optical power meter
- Clients roam poorly between APs Wi-Fi analyzer and controller logs route print on a file server
- Common Traps
Do not use DNS tools to solve a physical link problem.
Do not use a cable tester to diagnose an expired certificate.
Do not rely on ping alone when ICMP may be filtered.
Do not start with destructive changes when observation can narrow the issue.
Always interpret tool output with scope: one failed client does not prove a core outage.