Why should memory and network utilization be used to identify bottlenecks?

High memory utilization on a Delivery Controller can be caused by maintaining numerous active user sessions and their associated data. Additionally, high network utilization reflects the traffic generated by managing these connections, both pointing to a large volume of user activity and indicating the Delivery Controller is under heavy load.

High memory and network utilization on the Delivery Controller primarily relate to its own load from managing users, not directly indicating delays on a target device.

"Processor-intensive tasks" would more directly relate to high CPU utilization, not primarily high memory and network utilization, although memory is involved in all tasks.

While a virus could cause high utilization, it is a less common and less specific indicator for general bottleneck analysis compared to the primary function of a Delivery Controller handling user load.