N10-009 Network Troubleshooting Practice Question
A user reports that they cannot access any network resources. The technician checks the IP configuration on the workstation and sees an IP address of 169.254.10.55 with a subnet mask of 255.255.0.0. Which of the following should the technician check NEXT?
⚠ Common exam trap
The N10-009 exam often tests the misconception that a 169.254.x.x address indicates a DNS or static IP issue, when in fact it specifically points to DHCP server unreachability as the primary cause.
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
✓
Verify that the DHCP server is available and reachable
The IP address 169.254.10.55 with a subnet mask of 255.255.0.0 is an Automatic Private IP Addressing (APIPA) address, which Windows assigns when a DHCP server is unreachable. The next logical step is to verify that the DHCP server is available and reachable, as this directly addresses the root cause of the failed DHCP lease acquisition.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure a static IP address on the workstation
Why it's wrong here
While a static IP could resolve the issue temporarily, the root cause is likely DHCP, so statically assigning an IP bypasses the problem without fixing it. It is not the next step in standard troubleshooting.
When this WOULD be correct
A technician should configure a static IP when the DHCP server is confirmed unreachable or misconfigured, and the workstation needs temporary network access for troubleshooting, or when the network policy requires static IPs for certain devices.
- ✓
Verify that the DHCP server is available and reachable
Why this is correct
When a workstation fails to obtain an IP address lease from a DHCP server, it automatically assigns itself an Automatic Private IP Addressing (APIPA) address in the 169.254.0.0/16 range. This self-assigned address indicates a fundamental failure in the DHCP process. Therefore, the most logical and effective first troubleshooting step is to verify the operational status and network reachability of the DHCP server itself, as its unavailability is the direct cause of the APIPA assignment and lack of network resource access.
- ✗
Check the DNS server configuration on the workstation
Why it's wrong here
Checking the DNS server configuration is premature and incorrect in this scenario because DNS (Domain Name System) is responsible for resolving hostnames to IP addresses, not for assigning the initial IP address to a workstation. A workstation assigns an APIPA address when it cannot obtain an IP lease from a DHCP server, indicating a problem at the IP addressing layer, before DNS resolution would even become relevant for accessing network resources by name. DNS issues would manifest as an inability to reach resources by name, not an inability to obtain an IP address.
When this WOULD be correct
A user can access network resources by IP address but not by hostname. In this scenario, the workstation has a valid IP configuration (not APIPA), and the technician should check DNS server configuration to resolve name resolution issues.
- ✗
Replace the network cable
Why it's wrong here
Replacing the network cable is not the most appropriate initial step because an APIPA address assignment specifically indicates that the workstation's network interface is physically connected and operational, but it failed to complete the DHCP DORA (Discover, Offer, Request, Acknowledge) process. While a completely severed or faulty cable would prevent any network communication, including DHCP requests, it typically results in a "network cable unplugged" status or no link light, not an APIPA address. The presence of an APIPA address confirms the network adapter is active and attempting communication.
When this WOULD be correct
A user reports no network access, and the technician finds the workstation has no IP address (0.0.0.0) or a link-local address with a physical link indicator showing no activity. In that scenario, replacing the network cable would be a correct next step to rule out a physical connectivity issue.
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.
✓Verify that the DHCP server is available and reachableCorrect answer▾
Why this is correct
When a workstation fails to obtain an IP address lease from a DHCP server, it automatically assigns itself an Automatic Private IP Addressing (APIPA) address in the 169.254.0.0/16 range. This self-assigned address indicates a fundamental failure in the DHCP process. Therefore, the most logical and effective first troubleshooting step is to verify the operational status and network reachability of the DHCP server itself, as its unavailability is the direct cause of the APIPA assignment and lack of network resource access.
✗Configure a static IP address on the workstationWrong answer — click to see why▾
Why this is wrong here
The workstation has an APIPA address (169.254.x.x), indicating it failed to obtain an IP from a DHCP server. Configuring a static IP is premature before verifying DHCP server availability, as the root cause is likely DHCP-related.
★ When this WOULD be the correct answer
A technician should configure a static IP when the DHCP server is confirmed unreachable or misconfigured, and the workstation needs temporary network access for troubleshooting, or when the network policy requires static IPs for certain devices.
Why candidates choose this
Candidates may think that since the workstation has an invalid IP, manually setting a static IP will immediately fix the issue, overlooking the need to first diagnose why DHCP failed.
✗Check the DNS server configuration on the workstationWrong answer — click to see why▾
Why this is wrong here
The IP address 169.254.10.55 is an Automatic Private IP Addressing (APIPA) address, indicating the workstation failed to obtain an IP from a DHCP server. DNS configuration is irrelevant until IP connectivity is established; the immediate next step is to verify DHCP server availability.
★ When this WOULD be the correct answer
A user can access network resources by IP address but not by hostname. In this scenario, the workstation has a valid IP configuration (not APIPA), and the technician should check DNS server configuration to resolve name resolution issues.
Why candidates choose this
Candidates may confuse APIPA with general network configuration issues and incorrectly assume DNS is the cause, not recognizing that APIPA indicates a DHCP failure that must be resolved first.
✗Replace the network cableWrong answer — click to see why▾
Why this is wrong here
The IP address 169.254.10.55 is an Automatic Private IP Addressing (APIPA) address, indicating the workstation failed to obtain an IP from a DHCP server. A faulty network cable would typically cause a link-down condition, not an APIPA address, so checking the cable is not the next logical step.
★ When this WOULD be the correct answer
A user reports no network access, and the technician finds the workstation has no IP address (0.0.0.0) or a link-local address with a physical link indicator showing no activity. In that scenario, replacing the network cable would be a correct next step to rule out a physical connectivity issue.
Why candidates choose this
Candidates may assume that any network connectivity problem is caused by a physical issue like a bad cable, overlooking the specific indicator of APIPA which points to DHCP failure rather than a layer 1 problem.
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
Go deeper
Related to this question
Learn chapter
Troubleshoot: Network Connectivity
Key term
DHCP server
A DHCP server is a network device or service that automatically assigns IP addresses and other network configuration parameters to devices on a network, eliminating the need for manual configuration.
Key term
Automatic Private Internet Protocol Addressing
A fallback method used by a device to automatically assign itself an IP address when it cannot obtain one from a DHCP server.
About these practice questions
Courseiva writes every N10-009 question from scratch — 464 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.