APIPA Address: How to Troubleshoot DHCP Failure and Restore Connectivity
A user's workstation is unable to access the internet. The technician runs ipconfig and sees an IP address of 169.254.1.15 with a subnet mask of 255.255.0.0. What is the most likely cause?
⚠ Common exam trap
Many exam-takers confuse APIPA with a static IP configuration or assume the issue is with the default gateway, but the 169.254.x.x address is a definitive indicator of DHCP server unresponsiveness, not a routing or DNS problem.
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
✓
The DHCP server is not responding.
The IP address 169.254.1.15 with a subnet mask of 255.255.0.0 is an Automatic Private IP Addressing (APIPA) address, which Windows assigns when a DHCP client fails to receive an IP lease from a DHCP server. This indicates that the DHCP server is not responding to the client's DHCP Discover messages, causing the client to self-assign an APIPA address and lose internet connectivity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The default gateway is unreachable.
Why it's wrong here
An unreachable gateway prevents routing beyond the local subnet, but the workstation would still hold a valid DHCP-assigned address. The 169.254.x.x APIPA address proves DHCP itself failed, which precedes gateway reachability. Gateway issues are tempting because they also cause no internet, yet the address would differ.
When this WOULD be correct
A user's workstation has a valid IP address (e.g., 192.168.1.10) but cannot access the internet. The technician verifies that the default gateway is unreachable via ping. In this scenario, the most likely cause is that the default gateway is down or misconfigured.
- ✓
The DHCP server is not responding.
Why this is correct
The 169.254.1.15 address falls within the APIPA range, which Windows self-assigns when a DHCP server fails to respond. The workstation could not obtain a valid lease, so it configured a link-local address, leaving it unable to reach the internet.
- ✗
The DNS server is misconfigured.
Why it's wrong here
A 169.254.x.x address is an APIPA self-assignment, meaning the DHCP server was unreachable, so DNS configuration is unrelated. DNS misconfiguration would still permit internet access by IP address; it is the correct answer only when name resolution, not connectivity, fails.
When this WOULD be correct
A user can access the internet by IP address but not by domain name. The technician checks the network configuration and finds a valid IP address and default gateway. In this scenario, a misconfigured DNS server is the most likely cause.
- ✗
The IP address is statically assigned.
Why it's wrong here
A 169.254.x.x address is APIPA, self-assigned when DHCP fails — not a static configuration. Static addressing would show a valid, deliberately chosen address. It tempts because static IPs are manually set, but the 169.254 range is reserved for automatic link-local assignment, so this contradicts the observed address.
When this WOULD be correct
This option would be correct if the question described a workstation with a manually configured IP address that is incorrect or conflicting, such as a static IP that is outside the subnet or duplicates another device, causing network connectivity issues.
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 220-1101 exam frequently reuses these exact scenarios with slightly different constraints.
✓The DHCP server is not responding.Correct answer▾
Why this is correct
The 169.254.1.15 address falls within the APIPA range, which Windows self-assigns when a DHCP server fails to respond. The workstation could not obtain a valid lease, so it configured a link-local address, leaving it unable to reach the internet.
✗The default gateway is unreachable.Wrong answer — click to see why▾
Why this is wrong here
The IP address 169.254.1.15 is an Automatic Private IP Addressing (APIPA) address, which indicates that the workstation failed to obtain an IP from a DHCP server. An unreachable default gateway would not cause the workstation to assign itself an APIPA address; it would still have a valid DHCP-assigned IP but no connectivity.
★ When this WOULD be the correct answer
A user's workstation has a valid IP address (e.g., 192.168.1.10) but cannot access the internet. The technician verifies that the default gateway is unreachable via ping. In this scenario, the most likely cause is that the default gateway is down or misconfigured.
Why candidates choose this
Candidates may confuse symptoms of DHCP failure with gateway issues, as both result in no internet access. They might assume that if the gateway is unreachable, the workstation would show an APIPA address, not realizing APIPA is a DHCP failure indicator.
✗The DNS server is misconfigured.Wrong answer — click to see why▾
Why this is wrong here
The IP address 169.254.1.15 is an Automatic Private IP Addressing (APIPA) address, which indicates that the workstation failed to obtain an IP from a DHCP server. DNS misconfiguration would not cause the workstation to get an APIPA address; it would typically result in name resolution failures but the workstation would still have a valid IP.
★ When this WOULD be the correct answer
A user can access the internet by IP address but not by domain name. The technician checks the network configuration and finds a valid IP address and default gateway. In this scenario, a misconfigured DNS server is the most likely cause.
Why candidates choose this
Candidates may confuse symptoms of DNS issues (inability to resolve names) with the complete lack of network connectivity seen here, or they may think that any network problem is due to DNS without carefully analyzing the IP address assignment.
✗The IP address is statically assigned.Wrong answer — click to see why▾
Why this is wrong here
A statically assigned IP address would not typically be in the 169.254.x.x range, which is reserved for Automatic Private IP Addressing (APIPA) when DHCP fails. Static IPs are usually in the private or public ranges configured by the administrator.
★ When this WOULD be the correct answer
This option would be correct if the question described a workstation with a manually configured IP address that is incorrect or conflicting, such as a static IP that is outside the subnet or duplicates another device, causing network connectivity issues.
Why candidates choose this
Candidates may confuse static IP assignment with APIPA, thinking that any non-DHCP address is statically set, or they may overlook that APIPA addresses are automatically generated by the OS when DHCP fails.
Analysis generated from the official 220-1101blueprint 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
About these practice questions
One of 896 original 220-1101 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 220-1101 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 220-1101 exam.