Study guide
Official Troubleshooting Methodology and Evidence Handling
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
Official Troubleshooting Methodology and Evidence Handling
Key Takeaways Explain This Topic AI
The troubleshooting process starts with identifying the problem and gathering information before changing the environment.
A theory should be tested before a plan of action is implemented, and a disproven theory loops back to step two.
Escalation is appropriate when the issue is outside authority, skill, access, safety, or business-impact limits.
Verification includes confirming full system functionality and implementing preventive measures when appropriate.
Evidence handling requires accurate documentation, timestamps, preservation, and chain of custody when security or legal review may be involved.
Last updated: June 2026
Troubleshooting Methodology
Troubleshooting is a repeatable decision process, not a guessing game. On the CompTIA Network+ N10-009 exam, Domain 5 (Network Troubleshooting) carries the single largest weight at 24% , so methodology questions appear frequently. The exam rewards the answer that follows the documented method, not the answer that jumps directly to a favorite fix. Expect performance-based questions (PBQs) that ask you to drag the steps into order, plus multiple-choice items that ask "what should the technician do next?" The almost-always-correct early move is to gather facts, define scope, and avoid unnecessary change.
The full exam is up to 90 questions in 90 minutes; with a passing score of 720 on a 100-900 scale, mastering this domain's logic is high-yield.
The Seven Standard Steps
Step What it means Example
1. Identify the problem Gather information, question users, identify symptoms, determine if anything changed, approach multiple problems individually Ask who is affected, what changed, and exactly when the issue began
2. Establish a theory Question the obvious; use symptoms to form a likely cause; consider OSI top-to-bottom or bottom-to-top Suspect DNS if users can ping an IP but not a hostname
3. Test the theory Confirm or reject the cause; if confirmed, move on; if not, re-establish or escalate Query DNS directly with nslookup and compare expected records
4. Establish a plan Choose a fix and identify potential effects Schedule a firewall rule change in a maintenance window
5. Implement the solution Apply the approved fix, or escalate if needed Change a route, renew a certificate, replace a transceiver
6. Verify functionality Confirm the service works and implement preventive measures Test the user workflow, monitor logs, update alerting
7. Document findings Record cause, actions, results, and lessons learned Close the ticket with evidence and the final state
The steps loop. If a theory is disproven in step 3, return to step 2 and establish a new theory (or escalate). If a fix in step 5 creates a new symptom, roll back under change control and continue with evidence-based testing. A trap answer reverses verification and documentation, or skips testing the theory.
Two phrases inside the official steps are exam targets: in step 1, "determine if anything has changed" and "approach multiple problems individually," and in step 2, "if necessary, conduct external or internal research based on symptoms." When a scenario describes two simultaneous complaints, the correct early action is to treat each as a separate problem rather than assuming one root cause; bundling unrelated symptoms is a classic wrong answer.
Likewise, when a fix succeeds, step 6 explicitly pairs verifying functionality with implementing preventive measures, so an answer that stops at "it works now" without prevention or documentation is incomplete on Network+.
Identifying Scope
Scope dramatically narrows the likely cause, and scope questions are a Network+ favorite.
- Scope clue Likely direction
- One user affected Endpoint, NIC, cable, switch port, user account, local DNS cache
- One VLAN affected Default gateway, VLAN assignment, DHCP scope, ACL, trunk config
- One site affected WAN link, edge router, site firewall, local ISP, power
- One application affected DNS record, certificate, load balancer, server pool, firewall rule
- All Internet access affected Default route, ISP, edge firewall, NAT, DNS forwarders
Do not assume the largest possible outage. A single disconnected patch cable and a failed core switch can both produce "cannot connect" reports, but the correct scope, and the correct fix, differ.
Change Management and Escalation
Recent changes are the strongest clues. Firmware updates, firewall edits, new switch deployments, DHCP scope changes, certificate renewals, routing changes, and ISP maintenance all explain sudden symptoms. But correlation is not proof; verify before changing more. Escalate when:
The issue exceeds your access or authorization level.
The impact is high or safety-critical.
The action requires a change window or business approval.
Evidence suggests a security incident.
Specialized vendor, cloud, or carrier support is required.
You have tested reasonable theories and need additional expertise.
Evidence Handling
Some troubleshooting produces evidence for security, compliance, or legal review: packet captures, firewall and authentication logs, switch port mappings, wireless association logs, screenshots, exported configurations, and device images.
- Evidence practice Why it matters
- Preserve original data Prevents accidental alteration
- Record timestamps and time zone Supports a reliable timeline
- Document who collected the evidence Supports accountability
- Hash files (e.g., SHA-256) when appropriate Demonstrates integrity
- Maintain chain of custody Tracks possession and transfer
- Work on copies, not originals Protects source artifacts
- Limit access Reduces disclosure and tampering risk
In a routine performance ticket, evidence handling may be simple documentation. In a suspected compromise, preserve logs and captures before making destructive changes when feasible, and escalate to incident response if policy requires.
Common Traps
Rebooting a device before checking logs or scope.
Implementing a fix before testing a theory.
Ignoring recent changes because they came from another team.
Failing to verify from the user's perspective after a fix.
Closing a ticket without documenting what changed.
Altering security-sensitive evidence without recording who handled it and when.