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?

A. Perform a vMotion of the VM to the new cluster.

B. Backup the VM and restore it to the new cluster.

D. Inform the owner the VM cannot be moved to the new cluster.

Broadcom-VMware

2V0-16.25 · Question #3

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…

The correct answer is C. Perform a vMotion with Storage vMotion to the new cluster. Option C is correct because the scenario requires zero downtime while also migrating the VM to a datastore not shared between clusters - this is precisely the use case for a combined vMotion + Storage vMotion operation, which simultaneously live-migrates the VM's compute (to…

Section 4 – Manage VMware vSphere Foundation Compute

Question

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

APerform a vMotion of the VM to the new cluster.
BBackup the VM and restore it to the new cluster.
CPerform a vMotion with Storage vMotion to the new cluster.
DInform the owner the VM cannot be moved to the new cluster.

How the community answered

(49 responses)

A
2% (1)
B
8% (4)
C
78% (38)
D
12% (6)

Explanation

Option C is correct because the scenario requires zero downtime while also migrating the VM to a datastore not shared between clusters - this is precisely the use case for a combined vMotion + Storage vMotion operation, which simultaneously live-migrates the VM's compute (to the new cluster/host) and its storage (to a new datastore), all while the VM remains running.

Why the distractors fail:

A (vMotion only): Standard vMotion requires the VM's datastore to be accessible from the destination host. Since the datastore is absent in the destination cluster, this migration would fail outright.
B (Backup/Restore): This introduces downtime - the VM must be powered off or suspended to back up - directly violating the stated requirement.
D (Cannot be moved): Incorrect; the combined migration addresses all constraints: no downtime, same network present, and storage migration to a new datastore.

Memory tip: Think of it as a two-axis move - host axis (vMotion) + storage axis (Storage vMotion). Whenever the destination cluster lacks shared storage, you need both axes moving at once. If you only have one constraint to solve, use the matching tool; if you have both, combine them.

Topics

#vMotion#Storage vMotion#VM Migration#Cluster Management

Community Discussion

No community discussion yet for this question.

Full 2V0-16.25 Practice