A vSphere administrator is troubleshooting a performance issue on a cluster with vSphere DRS enabled. The administrator notices that all VMs are on the same host despite DRS being fully automated. What is the most probable cause?
Trap 1: DRS automation level is set to 'Manual'.
Incorrect. DRS is described as fully automated, so the automation level is not set to Manual.
Trap 2: The cluster has DRS set to manual mode.
Incorrect. DRS is set to fully automated, not manual mode.
Trap 3: The vMotion network is not configured.
Incorrect. While a missing vMotion network would prevent migrations, the question states DRS is fully automated, implying vMotion is configured and functional. The most probable cause is the threshold setting.
- A
DRS automation level is set to 'Manual'.
Why wrong: Incorrect. DRS is described as fully automated, so the automation level is not set to Manual.
- B
The host with all VMs has a higher DRS migration threshold.
Correct. A high DRS migration threshold (cluster-level) makes DRS conservative, causing it to avoid migrating VMs even when load is imbalanced. The phrasing in the option incorrectly suggests per-host, but the underlying concept is the cause.
- C
The cluster has DRS set to manual mode.
Why wrong: Incorrect. DRS is set to fully automated, not manual mode.
- D
The vMotion network is not configured.
Why wrong: Incorrect. While a missing vMotion network would prevent migrations, the question states DRS is fully automated, implying vMotion is configured and functional. The most probable cause is the threshold setting.