Overview
Network Troubleshooting is tied for the largest Network+ domain at 24%, reflecting that diagnosing problems is the core of network work. It has five objectives. The troubleshooting methodology covers CompTIA's structured steps: identify the problem, establish a theory, test it, establish a plan, implement and verify, and document. Cabling and physical issues covers diagnosing cable faults, interface errors and physical-layer problems. Network service issues covers diagnosing problems with DHCP, DNS and other services. Performance issues covers diagnosing latency, throughput and bottleneck problems. Tools and protocols covers using the right utility, such as ping, traceroute, nslookup and others, to solve a problem.
At 24%, this domain is heavily tested and integrates every other domain. The exam rewards following the methodology, diagnosing the correct layer and cause, and choosing the right tool, applying the concepts, implementations, operations and security from the earlier domains.
How it's tested
Network+ questions in this domain present a symptom and ask for the next methodology step, the likely cause, or the correct tool. Network+ questions are vendor-neutral and scenario-based, so read the situation and choose the networking concept, configuration or tool it points to before answering.
-
Methodology step
A troubleshooting situation is described, and you choose the correct next step in the methodology.
-
Diagnose the cause
A symptom is described, and you identify the cabling, service or performance cause.
-
Right tool
A diagnostic need is described, and you choose the correct tool or protocol.
A user can reach a server by its IP address but not by its name, and you must find where connectivity fails. Pinging the IP already works, so the issue is name resolution rather than reachability. Using nslookup to query DNS reveals whether the name resolves correctly, isolating a DNS problem, which is the correct tool choice the exam expects for a name-resolution symptom rather than ping or traceroute.
Domains 5
Official domains from the CompTIA outline, in outline order.
5.1 Explain the troubleshooting methodologyCompTIA's structured troubleshooting steps.
- What it means
- This covers CompTIA's network troubleshooting methodology: identify the problem, establish a theory of probable cause, test the theory, establish a plan of action, implement the solution or escalate, verify full system functionality and implement preventive measures, and document findings, actions and outcomes.
- What to understand
- The methodology is a disciplined, ordered process that prevents guessing. Each step builds on the last, from gathering information to confirming the fix and documenting it. The exam frequently asks for the correct next step, so knowing the order and purpose of each step is essential.
- How it shows up
- A troubleshooting situation is described, and you must choose the correct next methodology step.
- Common confusion
- Performing steps out of order, such as implementing a fix before establishing and testing a theory.
5.2 Troubleshoot common cabling and physical interface issuesCable faults, interface errors and physical-layer problems.
- What it means
- This covers diagnosing cabling and physical issues: cable faults such as opens, shorts and miswires, attenuation and interference, duplex and speed mismatches, interface errors and counters, and transceiver and port problems.
- What to understand
- Physical-layer problems include damaged or wrong cables, interference, and mismatched speed or duplex settings, revealed by interface error counters and cable testers. Many connectivity problems are physical, so checking cabling and interfaces early is important. Recognizing physical symptoms distinguishes them from configuration issues.
- How it shows up
- A connectivity symptom is described, and you must identify the cabling or physical cause.
- Common confusion
- Confusing a physical cabling or duplex-mismatch issue with a higher-layer configuration problem.
5.3 Troubleshoot common issues with network servicesDiagnosing DHCP, DNS and other service problems.
- What it means
- This covers diagnosing problems with network services: DHCP issues such as address exhaustion or wrong scopes, DNS resolution failures, gateway and routing problems, and other service misconfigurations that break connectivity.
- What to understand
- Service problems often present as specific symptoms: no address suggests DHCP, resolving by IP but not name suggests DNS, and reaching the local network but not beyond suggests a gateway or routing issue. Mapping the symptom to the responsible service is the key diagnostic skill.
- How it shows up
- A service symptom is described, and you must identify the responsible service and cause.
- Common confusion
- Confusing a DNS resolution problem with a general connectivity problem; resolving by IP but not name points to DNS.
5.4 Troubleshoot common performance issuesLatency, throughput and bottleneck problems.
- What it means
- This covers diagnosing performance problems: latency and jitter, low throughput, congestion and bottlenecks, duplex mismatches causing poor performance, and saturation, using metrics and baselines to find the constraint.
- What to understand
- Performance problems trace to a bottleneck revealed by metrics compared against a baseline: a saturated link, a duplex mismatch, congestion, or an overloaded device. The methodical approach measures to isolate the constraint rather than guessing, and addresses the specific cause.
- How it shows up
- A performance symptom is described, and you must identify the bottleneck or cause.
- Common confusion
- Confusing a latency problem with a throughput problem, or overlooking a duplex mismatch as a performance cause.
5.5 Use the appropriate tool or protocol to solve networking issuesping, traceroute, nslookup and other tools.
- What it means
- This covers selecting the right diagnostic tool or protocol: ping for reachability, traceroute for path, nslookup or dig for DNS, ip or ifconfig for interface details, packet captures, cable testers, and other hardware and software tools.
- What to understand
- Each tool answers a specific question: ping tests reachability, traceroute shows the path and where it breaks, nslookup queries DNS, and a cable tester checks physical media. Choosing the tool that matches the symptom is a core, heavily tested skill, since the right tool isolates the cause efficiently.
- How it shows up
- A diagnostic need is described, and you must choose the correct tool or protocol.
- Common confusion
- Confusing the purpose of tools, such as using ping where traceroute or nslookup is the right choice.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Troubleshooting methodology
The ordered CompTIA steps.
- Remember
- Follow them in order.
- Tested as
- Methodology questions.
- Trap
- Doing steps out of order.
-
Establish and test a theory
Form and verify a probable cause.
- Remember
- Before implementing a fix.
- Tested as
- Methodology questions.
- Trap
- Fixing before testing.
-
Verify and document
Confirm the fix and record it.
- Remember
- The final steps.
- Tested as
- Methodology questions.
- Trap
- Skipping documentation.
-
Cable faults
Opens, shorts, miswires, attenuation.
- Remember
- Found with a cable tester.
- Tested as
- Cabling questions.
- Trap
- Assuming a config issue.
-
Duplex and speed mismatch
Mismatched interface settings.
- Remember
- Cause errors and poor performance.
- Tested as
- Physical questions.
- Trap
- Overlooking the mismatch.
-
DHCP symptoms
No or wrong address.
- Remember
- Points to DHCP.
- Tested as
- Service questions.
- Trap
- Confusing with DNS.
-
DNS symptoms
Resolve by IP but not name.
- Remember
- Points to DNS.
- Tested as
- Service questions.
- Trap
- Confusing with connectivity.
-
Gateway and routing symptoms
Reach local but not beyond.
- Remember
- Points to gateway or routing.
- Tested as
- Service questions.
- Trap
- Confusing with DNS.
-
ping and traceroute
Reachability versus path.
- Remember
- traceroute shows where it breaks.
- Tested as
- Tool questions.
- Trap
- Using ping where traceroute fits.
-
nslookup and dig
Query DNS resolution.
- Remember
- For name-resolution problems.
- Tested as
- Tool questions.
- Trap
- Using ping for DNS issues.
-
Cable tester
Checks physical media.
- Remember
- For suspected cable faults.
- Tested as
- Tool questions.
- Trap
- Overlooking physical testing.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
ping vs. traceroute vs. nslookup
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| ping | Tests reachability | Is the host reachable | Using for path or DNS |
| traceroute | Shows the path | Where it breaks | Using for simple reachability |
| nslookup | Queries DNS | Name resolution | Using for reachability |
DHCP vs. DNS vs. gateway symptoms
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| DHCP | No or wrong address | Address assignment fails | Confusing with DNS |
| DNS | IP works, name does not | Name resolution fails | Confusing with connectivity |
| Gateway/routing | Local works, remote does not | Path beyond the subnet fails | Confusing with DNS |
Physical vs. configuration issue
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Physical | Cable, interface, duplex | Check media and counters first | Assuming a config issue |
| Configuration | Settings or service | Check after physical | Overlooking physical causes |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Fix before theory
- What candidates pick
- Implement a solution before establishing and testing a theory of probable cause.
- Why it looks right
- It seems faster.
- Why it's wrong
- The methodology requires establishing and testing a theory before implementing a fix, to avoid guessing.
Clue to watch for The question asks for the next step after identifying the problem.
-
ping for name resolution
- What candidates pick
- Use ping to diagnose why a server is reachable by IP but not by name.
- Why it looks right
- ping tests connectivity.
- Why it's wrong
- Resolving by IP but not name is a DNS issue; nslookup or dig queries DNS to diagnose it.
Clue to watch for The host works by IP but not by name.
-
Config issue is physical
- What candidates pick
- Investigate switch configuration first for a link with high interface errors.
- Why it looks right
- Configuration is a common cause.
- Why it's wrong
- High interface errors and connectivity loss often indicate a physical cable or duplex problem; check the physical layer first.
Clue to watch for Interface error counters are high.
-
DNS is connectivity
- What candidates pick
- Treat a name-resolution failure as a general loss of connectivity.
- Why it looks right
- Both break access.
- Why it's wrong
- If the IP is reachable but the name is not, connectivity is fine and the problem is DNS.
Clue to watch for The IP works but the name fails.
-
ping for path
- What candidates pick
- Use ping to find which hop along a route is dropping traffic.
- Why it looks right
- ping tests reachability.
- Why it's wrong
- traceroute shows the path and where it breaks; ping only tests whether the final host responds.
Clue to watch for The need is to find where along the path traffic fails.
Answer framework
For any Domain 5 scenario, use these steps to find the answer Network+ expects.
- Follow the troubleshooting methodology in order: identify the problem, establish and test a theory, plan, implement or escalate, verify, and document.
- Check the physical layer early, since cabling, interface and duplex issues cause many connectivity problems.
- Map service symptoms to the responsible service: no address to DHCP, name-not-IP to DNS, local-not-remote to the gateway or routing.
- For performance, measure against a baseline to isolate the bottleneck, such as saturation or a duplex mismatch.
- Choose the tool that matches the symptom: ping for reachability, traceroute for path, nslookup for DNS, and a cable tester for physical media. Where two options seem to fit, pick the one that most precisely matches the scenario's symptom or requirement.
Practice question
Want more like this? The Network+ practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
This is the largest domain and integrates every other, so treat it as applying the whole exam methodically. First, learn CompTIA's troubleshooting methodology cold and in order, because the exam frequently asks for the correct next step, and the order matters: establish and test a theory before implementing a fix, and always verify and document.
Then practice mapping symptoms to causes: physical issues like cable faults and duplex mismatches, service issues where the symptom points to DHCP, DNS or the gateway, and performance issues isolated against a baseline. Finally, master tool selection, matching ping, traceroute, nslookup and others to the symptom, which is a core, heavily tested skill.
Because this domain draws on everything else, strong earlier domains pay off here. This is the final domain, so finish with full practice tests across all five, and practice the 90-minute pacing. Because Network+ rewards hands-on familiarity, practice configuring and troubleshooting on real or simulated devices rather than only reading, and review missed practice questions by domain to find weak spots.
FAQ
How much of Network+ is Domain 5?
Network Troubleshooting is 24% of the exam, tied for the largest domain, because methodical diagnosis is central to network work.
What is the CompTIA troubleshooting methodology?
An ordered process: identify the problem, establish a theory of probable cause, test the theory, establish a plan of action, implement the solution or escalate, verify full functionality and add preventive measures, and document findings and outcomes.
Why does the order of the methodology matter?
Because each step builds on the last, and the exam frequently asks for the correct next step. Implementing a fix before establishing and testing a theory is guessing and is the wrong order.
If a host is reachable by IP but not by name, what is wrong?
Connectivity is working, so the problem is name resolution, which is a DNS issue. The right tool to diagnose it is nslookup or dig, not ping.
How do I choose the right troubleshooting tool?
Match the tool to the question: ping for reachability, traceroute for the path and where it breaks, nslookup for DNS resolution, and a cable tester for physical media. Choosing the right tool isolates the cause efficiently.
What symptoms point to a physical-layer problem?
High interface error counters, intermittent connectivity, and issues after a cabling change often indicate physical problems such as a damaged cable or a duplex or speed mismatch, which should be checked early.
How does Domain 5 connect to the rest of the exam?
Troubleshooting applies the concepts of Domain 1, the implementations of Domain 2, the operations and monitoring of Domain 3, and the security of Domain 4 to diagnose and resolve real problems.
Other Networking certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 5 knowledge
You have covered the methodology, cabling, service and performance diagnosis, and tools. Test whether you can find the real cause and choose the right tool under exam conditions.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the Network+ AI tutor Get any concept explained your way