A retailer will configure ThousandEyes at the branches, and the complaint is jitter on a point-of-sale path. Which test should they configure?
Select an answer to reveal the explanation.
Short Explanation
Jitter on the point-of-sale path is a shaky road, not a wrong store name on the sign. You configure a ThousandEyes network test that measures jitter on that path. A name check, a public page load, or a test of the store phone system measures something other than that shake.
Full Explanation
The retailer will use ThousandEyes, and the complaint is jitter on a point-of-sale path, so the test to configure is a ThousandEyes network test that measures jitter on that path. A network test reports path metrics such as loss, latency, and jitter for the path under test, which is the complaint on the point-of-sale path. A DNS test of the point-of-sale name checks resolution and does not measure jitter on the path. A web test of the public retail home page times a public page and is not a measurement of the point-of-sale path. A voice test of the store phone system scores a call, and jitter on a phone call is a different service from jitter on the point-of-sale path. The exam trap is hearing jitter and selecting a voice test when the path that is unsteady belongs to point of sale. In production, place the ThousandEyes network test on the point-of-sale path and read jitter there, leaving the name, page, and phone tests for symptoms those tests cover. A green phone test does not clear jitter on the point-of-sale path, and a successful name lookup does not measure it either.