Why should CPU consumption be used to identify bottlenecks?

The Delivery Controller is responsible for brokering connections, authenticating users, and managing sessions. A high volume of user logons or ongoing session management tasks are processor-intensive, directly manifesting as high CPU utilization and indicating the controller is struggling to keep up.

High CPU on the Delivery Controller points to issues on the controller itself, not directly implying delays on a target device, although controller performance can indirectly affect end-user experience.

While high CPU can indicate processor-intensive tasks, option A provides a more specific and common scenario for a Delivery Controller in a VDI environment, specifically user logons.

While malware can cause high CPU, it's a less common and specific reason for general performance bottleneck analysis compared to the primary function of the Delivery Controller handling user logons.