Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

VMware Exam 1V0-21.20 Topic 7 Question 74 Discussion

Actual exam question for VMware's 1V0-21.20 exam
Question #: 74
Topic #: 7
[All 1V0-21.20 Questions]

An administrator wants to ensure that a copy of a virtual machine can

still power up on another data center during a disaster.

Which feature meets this requirement?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Rory
6 months ago
vSphere Replication? More like 'vSphere Relocation' am I right? *wink wink*
upvoted 0 times
Boris
5 months ago
A: Definitely, it's like a safety net for your virtual machines.
upvoted 0 times
...
Kiera
5 months ago
B: I agree, it ensures that a copy of the virtual machine can power up in another data center.
upvoted 0 times
...
Lili
6 months ago
A: Yeah, vSphere Replication is the way to go for disaster recovery.
upvoted 0 times
...
...
Shad
6 months ago
Hmm, Fault Tolerance might work, but it's more for protecting against individual host failures, not full-blown disasters. Replication is the way to go.
upvoted 0 times
...
Arlette
6 months ago
Nah, High Availability is more for keeping VMs running during host failures, not disasters. Gotta go with Replication on this one.
upvoted 0 times
Berry
5 months ago
High Availability won't help much during a disaster, Replication is the key.
upvoted 0 times
...
Becky
5 months ago
Yeah, Replication ensures that a copy of the VM is available in another data center.
upvoted 0 times
...
Anglea
5 months ago
Replication is definitely the way to go for disaster recovery.
upvoted 0 times
...
...
Madonna
6 months ago
I think vMotion would work too, since you can live migrate VMs between data centers.
upvoted 0 times
Marnie
5 months ago
A) vSphere Replication
upvoted 0 times
...
Santos
5 months ago
vMotion allows live migration of VMs between data centers.
upvoted 0 times
...
Linette
5 months ago
D) Fault Tolerance
upvoted 0 times
...
Carmen
5 months ago
C) vSphere High Availability
upvoted 0 times
...
Ryan
5 months ago
B) vMotion
upvoted 0 times
...
Evangelina
5 months ago
A) vSphere Replication
upvoted 0 times
...
Twanna
5 months ago
vMotion allows live migration of VMs between data centers.
upvoted 0 times
...
Nakisha
5 months ago
D) Fault Tolerance
upvoted 0 times
...
Marvel
5 months ago
C) vSphere High Availability
upvoted 0 times
...
Eileen
6 months ago
C) vSphere High Availability
upvoted 0 times
...
Devorah
6 months ago
B) vMotion
upvoted 0 times
...
Earlean
6 months ago
B) vMotion
upvoted 0 times
...
Mica
6 months ago
A) vSphere Replication
upvoted 0 times
...
Kaycee
6 months ago
A) vSphere Replication
upvoted 0 times
...
...
Tuyet
7 months ago
vSphere Replication, obviously! It's the only option that specifically mentions disaster recovery.
upvoted 0 times
Shelia
5 months ago
Agreed, vSphere Replication is the best choice for ensuring a copy of the virtual machine can power up in another data center during a disaster.
upvoted 0 times
...
Kenneth
5 months ago
A) vSphere Replication
upvoted 0 times
...
Olive
6 months ago
Fault Tolerance is more about continuous availability rather than disaster recovery.
upvoted 0 times
...
Mitsue
6 months ago
D) Fault Tolerance
upvoted 0 times
...
Chauncey
6 months ago
I think vSphere High Availability would also help in ensuring the virtual machine can power up in another data center during a disaster.
upvoted 0 times
...
Candida
6 months ago
C) vSphere High Availability
upvoted 0 times
...
Emilio
6 months ago
Definitely vSphere Replication, it's designed for disaster recovery.
upvoted 0 times
...
Stefania
6 months ago
A) vSphere Replication
upvoted 0 times
...
Yuki
6 months ago
Yes, vSphere Replication is designed for disaster recovery scenarios.
upvoted 0 times
...
Elke
6 months ago
A) vSphere Replication
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77