A government agency sees a public forms page where one embedded object is slow, while path metrics to the same host stay in their usual range. Which test fits the symptom?
Select an answer to reveal the explanation.
Short Explanation
The truck showed up on time, and one crate inside it was late. You use a web test when a single object on the page is slow and the path to that host looks normal. A path probe, a name check, or a call test measures a layer this symptom has not implicated.
Full Explanation
A slow embedded object, with path metrics to the same host still in their usual range, is a page problem, and a web test times the page and the objects on it. The route is not the symptom the agency reported, so a test that reports only path metrics will agree the path looks normal and still miss the slow object. A network test focused on loss, latency, and jitter covers the path question that the existing metrics have already described. A DNS test against the public resolvers checks name lookup, and a slow object after the page has loaded is not a resolution failure. A voice test places a call through the contact center and does not time an object on a forms page. The exam trap is hearing the word slow and selecting a latency test after the path metrics have already been ruled out. In production, compare object timing from a web test of that forms page with the path metrics toward the same host, and confirm the delay sits in the object. Leave the network, DNS, and voice tests for symptoms that name loss, a bad name, or a failed call.