Loan officers at a bank say one internal page is slow, and a network test to that server shows a clean path. Which test should run next?
Select an answer to reveal the explanation.
Short Explanation
Timing a clear highway again will not show you why the crate at the dock is slow to open. You run a web test that loads the slow page and watch how its objects behave. Another path test, a name check, or a call-quality score does not open that page.
Full Explanation
The loan officers say one internal page is slow, and a network test to that server already shows a clean path. A web test loads the page and records how its objects behave, which is the measurement that can explain a slow page on a healthy path. Repeating the network test for loss and latency on a path that just came back clean spends another cycle on a result you already have. A DNS test of the hostname checks name resolution, and the page is opening, so the name is not the slowness the officers reported. A voice test scores call quality for phones, which are not the internal page the loan office is waiting on. Object timings on that page show whether a heavy object, or the way the page is built, explains the wait after the path has already tested clean. Exam caveat: a clean network test narrows the problem; it does not finish it when the remaining symptom is how the page itself loads. Operational check: load the slow page in a web test from the loan office and compare object behavior with the clean network test to the same server.