Match each network symptom described on the left with its most likely root cause on the right.
- A workstation receives an IP address starting with 169.254.50.12 and cannot access external internet resources.DHCP server unreachability leading to Automatic Private IP Addressing (APIPA)
- A user can successfully ping an external IP address (8.8.8.8) but receives a host unreachable error when attempting to ping www.comptia.org.DNS server misconfiguration or failure to resolve domain names
- A wireless client experiences severe latency and dropped packets in an office suite where adjacent access points are all set to 2.4 GHz Channel 3.Wireless co-channel / adjacent-channel interference
- A wired desktop reports no network connection, and the Ethernet port LED link indicators on the back of the PC remain completely unlit.Physical layer fault such as a disconnected or damaged patch cable
Answer
169.254.x.x IP matches DHCP unreachability (APIPA); Ping by IP working but domain name failing matches DNS misconfiguration; 2.4 GHz Channel 3 usage matches channel interference; Unlit NIC link lights match physical layer cable fault.
Each symptom maps directly to standard networking layer troubleshooting principles: APIPA (169.254.x.x) signals DHCP unreachability; successful IP communication with failed FQDN resolution indicates DNS failure; 2.4 GHz Channel 3 causes wireless interference; and completely unlit NIC LEDs confirm a Layer 1 physical link failure.
Step-by-Step Solution
Key Concept
Wired and Wireless Network Troubleshooting Symptoms and Diagnoses