2V0-622 · Question #485
How can a vSphere administrator ensure that two virtual machines never run on the same datastore in a datastore cluster, while permitting the VMs to be load-balanced?
The correct answer is B. Configure a storage DRS VM override. Storage DRS VM overrides allow per-VM customization of placement behavior within a datastore cluster, enabling separation of specific VMs while load balancing remains active.
Question
How can a vSphere administrator ensure that two virtual machines never run on the same datastore in a datastore cluster, while permitting the VMs to be load-balanced?
Options
- AUse an Intra-VM Anti-Affinity Rule.
- BConfigure a storage DRS VM override.
- CDisable storage DRS for the VMs.
- DUse an Inter-VM Anti-Affinity Rule.
How the community answered
(22 responses)- A5% (1)
- B68% (15)
- C9% (2)
- D18% (4)
Why each option
Storage DRS VM overrides allow per-VM customization of placement behavior within a datastore cluster, enabling separation of specific VMs while load balancing remains active.
An Intra-VM Anti-Affinity Rule applies to virtual disk files within a single VM, keeping that VM's VMDKs on different datastores - it does not govern placement of two separate VMs relative to each other.
A Storage DRS VM override lets an administrator configure individual VM placement settings within a datastore cluster, including keeping specific VMs on different datastores, without disabling SDRS automation for those VMs. This approach ensures the two VMs do not share a datastore while still allowing SDRS to perform load-balancing operations across the cluster.
Disabling Storage DRS for the VMs removes all automated load balancing and placement management for those VMs, which directly contradicts the requirement to permit load balancing.
An Inter-VM Anti-Affinity Rule prevents two VMs from sharing a datastore but is a hard constraint that can conflict with or restrict SDRS load-balancing flexibility compared to a VM override configuration.
Concept tested: Storage DRS VM override for per-VM placement rules
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-3F1DFF43-AC3B-4D30-AAD5-38B9613AFCE2.html
Topics
Community Discussion
No community discussion yet for this question.