When troubleshooting performance and latency issues on BIG-IP, especially under peak load conditions, it is critical to identify which Virtual Servers are consuming the most resources . This is a core data plane analysis task .
BIG-IP provides multiple views of configuration and status, but only certain areas expose real-time and historical traffic statistics that correlate directly with CPU usage and throughput.
Why Option C Is Correct:
Statistics > Module Statistics > Local Traffic > Virtual Servers provides:
Real-time and cumulative statistics per Virtual Server
Metrics such as:
Bits in / Bits out
Packets in / Packets out
Current connections
Connection rate
Total requests
The ability to identify high-traffic or high-connection Virtual Servers , which are the most likely contributors to elevated CPU utilization
These statistics allow the administrator to objectively determine which Virtual Servers are the top consumers of system resources and therefore good candidates for migration to a dedicated BIG-IP device.
Why the Other Options Are Incorrect:
A. Local Traffic > Virtual Servers > Virtual Server List
Primarily a configuration view
Does not provide sufficient performance or utilization statistics to identify CPU-heavy Virtual Servers
B. System > Platform
Displays hardware-level information such as CPU cores, memory, disk, and platform type
Does not break down utilization by Virtual Server
D. Local Traffic > Network Map
Provides a logical topology view of Virtual Servers, pools, and pool members
Useful for understanding relationships, but not for identifying high-utilization Virtual Servers
Key Data Plane Concept Reinforced:
To diagnose performance problems and plan traffic redistribution, BIG-IP administrators must rely on Module and object-level statistics , not configuration screens. The Virtual Server statistics view is the authoritative location for identifying traffic hotspots that directly impact CPU and latency during peak events such as Black Friday.
===========
Submit