MENU
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?
Suggested Answer: C
Get Premium 2V0-16.25 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
29 comments · newest first
AN
Andrew
8 months ago
C is definitely the way to go. It handles both VM and storage.
RE
Reyes
8 months ago
D is not an option. We need to find a solution.
AN
Annabelle
8 months ago
B is too risky. We can't afford downtime.
DA
Daron
9 months ago
I thought you could only vMotion if the datastore is available.
PA
Paris
9 months ago
Option D is just not an option, we have to move it!
AL
Allene
9 months ago
Wait, can you really do that if the datastore isn’t there?
RA
Rachael
9 months ago
I agree, that’s the only way to avoid downtime.
ST
Stanford
9 months ago
You need to do a vMotion with Storage vMotion.
VE
Veronica
9 months ago
I’m leaning towards A, but I’m not entirely sure if that would work since the datastore issue complicates things.
JU
Justine
10 months ago
I think the answer might be C, but I’m a bit confused about how Storage vMotion works when the datastore isn't present.
CA
Carma
10 months ago
I remember practicing vMotion scenarios, but I'm not sure if Storage vMotion is necessary here since the datastore isn't available in the new cluster.
LI
Lili
10 months ago
I feel like A might work, but the datastore issue is a problem.
DE
Derick
10 months ago
Agreed! vMotion with Storage vMotion keeps it running.
NY
Nydia
10 months ago
This is tricky. I think C is the best option.
LO
Lorrine
11 months ago
I like C too. It’s efficient and meets the requirements.
RE
Renea
11 months ago
I feel like I’ve seen a question like this before, and I think vMotion with Storage vMotion could allow for the transfer without downtime.
MA
Marget
11 months ago
Hmm, I'd say C) is the way to go. Gotta love that fancy vMotion with Storage vMotion. Sounds like a real party trick!
LA
Lavera
11 months ago
C) Storage vMotion is the key here. Smooth migration without any downtime.
DE
Desirae
11 months ago
D) Inform the owner the VM cannot be moved to the new cluster. No datastore match, no can do!
PE
Percy
12 months ago
C) Definitely the way to go. Gotta love that Storage vMotion!
KA
Katy
12 months ago
C) Perform a vMotion with Storage vMotion to the new cluster.
HA
Harris
1 year ago
Ah, this is a good one. I'm pretty confident that C is the right answer here. The key is that we need to do the Storage vMotion along with the regular vMotion to move the VM without any downtime, since the datastore isn't available in the new cluster. Nice question!
HA
Harrison
1 year ago
Option D seems like the easiest choice, but I don't want to just give up on moving the VM. I'm leaning towards C, the vMotion with Storage vMotion, since that seems to address all the requirements. I'll double-check the details, but I think that's the best approach.
CA
Carlee
1 year ago
Hmm, this is a tricky one. I'm not sure if a regular vMotion will work since the datastore isn't available. Maybe option B, backing up and restoring, could be a solution, but that might cause some downtime. I'll have to think this through carefully.
SI
Silva
1 year ago
I think option C is the way to go here. Since the datastore isn't present in the destination cluster, we'll need to do a Storage vMotion along with the vMotion to move the VM without any downtime.
DI
Dick
7 months ago
Plus, the datastore issue makes C the only viable option.
YA
Yan
7 months ago
Right! Can't risk downtime for the owner.
AR
Armando
7 months ago
Definitely! Storage vMotion is essential here.
RO
Rodolfo
8 months ago
I agree, option C is the best choice. No downtime is crucial.