Troubleshooting APIPA Addresses and DHCP Failures
Short answer
C Address pool exhaustion prevents the DHCP server from responding, causing the client to assign itself an APIPA address instead of obtaining a valid configuration.
Question
Which of the following is most likely causing the issue?
Key Takeaways
The question tests recognition of APIPA (169.254.0.0/16) as a symptom of DHCP failure, specifically identifying address pool exhaustion as the likely cause among the choices.
Learn why a laptop displaying an Autoconfiguration IPv4 Address of 169.254.x.x points to DHCP issues like address pool exhaustion.
Common mistake: Choosing 'IIS server malfunction' because the user cannot access the intranet, ignoring that the problem lies in network connectivity/IP configuration rather than the web server itself.
Expert Analysis
The ipconfig /all output displays an Autoconfiguration IPv4 Address of 169.254.x.x. This range is reserved for APIPA (Automatic Private IP Addressing). In Windows networking, the operating system automatically assigns an APIPA address when a client device is configured to obtain an IP address via DHCP but fails to reach any available DHCP server within the allotted lease time.
This behavior indicates a breakdown in the communication between the client and the network's DHCP infrastructure. Since the laptop cannot communicate with the intranet site, it is effectively isolated on a local link-local segment without a valid gateway or DNS settings provided by the server.
Among the options provided:
- C (Address pool exhaustion) is the most plausible cause listed. If the DHCP server’s scope has run out of available IP addresses, it cannot respond to new requests from clients. The client receives no reply and falls back to APIPA. While technically this is a 'no response' scenario, it is the only option that explains why the DHCP server would be unreachable or unresponsive to the client's request.
- A (Short DHCP lease duration) affects how often renewals occur but does not prevent initial acquisition or cause APIPA assignment if the server is reachable.
- B (IIS server malfunction) refers to the web server hosting the site; it does not affect the client's ability to obtain an IP address.
- D (IDS misconfiguration) involves intrusion detection systems, which do not interfere with basic DHCP lease negotiation.
Therefore, the issue is caused by the inability to obtain a DHCP lease, pointing to address pool exhaustion as the root cause.
Exam Strategy
Always check the IP configuration first when a client cannot connect to network resources. Look specifically for the 'Autoconfiguration IPv4 Address' prefix. If you see 169.254.x.x, immediately rule out application-layer issues (like web servers) and focus on Layer 3/DHCP failures such as scope exhaustion or physical connectivity problems.
Frequently Asked Questions
What does an Autoconfiguration IPv4 Address mean?
Can a short DHCP lease cause APIPA?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
ERB14 👍 1 Answered CThe output shows an Autoconfiguration IPv4 Address of 169.254.0.5, which is an APIPA (Automatic Private IP Addressing) address. Windows assigns an APIPA address when a client device sends a request to a DHCP server but receives no response.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All N10-009 Questions
Access 100 questions with complete answers and detailed explanations.
View Full N10-009 Practice Test →