A vSAN administrator receives a request from the application team to create a virtual machine on a vSAN datastore. The requirements state that the virtual machine needs to be available quickly after a failure occurs. The solution must minimize administrative effort.
Which vSphere feature should the vSAN administrator implement?
vSphere High Availability (HA) is the most suitable feature for ensuring that a virtual machine is quickly available after a failure with minimal administrative effort. HA automatically restarts affected virtual machines on healthy hosts within the cluster in the event of a host failure, ensuring minimal downtime and quick recovery without requiring extensive manual intervention.
vSphere High Availability (HA) provides easy to use, cost effective high availability for applications running in virtual machines. In the event of server failure, affected virtual machines are automatically restarted on other production servers with spare capacity. The benefit is minimum downtime, hence quick recovery, without the need for constant manual intervention.
C FT is the right answer, there is not clear description of what sort of a failure, hence FT is right option here, that relying on HA to have the entire vm on another host all together, rather FT is more apt feature as it can tolerate failures and VM and data are still accessible effortlessly.
One more thing, the question is around the vsan administrator, so he apt for him to think and work with FT
B is correct
The correct answer is B, HA is activated per cluster and does not require more effort, while FT must be created a network and also configured in the VMs
B - if a host failure occurs the VM would restart on another host. This solution has the least administrative effort
C - FT correct , machine will reboot on other host
I've now had this discussion with my entire team. They all agree that the answer is in "as little administrative effort as possible". I also initially would chose FT and in my opinion it's not a lot of effort but never the less, it is more effort than just relying on HA. HA will restart the machines "quickly after a failure" as the question states.
One more thing, FT won't reboot the VM on another host, FT maintains a "clone" vm on another host and mirrors the memory state so that in the event of a failure, that VM will be available immediately without requiring a reboot of the guest os.