At a logistics hub, a shipping application fails only when the laptop proxy is on the path, while data-center probes reach the application without that proxy. Which test should the team run?
Select an answer to reveal the explanation.
Short Explanation
A flat tire in the driveway will not show up on a traffic camera downtown. You run an Endpoint Agent test on the laptop, because the failing proxy sits on that user device. A data-center Enterprise Agent, a cloud DNS probe, or a page load that stays off the laptop is looking in the wrong place.
Full Explanation
The shipping application fails only when traffic passes through the proxy configured on the laptop, and probes placed in the data center reach the application without that proxy. An Endpoint Agent test on the laptop is the measurement that includes the failing proxy, because the agent runs on the user device and follows the path that device actually takes. An Enterprise Agent in the data center that reaches the shipping application without the laptop proxy repeats the test that already succeeds and cannot see the proxy policy on the laptop. A DNS test from a cloud probe that resolves the shipping name off the affected laptop checks a resolver the laptop is not using, so a clean lookup there does not explain an application failure tied to the local proxy. A page-load test that runs on a hub server and does not run on the affected laptop likewise skips the device where the proxy is applied. Exam caveat: a successful test from a central probe does not clear a failure that depends on software present only on the endpoint. Operational check: on an affected laptop, confirm the endpoint test traverses the same proxy as the shipping application, and confirm a data-center probe does not.