Which two vSphere features enable remote site availability? (Choose two.)
Which two vSphere features enable remote site availability? (Choose two.)
Proactive High Availability (HA) ensures that virtual machines remain running by proactively detecting hardware issues and initiating the migration of virtual machines away from hosts that might fail, which in turn contributes to remote site availability by minimizing downtime. vSphere Replication is specifically designed for disaster recovery, enabling asynchronous replication of virtual machines to remote sites, thereby ensuring that data and services can be quickly restored in the event of a site failure. These two features directly support the concept of maintaining operation continuity and availability at a remote site.
AE is correct both are a wide site disaster recovery. it's very tricky question, I see guys comments speak about different answers which is confusing. I think everyone agree on E which is vSphere replication. FT is a VM settings on cluster level. it could be used to avail one VM, but question is speak about whole site availability and I think it's not logic to us FT for each VM! in case cluster is stretched!. Cross vCenter Migration as a term it include VMotion hot as well as cold migration so it's on demand it's not say when site A is down it will allow you to move to site 2 on one task. It says vmotion and not Xvmotion and even if the term meaning to use it's to vmotion between two vcenters which isn't automated.
C & E Either Cross vCentre vMotion or vSphere Replication would allow the VMs to move to a different site.
Migration is not the same as Availability. If the site goes down, you don't have time to log on and trigger a VMotion.
The correct answer is CE.
No, cross vCenter migration is something that needs to be engaged while both vcenter instances are online. It is for the migration of vms from one vcenter instance to another. It has nothing to do with availability. A and E are the correct answers.
A & E Passed today with 500/500 (9/3/23)
A AND E Cross vCenter Migration is not availability but has to be manually actioned.
E and B are correct. The question is about remote site availability. Pro active HA does not provide that. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-3E3B18CC-8574-46FA-9170-CF549B8E55B8.html This is not vCenter HA. The only two feauters are FT and Replication. So B&E
AE is right Remote Site Availability is not an use case for Cross vCenter Migration
AE is right Remote Site Availability is not a use case for Cross vCenter Migration https://core.vmware.com/resource/introducing-advanced-cross-vcenter-server-vmotion-capability#section3
CE is the correct
Cross vCenter vMotion and vSphere Replication would allow the VMs to move to a different site
that's what I thought first too. but for HA you want your VMs to be replicated beforehand and just restarted at the other site.
What is the correct answer?
b & d came first to mind
A & E As the question asks specifically "enable" remote site availability. vMotion performs migrations, it doesn't enable availability. vSphere vMotion enables zero-downtime, live migration of workloads from one server to another so your users can continue to access the systems they need to stay productive.
C is NOT the correct answer. A and E is correct.
If 1 answer is needed, I choose answer E. If 2 answers are needed, then 1 choose answer C & E
AE is correct C is not automate
The key here is "Availability." the only services considered DR/HA services are Proactive HA <- High Availability and vSphere Replication <- remote Availability.
C & E from a guy who got 500/500 - vSphere Features == Cross vCenter Migration & vSphere Replication