2V0-621 · Question #194
How does vSphere High Availability calculate the memory slot size of a virtual machine?
The correct answer is A. Virtual machine memory reservation + overhead of largest virtual machine. vSphere HA computes the memory slot size as the VM memory reservation plus the memory overhead of the largest VM, ensuring any VM can fail over to any host.
Question
How does vSphere High Availability calculate the memory slot size of a virtual machine?
Options
- AVirtual machine memory reservation + overhead of largest virtual machine
- BVirtual machine memory reservation - overhead of largest virtual machine
- CVirtual machine memory reservation + overhead of smallest virtual machine
- DVirtual machine memory reservation - overhead of smallest virtual machine
How the community answered
(38 responses)- A92% (35)
- B5% (2)
- C3% (1)
Why each option
vSphere HA computes the memory slot size as the VM memory reservation plus the memory overhead of the largest VM, ensuring any VM can fail over to any host.
In vSphere HA slot-based admission control, the memory slot size is the sum of the highest VM memory reservation across all VMs plus the memory overhead associated with the largest VM. This combination ensures the slot is large enough to accommodate the worst-case scenario of restarting the most demanding VM on any available host in the cluster.
Subtracting the overhead would underestimate the required slot size because memory overhead is an additional cost on top of the reservation, not something to be removed from it.
Using the smallest VM overhead would produce a slot size insufficient for restarting the largest VM, because the overhead of the largest VM may be significantly greater.
Subtracting the smallest VM overhead is incorrect on two counts - overhead must be added, not subtracted, and the largest VM overhead must be used to guarantee failover capacity.
Concept tested: vSphere HA admission control slot size calculation
Source: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-availability/GUID-85D9D829-5049-4144-8193-9C8161E7E1FB.html
Topics
Community Discussion
No community discussion yet for this question.