vSphere Performance and Scaling →easyMultiple ChoiceObjective-mapped

VCP-DCV vSphere Performance and Scaling Practice Question

Exhibit

Log file snippet:

2025-03-01T10:15:23.456Z cpu10:VMKB: vm2: vcpu-0: CPU ready time: 3000ms (3.0%)
2025-03-01T10:15:23.456Z cpu10:VMKB: vm2: vcpu-1: CPU ready time: 2800ms (2.8%)
2025-03-01T10:15:23.456Z cpu10:VMKB: vm2: vcpu-2: CPU ready time: 3100ms (3.1%)
2025-03-01T10:15:23.456Z cpu10:VMKB: vm2: vcpu-3: CPU ready time: 2900ms (2.9%)

Refer to the exhibit. The administrator is troubleshooting performance for VM 'vm2'. Based on the log, what is the performance issue?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The VM is not experiencing significant CPU performance issues

The CPU ready time values (around 3%) are within acceptable thresholds (typically under 5%). There is no indication of contention or overcommitment.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The host is overloaded with too many VMs
Why it's wrong here
Low ready time suggests the host is not overloaded.
✓
The VM is not experiencing significant CPU performance issues
Why this is correct
Ready time below 5% is normal; no issue.
✗
The VM is experiencing high CPU ready time indicating starvation
Why it's wrong here
3% is low and acceptable, not indicating starvation.
✗
The VM has a memory balloon driver issue
Why it's wrong here
The log only shows CPU ready time, not memory metrics.

Go deeper

VCP-DCV vSphere Performance and Scaling Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question