Which two scenarios would cause a Fault Tolerance-enabled virtual machine to fail to power the Secondary virtual machine? (Choose two.)

A network-partitioned state breaks the required network communication channel between the Primary and Secondary FT VMs, making it impossible for the Secondary to synchronize state with and successfully power on alongside the Primary.

vSphere FT has a hard dependency on vSphere HA being enabled on the cluster - without HA, the FT framework that manages Secondary VM placement, heartbeat monitoring, and failover orchestration cannot operate, so the Secondary VM will not power on.

Enhanced vMotion Compatibility (EVC) normalizes CPU instruction sets across hosts to enable cross-host migrations; it does not block FT Secondary VM power-on and is actually beneficial for FT in mixed-CPU clusters.

While DPM can power down underutilized hosts, its presence on the cluster does not inherently prevent FT from powering on a Secondary VM - FT and DPM can coexist, though FT VMs are excluded from DPM standby consideration.