Q: 4
A virtual machine (VM) owner has requested to move a VM from one cluster to another. The
following information has been provided:
The VM cannot have downtime during the transfer.
The same network is present on both clusters.
The datastore that the VM is currently on is not present in the destination cluster.
What step should the administrator perform to move the VM?
Options
Discussion
Saw something like this on a practice exam and picked A.
A or B. I saw something similar in practice questions and the official cert guide so maybe review those resources.
Probably C, since a normal vMotion (A) needs shared storage and the question says the datastore isn’t present in the new cluster. C combines compute and storage migration with no downtime, which is what’s needed here. Easy to trip up if you forget about that storage limitation, I think.
B , since restoring from backup could also move the VM, though there would be some downtime. A is a trap here.
Option C
No shared datastore, so you need Storage vMotion along with vMotion to keep the VM running.
Makes sense here, has to be C since there's no shared storage between clusters and zero downtime is needed.
C imo. Regular vMotion (A) won't work since there's no shared datastore between clusters. Storage vMotion is required to move both compute and storage live. Did see some folks confuse this with plain vMotion, easy trap.
C, Storage vMotion covers both the compute and storage move with zero downtime, so that's what fits this scenario.
If the datastore isn’t available on the destination, vMotion alone (A) won’t work since it needs shared storage. Storage vMotion handles both compute and storage changes with no downtime. Pretty sure C is best here, but open to correction!
I don’t think A works since vMotion alone needs shared storage, which isn’t available here. Pretty sure C is correct because Storage vMotion lets you move both compute and storage with no downtime. Option B is tempting but has downtime.
Be respectful. No spam.
