Witch two statements are true about High Priority vMotion requests in vSphere 5.x?

Witch two statements are true about High Priority vMotion requests in vSphere 5.x?

(Choose two)

Witch two statements are true about High Priority vMotion requests in vSphere 5.x?

(Choose two)

A.
Migrations always proceed regardless of whether or not resources have been successfully

B.
Migrations do not proceed if resources are not successfully reserved.

C.
vCenter Server attempts to reserve resources on both the source and destination hosts to be shared among all concurrent migrations with vMotions.

D.
vCenter Server attempts to reserve resources on both the source and destinations hosts for each individual High Priority migration with vMotion.

Explanation:
Page 135 from vsphere-esxi-vcenter-server-50-host-management-guide.pdf



Leave a Reply 1

Your email address will not be published. Required fields are marked *


foreignbishop

foreignbishop

DO NOT be tricked by this question. High priority vMotion was defined differently with ESX3.x.