Question 11 of 464
N10-009 Network Troubleshooting Practice Question
A user reports that they cannot access the internet. The technician verifies the workstation has IP address 192.168.1.10 with subnet mask 255.255.255.0 and default gateway 192.168.1.1. The user can ping the default gateway successfully. Other users on the same subnet can access the internet. Which command should the technician run on the workstation to further isolate the issue?
⚠ Common exam trap
The N10-009 exam often tests the misconception that 'ipconfig /all' is the first step for any connectivity issue, but here the technician already has the IP configuration, so the trap is to overlook that the routing table must be examined when local connectivity works but internet access fails.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
netstat -r
The user can ping the default gateway (192.168.1.1), indicating Layer 2 and basic Layer 3 connectivity to the local router. However, other users on the same subnet can access the internet, so the issue is likely with the workstation's routing table. The 'netstat -r' command displays the IP routing table, allowing the technician to check for a missing or incorrect default route (e.g., destination 0.0.0.0 with gateway 192.168.1.1). This isolates whether the workstation knows how to forward traffic beyond the local subnet.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
ipconfig /all
Why it's wrong here
While `ipconfig /all` provides comprehensive details about a network adapter's configuration, including IP address, subnet mask, and default gateway, the problem statement implies that basic IP configuration has already been checked and appears correct, given the ability to ping the gateway. This command primarily shows assigned addresses and settings, but it does not display the actual routing table entries that govern how traffic is forwarded beyond the local subnet. Therefore, it won't reveal the specific routing table issues preventing internet access.
When this WOULD be correct
When a user cannot access the internet and the technician needs to verify the workstation's IP address, subnet mask, default gateway, DNS servers, and DHCP lease details to check for misconfiguration or APIPA address.
- ✓
netstat -r
Why this is correct
The `netstat -r` command (or `route print` on Windows) displays the local routing table, which dictates how the workstation forwards network traffic. Since the user can ping the default gateway but not an external IP address (8.8.8.8), the issue points to a problem with how the workstation routes traffic destined for the internet. Verifying the presence and correctness of the default route (0.0.0.0/0) pointing to the gateway (192.168.1.1) is crucial, as its absence or misconfiguration would prevent the workstation from knowing where to send internet-bound packets.
- ✗
tracert 8.8.8.8
Why it's wrong here
`tracert 8.8.8.8` is incorrect because the workstation can successfully ping its default gateway, and other users on the same subnet can access the internet. This indicates the issue is not a general routing problem beyond the gateway, but rather a specific configuration on the workstation preventing it from utilising the internet connection, possibly a DNS resolution failure. `tracert` is tempting as it diagnoses routing path issues to a remote destination. It would be the correct command if the user could not reach the default gateway, or if no users on the subnet could access the internet, to identify where connectivity breaks down on the path to the internet.
When this WOULD be correct
A user cannot reach a specific external server, but can ping the default gateway. Running tracert to that server would identify where packets are being dropped or delayed, isolating a routing issue beyond the local network.
- ✗
nslookup google.com
Why it's wrong here
The `nslookup google.com` command is used to test Domain Name System (DNS) resolution, which translates hostnames into IP addresses. However, the critical piece of information is that the user cannot ping 8.8.8.8, which is an IP address. This indicates a fundamental connectivity or routing problem at the network layer, preventing access to *any* external IP address, regardless of whether a hostname needs to be resolved. If the workstation cannot reach an IP address on the internet, DNS resolution will inherently fail, but it's a symptom of the underlying routing issue, not the root cause.
When this WOULD be correct
If the user could not access the internet but could ping the default gateway and other users had the same issue, or if the problem was specifically that domain names were not resolving while IP addresses worked, then `nslookup google.com` would be the correct command to diagnose DNS resolution.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The N10-009 exam frequently reuses these exact scenarios with slightly different constraints.
✓netstat -rCorrect answer▾
Why this is correct
The `netstat -r` command (or `route print` on Windows) displays the local routing table, which dictates how the workstation forwards network traffic. Since the user can ping the default gateway but not an external IP address (8.8.8.8), the issue points to a problem with how the workstation routes traffic destined for the internet. Verifying the presence and correctness of the default route (0.0.0.0/0) pointing to the gateway (192.168.1.1) is crucial, as its absence or misconfiguration would prevent the workstation from knowing where to send internet-bound packets.
✗ipconfig /allWrong answer — click to see why▾
Why this is wrong here
The technician already knows the workstation's IP configuration (IP, subnet mask, gateway) from the initial verification, so running ipconfig /all would provide no new information to isolate the issue.
★ When this WOULD be the correct answer
When a user cannot access the internet and the technician needs to verify the workstation's IP address, subnet mask, default gateway, DNS servers, and DHCP lease details to check for misconfiguration or APIPA address.
Why candidates choose this
Candidates often default to ipconfig /all as the first troubleshooting step for any network issue, overlooking that the necessary IP details are already known.
✗tracert 8.8.8.8Wrong answer — click to see why▾
Why this is wrong here
The user can ping the default gateway, indicating Layer 3 connectivity to the local network. Since other users on the same subnet can access the internet, the issue is likely DNS or routing beyond the gateway. tracert would show the path to 8.8.8.8, but the problem is more likely DNS resolution, not routing.
★ When this WOULD be the correct answer
A user cannot reach a specific external server, but can ping the default gateway. Running tracert to that server would identify where packets are being dropped or delayed, isolating a routing issue beyond the local network.
Why candidates choose this
Candidates may think tracert is a standard first step for internet connectivity issues, but here the symptom (others can access internet) suggests a local configuration problem, not a routing failure.
✗nslookup google.comWrong answer — click to see why▾
Why this is wrong here
The user can ping the default gateway, indicating Layer 3 connectivity to the local network. The issue is likely DNS resolution, but the question states other users on the same subnet can access the internet, so DNS is probably working. The technician needs to check the routing table to see if the default route is missing or incorrect, which `netstat -r` does. `nslookup` tests DNS, which is not the immediate next step given the symptoms.
★ When this WOULD be the correct answer
If the user could not access the internet but could ping the default gateway and other users had the same issue, or if the problem was specifically that domain names were not resolving while IP addresses worked, then `nslookup google.com` would be the correct command to diagnose DNS resolution.
Why candidates choose this
Candidates often jump to DNS issues when internet access fails, especially if pinging the gateway works. `nslookup` is a common tool for testing DNS, making it a tempting choice without fully analyzing the scenario.
Analysis generated from the official N10-009blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Visual reference
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
This N10-009 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the N10-009 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.