MENU
An architect needs to measure end-user experience for internal web applications and SaaS products.20 Which ThousandEyes agent should be deployed for this purpose?
In the context of Designing and Implementing Enterprise Network Assurance (300-445 ENNA), measuring the 'lived experience' of an end-user requires data collection from the actual device being used to access the services. Unlike server-side or infrastructure-side monitoring, user experience (UX) monitoring must account for local variables like Wi-Fi signal quality, CPU/memory usage, and browser-level pe21rformance.
The Endpoint Agent (Option D) is the correct choice for this architecture. It is a lightweight software service installed directly on Windows or macOS workstations, as well as RoomOS devices. The Endpoint Agent provides a dual-monitoring approach: Real User Monitoring (RUM) and Scheduled Synthetic Tests.24 RUM captures actual browser sessions to SaaS (e.g., Salesforce, Microsoft 365) or internal apps, providing a 'Experience Score' and a detailed waterfall view of page load components.25 Simultaneously, the agent can run background synthetic network tests to measure latency and path visualization from the user's specific location, whether they are in a branch office, at home on a VPN, or in a coffee shop.
Comparing other agents:
Enterprise Agents (Option B) can simulate a user at a branch office, but they cannot provide insight into the specific health of an individual's laptop or their unique Wi-Fi environment.
Cloud Agents (Option C) are entirely outside the user's network and cannot measure the performance of internal web applications or the 'last mile' connectivity of the employee.
Synthetic Agent (Option A) remains a distractor term.
By deploying Endpoint Agents, the architect ensures they have granular, contextual data that correlates application performance directly with the user's device and local network environment.