Which command helps identify where a network path is failing?

Which command helps identify where a network path is failing?

• A. traceroute
• B. ping
• C. ipconfig
• D. nslookup

Answer: (A)

The key thing tested here is identifying the exact point in the network path where communication breaks down. Traceroute reveals the route your packets take to a destination by sending probes that elicit responses from each hop along the way. Each reply shows which router or device handled the packet, so you can see where progress stops or slows. If a hop doesn’t respond or shows unusually high latency, you’ve pinpointed where the path may be failing or encountering problems. Do keep in mind that some devices block ICMP responses, which can lead to timeouts that don’t necessarily mean the path is broken, just that those devices aren’t replying. Ping, by contrast, checks whether a destination is reachable and measures round-trip time to that single endpoint, but it doesn’t map the route. Ipconfig shows your own machine’s network configuration (IP address, gateway, DNS, etc.), not the path to a remote host. Nslookup asks DNS servers to resolve domain names to IPs, also not diagnosing the route. If you’re trying to diagnose path issues, traceroute is the tool that provides the route and where it fails. On Windows, the equivalent command is tracert, but the concept is the same.

The key thing tested here is identifying the exact point in the network path where communication breaks down. Traceroute reveals the route your packets take to a destination by sending probes that elicit responses from each hop along the way. Each reply shows which router or device handled the packet, so you can see where progress stops or slows. If a hop doesn’t respond or shows unusually high latency, you’ve pinpointed where the path may be failing or encountering problems. Do keep in mind that some devices block ICMP responses, which can lead to timeouts that don’t necessarily mean the path is broken, just that those devices aren’t replying.

Ping, by contrast, checks whether a destination is reachable and measures round-trip time to that single endpoint, but it doesn’t map the route. Ipconfig shows your own machine’s network configuration (IP address, gateway, DNS, etc.), not the path to a remote host. Nslookup asks DNS servers to resolve domain names to IPs, also not diagnosing the route. If you’re trying to diagnose path issues, traceroute is the tool that provides the route and where it fails. On Windows, the equivalent command is tracert, but the concept is the same.