1V0-621 · Question #237
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…
The correct answer is B. Fault tolerance C. High availability. See the full explanation below for the reasoning.
Question
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 stops the line and results in enormous costs for the business. The application is extremely old and does not support application level clustering . Which two vsphere features help reduce downtime for this critical virtual machine in case of esxi host failure? choose two )
Options
- AVshield endpoint
- BFault tolerance
- CHigh availability
- DCross-v center vmotion
How the community answered
(43 responses)- A14% (6)
- B79% (34)
- D7% (3)
Community Discussion
5
Kavya H.Jan 12, 2026B and C are your answers, Fault Tolerance and High Availability, because FT keeps a shadow VM running in lockstep so there is literally zero interruption if the host dies, while HA restarts the VM automatically on another host in the cluster when a failure is detected, which covers you when the app cannot do its own clustering. vShield Endpoint is a security offload feature and Cross-vCenter vMotion is a live migration tool, neither one protects you from an unplanned host failure.
Luis F.Jan 13, 2026Solid breakdown, I'd just add that FT also comes with the CPU/memory overhead caveat so in practice a lot of shops actually lean on HA for most workloads and only bust out FT for the truly mission-critical stuff where even a 30-second restart is unacceptable.
Luis F.Jan 30, 2026Fault Tolerance and High Availability are your two picks here, and I remember staring at this exact type of question on my exam thinking "wait, does vMotion count?" but no, Cross-vCenter vMotion just moves a running VM, it does not protect against host failure. The old app with no clustering support is the hint that FT is perfect since it keeps a shadow VM ready to take over instantly, while HA restarts the VM on another host if the primary goes down.
Kavya H.Jan 31, 2026Good breakdown, though worth flagging that FT does carry a meaningful performance overhead from continuous vLockstep replication, so if that legacy app is already CPU-sensitive you may actually feel it in session responsiveness even before you hit a failure event.
Brenda K.Jan 22, 2026Honestly my first instinct was to pick D because Cross-vCenter vMotion sounds like it moves workloads around to keep them safe, but that is a migration tool, not a protection tool. It moves VMs between vCenter instances on demand, it does not automatically respond to a host failure. What locked it in for me was the phrase "application does not support clustering," which is the exact scenario Fault Tolerance was built for, it mirrors the VM on a second host in lockstep so if the primary ESXi host dies there is zero data loss and essentially zero downtime. High Availability pairs with it perfectly here because HA restarts VMs on surviving hosts automatically when a host fails, so even if FT is not licensed everywhere, HA is your safety net that kicks in without any manual intervention. On the clock, this one reads fast once you key on that clustering limitation sentence, flag it only if the FT versus HA distinction is tripping you up, otherwise mark B and C and move on.