vSphere Performance and Scaling →hardMultiple SelectObjective-mapped

VCP-DCV vSphere Performance and Scaling Practice Question

Which THREE factors should be considered when sizing a host cluster for a VDI environment with 1000 desktops? (Choose three.)

⚠ Common exam trap

Candidates often confuse operational features (like vMotion compatibility) with true capacity-sizing factors, or they mistakenly think NUMA alignment is a sizing input rather than a post-deployment optimization.

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

✓

Storage IOPS capacity for boot storms.

Storage IOPS capacity for boot storms is critical because when 1000 desktops boot simultaneously (e.g., at start of shift), they generate a massive burst of read I/O. If the storage array cannot handle the peak IOPS, desktops will experience slow boot times or timeouts. Proper sizing must account for both steady-state IOPS and the boot storm peak, often using flash storage or caching to absorb the load.

Answer analysis

Option-by-option breakdown

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

✗
vMotion compatibility between hosts.
Why it's wrong here
Incorrect: Important for maintenance but not a sizing factor.
✗
NUMA alignment of virtual desktops.
Why it's wrong here
Incorrect: Typically desktops have few vCPUs, so NUMA is less critical.
✓
Storage IOPS capacity for boot storms.
Why this is correct
Correct: Boot storms can saturate storage; IOPS must be sufficient.
✓
vCPU-to-core ratio to prevent CPU contention.
Why this is correct
Correct: Overcommitment leads to poor performance.
✓
Memory overcommitment ratio and available memory per host.
Why this is correct
Correct: Memory is often the limiting factor in VDI.

Go deeper

VCP-DCV vSphere Performance and Scaling Practice Question

Why each option matters

Option-by-option breakdown

Related to this question