nerdexam
CompTIA

220-1101 · Question #228

A user reports limited or no connectivity on a laptop. A technician runs ipconfig /all with the following result: IPv4 connectivity...limited or none IPv4 address...169.254.254.1 subnet mask...255.255

The correct answer is A. DHCP failure. The IPv4 address 169.254.254.1 is an Automatic Private IP Addressing (APIPA) address, which is self-assigned when a device fails to obtain an IP address from a DHCP server.

Hardware and network troubleshooting

Question

A user reports limited or no connectivity on a laptop. A technician runs ipconfig /all with the following result:

IPv4 connectivity...limited or none IPv4 address...169.254.254.1 subnet mask...255.255.0.0 default gateway... Which of the following is the MOST likely cause of this issue?

Options

  • ADHCP failure
  • BARP cache
  • CDNS resolution
  • DDuplicate IP address

How the community answered

(55 responses)
  • A
    73% (40)
  • B
    7% (4)
  • C
    16% (9)
  • D
    4% (2)

Why each option

The IPv4 address 169.254.254.1 is an Automatic Private IP Addressing (APIPA) address, which is self-assigned when a device fails to obtain an IP address from a DHCP server.

ADHCP failureCorrect

An IP address in the 169.254.0.0/16 range (APIPA address) is automatically assigned by Windows when a DHCP server is unavailable or fails to provide an IP address. The absence of a default gateway also points to a DHCP server not providing network configuration.

BARP cache

ARP cache issues typically manifest as problems reaching specific devices on the local network despite having a valid IP configuration, rather than a lack of an IP address and connectivity.

CDNS resolution

DNS resolution problems occur when a device has a valid IP address but cannot translate domain names to IP addresses, which is not the primary issue described by the APIPA address.

DDuplicate IP address

A duplicate IP address would usually result in an error message indicating the conflict, and while it could cause connectivity issues, the 169.254.x.x address explicitly points to a DHCP failure.

Concept tested: APIPA address interpretation and DHCP troubleshooting

Source: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/description-of-apipa

Topics

#DHCP#APIPA#IP configuration#Network troubleshooting

Community Discussion

No community discussion yet for this question.

Full 220-1101 Practice