Why should disk I/O and page file utilization be used to identify bottlenecks?

While related to user volume, this option is too vague and does not specifically explain the technical reason for using disk I/O and page file utilization as an indicator for resource exhaustion leading to bottlenecks.

High disk I/O and page file utilization on the Delivery Controller indicates a problem with the controller's own performance, not a direct prediction that a target device will fail.

High disk I/O and page file utilization on a Delivery Controller suggests that the server is under severe memory pressure, causing it to constantly swap data between RAM and disk. This condition typically arises when the controller is attempting to manage a high number of concurrent user sessions or processing numerous operations, leading to resource exhaustion and degraded performance.

Although a virus could cause high disk I/O, it is not the primary or most common reason to monitor these metrics for identifying general performance bottlenecks in a typical VDI environment; resource exhaustion from legitimate workloads is more common.