When troubleshooting intermittent latency to a remote internal resource, CompTIA A+ recommends using tools that help identify where latency occurs and whether it is consistent or fluctuating over time. The best tools for this scenario are ping -t and tracert.
Ping -t (B) sends continuous ICMP echo requests, allowing the technician to observe packet loss, fluctuating response times, or timeouts. This helps identify intermittent connectivity problems that occur at specific times, such as bandwidth congestion, routing instability, or wireless interference.
Tracert (F) maps each hop between the local workstation and the remote office. If latency spikes occur only after a particular hop—such as a VPN tunnel, MPLS gateway, or inter-office router—that device becomes the suspected bottleneck. This makes tracert essential for isolating WAN-related slowdowns.
Ipconfig /all (A) only provides local configuration and does not diagnose latency. Nslookup (C) is for DNS testing—not latency to a specific internal host. Examining switchports (D) helps with local issues but not remote latency. QoS (E) is a solution, not a troubleshooting step. Calling ISP (G) may be premature unless testing confirms ISP-related issues.
Thus, ping -t and tracert are the correct diagnostic tools.
