Home » VMware » VCP550D » Which configuration option should the VMware administrator use to resolve this issue?
A VMware administrator determines that a low priority virtual machine is negatively affecting the disk I/O performance of a higher priority virtual machine.
The virtual machines are hosted on the same datastore presented to the same ESXi host.
Which configuration option should the VMware administrator use to resolve this issue?
A. Increase the disk share value for the high priority VM.
B. Migrate the low priority VM to another ESXi host.
C. Create a Storage Profile for each priority level.
D. Enable vSphere APIs for Array Integration (VAAI).
Correct Answer: A
Explanation/Reference:
Explanation:
A: Disk share are used to distinguish between high-priority and low priority virtual machines. These disk share value represents the relative metric that controls the disk bandwidth to all the virtual machines on a host/server. Since the disk share values are compared to the sum of all shares of all the virtual machines on a particular host/server you should increase the disk share value for the high priority virtual machine to troubleshoot the performance issue caused by the low priority virtual machine.
Incorrect Answers:
B: Migrating the low priority virtual machine to another host will not resolve the issues since the virtual machines are hosted on the same datastore presented to the same ESXi host.
C: Storage profiles allow for the ability to streamline the storage provisioning process and for the VMware administrator to mass scale the storage within the environment. The storage profile will not address the issue of the low priority VM negatively affecting the performance of the high priority virtual machine. And since all the virtual machines are hosted on the same datastore presented to the same host configuring a storage profile for each priority level will not solve the issue.
D: VAAI is used to integrate the block storage arrays to benefit from array hardware operations and this option will not resolve the issue since all the virtual machines are hosted on the same datastore that is presented to the same host.
References:
https://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.vsphere.vm_admin.doc/GUID-61F43364-AA74-4944-A996-F09C5BB59E0D.html