Match each network troubleshooting scenario on the left with its most likely underlying cause on the right.
- A workstation auto-assigns an IP address of 169.254.42.108 and cannot access network shares or the internet.DHCP server unreachability resulting in an APIPA address
- A wireless client in a dense office setup experiences high packet loss and latency despite full Wi-Fi signal indicator.Wi-Fi co-channel interference and frequency overlap
- An Ethernet connection experiences extreme interference and data corruption when running adjacent to high-voltage fluorescent lighting.Electromagnetic interference (EMI) on unshielded cabling
- A computer can ping external IP addresses (e.g., 1.1.1.1) successfully but cannot load web pages using standard domain names.DNS server failure or local misconfiguration
Answer
The troubleshooting scenarios correctly match as follows: receiving a 169.254.x.x address indicates DHCP server unreachability (APIPA); Wi-Fi packet loss despite strong signal indicates channel interference; cable degradation near high-voltage lighting indicates EMI; and successful IP pings alongside failed domain navigation indicates DNS failure.
Each diagnostic symptom directly corresponds to a specific failure mode: 169.254.x.x addresses signify DHCP failure; degraded Wi-Fi with high signal strength signifies channel overlap; signal degradation near electrical fixtures signifies EMI; and successful IP connectivity with domain failures signifies DNS breakdown.
Step-by-Step Solution
Key Concept
Diagnosing common wired and wireless symptoms and identifying their root network causes.