At a retailer with branch stores, store laptops reach the inventory application until the VPN client connects, and then only those VPN sessions fail. Which test matches the failure?
Select an answer to reveal the explanation.
Short Explanation
The headset that crackles only after you put it on is a problem at your ear, not at the tower. Run an Endpoint Agent test on the laptop that fails once the VPN client connects. A data-center Enterprise Agent, a cloud DNS test, or a page load that never runs on that laptop misses the moment the client path breaks.
Full Explanation
The inventory application is reachable until the VPN client connects, and the failure is limited to those VPN sessions on the store laptops. An Endpoint Agent test on the laptop that fails after the VPN connects stands on the device where the client starts and can see the experience after that connection. An Enterprise Agent test running only inside the data center measures from a probe that does not run the store VPN client, so it misses the change that creates the failure. A DNS test started from a cloud probe far from the store laptop asks how a name looks from the cloud, which is neither the laptop nor the moment the VPN client connects. A page-load test that never executes on the laptop using the VPN client can load the inventory page from somewhere else and will not reproduce the session that fails. Exam caveat: a failure that begins when the user client connects is an endpoint condition even if the application itself is healthy from the data center. Operational check: run the Endpoint Agent test on a store laptop, capture one attempt before the VPN client connects and one after, and confirm the break appears only on the after attempt.