A technician is troubleshooting a user's inability to access the internet. The user can ping the default gateway but cannot ping external websites. What is the most likely issue?
Pinging external sites by name fails if DNS is not resolving.
Why this answer
The user can ping the default gateway, which confirms that the local network configuration (IP address, subnet mask, and gateway) is correct and that Layer 3 connectivity to the router is working. However, pinging external websites fails because the DNS server is not configured or unreachable, preventing the resolution of domain names to IP addresses. This is a classic symptom: internal connectivity works, but name resolution fails.
Exam trap
The trap here is that candidates often assume a firewall is blocking traffic (Option A) when they see internet failure, but the ability to ping the gateway proves Layer 3 connectivity is intact, pointing instead to a DNS resolution issue.
How to eliminate wrong answers
Option A is wrong because if the firewall were blocking all outbound traffic, the ping to the external website's IP address would also fail, but the user can ping the default gateway, indicating outbound traffic is not entirely blocked. Option B is wrong because if the default gateway were down, the user could not ping it successfully; the gateway is reachable. Option C is wrong because if the IP address were misconfigured (e.g., wrong subnet or gateway), the user would not be able to ping the default gateway; successful gateway ping confirms correct IP configuration.