Which of the following is NOT a goal of using RUM?

Using Real User Monitoring (RUM) primarily focuses on understanding how actual end users experience a web application. Its main goals include improving user experience by providing insights into how users interact with the application, identifying performance bottlenecks through the analysis of user sessions, and troubleshooting application performance based on real-world data and interaction patterns.

Improving user experience is achieved by analyzing metrics such as page load times, session duration, and interaction rates, which can guide you in making design and performance improvements. Troubleshooting application performance involves examining the user's perspective to diagnose issues that might not be evident through server-side monitoring alone. Testing application load times is also part of RUM's capabilities, as it directly measures how quickly users can load and interact with application pages in real environments.

Monitoring backend server health, however, is not a goal of RUM. This function is typically served by other monitoring tools and strategies focused on the server-side infrastructure, rather than the user-facing aspects of the application. Such monitoring emphasizes metrics like CPU usage, memory utilization, or server response times, which are essential for maintaining the health of the infrastructure but do not directly address the user experience or performance from the user's perspective.