Exam NCA-7.5 Topic 1 Question 59 Discussion

CPU Ready measures the time during which a virtual CPU is ready to execute but cannot be scheduled on a physical CPU. Increasing CPU Ready while the VM's actual CPU usage remains unchanged indicates that the workload wants processor time but the hypervisor cannot schedule it promptly. This most commonly points to host CPU contention, oversubscription, or effectively exhausted CPU scheduling capacity.
This condition is not evidence that the VM lacks assigned vCPUs. Adding more vCPUs can make the problem worse because the hypervisor may have greater difficulty scheduling a larger virtual CPU configuration. The administrator should examine host CPU utilization, physical-core availability, CPU overcommitment, NUMA alignment, VM sizing, other high-demand VMs, and any CPU limits or affinity constraints.
Memory exhaustion produces different indicators, including swapping, ballooning, or elevated memory wait behavior. A full disk would affect storage capacity and possibly I/O latency but would not directly create CPU Ready time.
The wording "host CPU resources are exhausted" should be understood as unavailable or heavily contended physical scheduling capacity, not necessarily that every processor reports exactly 100% utilization. CPU Ready measures scheduling delay and can reveal contention that VM CPU usage alone does not expose.
NHCF/NCA reference: VM performance metrics, CPU contention, and troubleshooting resource constraints.
Official references: Interpreting CPU Ready Values , CPU Ready Time , and Prism Alert Metrics .