An administrator wants to ensure that VMs running latency-sensitive applications are placed on hosts that minimize CPU scheduling delays. Which DRS setting should be configured?
Trap 1: Set DRS migration threshold to the most aggressive setting.
Setting the DRS migration threshold to the most aggressive level is not recommended because it causes frequent vMotions, increasing overhead and potentially causing more scheduling delays.
Trap 2: Enable Distributed Power Management (DPM).
DPM is designed for power savings and can cause delays when hosts are powered on or off, making it unsuitable for latency-sensitive workloads.
Trap 3: Enable Enhanced vMotion Compatibility (EVC).
EVC ensures CPU compatibility across hosts but does not directly address CPU scheduling delays.
- A
Set DRS migration threshold to the most aggressive setting.
Why wrong: Setting the DRS migration threshold to the most aggressive level is not recommended because it causes frequent vMotions, increasing overhead and potentially causing more scheduling delays.
- B
Enable vSphere HA with admission control.
This is correct because HA with admission control reserves capacity, ensuring that VMs have dedicated resources, which minimizes CPU scheduling delays.
- C
Enable Distributed Power Management (DPM).
Why wrong: DPM is designed for power savings and can cause delays when hosts are powered on or off, making it unsuitable for latency-sensitive workloads.
- D
Enable Enhanced vMotion Compatibility (EVC).
Why wrong: EVC ensures CPU compatibility across hosts but does not directly address CPU scheduling delays.