Question

Difficulty: Very hardIP Addressing and Network Configuration

A network technician is diagnosing workstation configuration and connectivity issues across different network segments. Match each observed host diagnostic symptom on the left with its underlying network configuration root cause on the right.

  • A workstation receives an IP address of 169.254.10.45 and can only communicate with hosts on the local link.The DHCP server is unreachable or offline, resulting in automatic APIPA self-assignment.
  • A host successfully pings 8.8.8.8 but fails to reach www.comptia.org using a web browser.The DNS server address is missing, unreachable, or improperly configured on the host.
  • A client device can communicate with neighboring devices on 192.168.1.0/24 but cannot reach any external subnets.The default gateway IP address is misconfigured or missing from the network interface settings.
  • A workstation displays an IP address of fe80::211:22ff:fe33:4455 and communicates locally without a DHCP server.The host automatically generated an IPv6 link-local address for local segment communications.

Answer

Matching pairs: (1) 169.254.10.45 address matches unreachable DHCP server resulting in APIPA; (2) Ping 8.8.8.8 success with browser URL failure matches missing or misconfigured DNS server; (3) Local subnet communication success with remote subnet failure matches misconfigured default gateway; (4) fe80:: address matches IPv6 link-local auto-configuration.
Each diagnostic symptom maps precisely to IP protocol principles: APIPA (169.254.x.x) indicates DHCP timeout; domain-name-only failure isolates DNS misconfiguration; inability to leave the local subnet indicates a missing/invalid default gateway; and fe80:: prefixes represent standard self-configured IPv6 link-local addresses.

Step-by-Step Solution

1
Diagnose APIPA behavior
Recognize 169.254.x.x as the IPv4 APIPA block self-assigned when DHCP discovery times out.
APIPA allows basic local communication when dynamic addressing fails.
2
Diagnose name resolution vs network layer routing
Identify that raw IP pings succeed while hostname lookups fail, pointing directly to DNS misconfiguration.
DNS is responsible for translating human-readable hostnames into IP addresses; IP routing works independently of DNS.
3
Diagnose inter-subnet routing requirements
Determine that local communication works via ARP but remote routing fails due to a missing or invalid default gateway.
The default gateway is the exit point for packets directed to destinations outside the local subnet mask.
4
Diagnose IPv6 link-local addressing
Identify fe80::/10 as the mandatory self-generated IPv6 unicast address scope for link-local traffic.
IPv6 nodes auto-generate link-local addresses independently without requiring stateful DHCP services.

Key Concept

IP Addressing, Default Gateways, DNS Resolution, APIPA, and IPv6 Link-Local auto-configuration
Estimated Time:3m 0s
Rate this question