A beverage company has a critical virtual machine running on vsphere . The virtual machine runs an application that controls the customer automatic botting line. An outage of this virtual machines…

Grigory K.Jun 10, 2026

B and C, Fault Tolerance and High Availability. Those are your two answers and here is why they both fit. FT runs a live shadow VM on a second host in lockstep with the primary. If the ESXi host dies, the shadow takes over instantly, zero downtime, zero data loss. That is exactly what you want when your app cannot do its own clustering and a stopped bottling line means someone is writing big checks. HA is a step below FT in terms of RTO but it still belongs here because it automatically restarts protected VMs on surviving hosts after a host failure, no admin has to log in at 2 AM and manually vMotion anything. vShield Endpoint is a security offload feature for antivirus, it has nothing to do with availability. Cross-vCenter vMotion lets you migrate a running VM between vCenter instances, which is useful for maintenance windows and migrations but it does nothing automatically when a host crashes. Neither of those two belongs anywhere near a downtime-reduction conversation.

Grace U.Jun 21, 2026

The correct answers are B and C, and they work together beautifully for exactly this kind of scenario. Fault Tolerance keeps a live shadow copy of the VM running in lockstep on a second host, so if the primary host dies the secondary takes over instantly with zero data loss, which is exactly what you want for an application that cannot cluster on its own. High Availability covers you at the cluster level by automatically restarting the VM on another host after a failure, which is a slightly longer recovery but still far better than a manual intervention, and together these two give you layered protection without requiring any changes to that old application.

Orla P.Jun 23, 2026

Saw this exact scenario on my attempt last spring and the trick they are going for is that Cross-vCenter vMotion moves a VM while it is running but does nothing to restart it after a host dies, and vShield Endpoint is a security feature, so you cross those off fast and land on Fault Tolerance for zero-interruption protection and High Availability for the automatic restart after host failure. B and C is the right call, full stop.

Anjali D.Jun 5, 2026

This exact scenario came up on my exam and I almost second-guessed myself on C because I kept thinking HA just restarts the VM on another host, which still means some downtime, but then I remembered that is exactly what the question is asking about, reducing downtime, not eliminating it, so HA fits. Fault Tolerance was the easy pick since it keeps a shadow VM running in lockstep so there is zero interruption, which is perfect for an app that cannot cluster on its own. Anyone else find themselves overthinking HA here, or was it a clear B and C for you from the start?

Yelena W.Jun 11, 2026

Both B and C are right here. Fault Tolerance gives you zero-downtime protection by keeping a shadow VM in lockstep with the primary, which is exactly what you need for an app that cannot cluster at the application layer, and High Availability covers the restart side so that if the ESXi host dies and FT somehow cannot sustain, the VM gets restarted on another host automatically with minimal manual intervention.

Bao N.Jun 19, 2026

Yep, B and C is the right call here. Fault Tolerance keeps a shadow VM in lockstep so there is literally zero downtime if the host dies, and High Availability restarts the VM automatically on another host within minutes, which covers the case where FT overhead is too much for the workload.

Jelena G.Jun 26, 2026

Cross-vCenter vMotion moves the VM live, zero downtime, pick D.