2V0-622D · Question #276
A vSphere Administrator has VM Component Protection (VMCP) enabled, but the VM was not restarted when one of the VMFS datastores experienced an All Paths Down (APD) failure. What two scenarios would e
The correct answer is A. Insufficient Capacity is available on the failover ESXi hosts. D. The APD failure was corrected before the VM could be restarted.. VMCP will not restart a VM during an APD event if there are insufficient cluster resources to accommodate the VM on another host, or if the APD condition resolves itself before the restart timeout expires.
Question
A vSphere Administrator has VM Component Protection (VMCP) enabled, but the VM was not restarted when one of the VMFS datastores experienced an All Paths Down (APD) failure. What two scenarios would explain why the virtual machine was not restarted? (Choose two.)
Options
- AInsufficient Capacity is available on the failover ESXi hosts.
- BVM Monitoring is required in order for VMCP to failover during an APD event.
- CVMware Tools is not installed on the guest operating system for the VM.
- DThe APD failure was corrected before the VM could be restarted.
How the community answered
(51 responses)- A49% (25)
- B35% (18)
- C16% (8)
Why each option
VMCP will not restart a VM during an APD event if there are insufficient cluster resources to accommodate the VM on another host, or if the APD condition resolves itself before the restart timeout expires.
VMCP relies on vSphere HA to restart affected VMs on other hosts in the cluster, but if no ESXi host has sufficient CPU, memory, or storage resources available to power on the VM, the restart attempt will fail and the VM will remain offline.
VM Monitoring is a separate vSphere HA feature that monitors guest heartbeats and is entirely independent of VMCP - VMCP detects storage path failures at the ESXi layer and can trigger restarts without VM Monitoring being configured or enabled.
VMware Tools installation in the guest OS is not a prerequisite for VMCP operation - VMCP monitors storage path state at the ESXi hypervisor level and does not rely on any guest OS agents or VMware Tools to detect APD or PDL conditions.
VMCP uses a configurable timeout delay before triggering a VM restart during APD conditions - if storage paths are restored and the APD failure is corrected before this timeout elapses, VMCP cancels the pending restart because recovery has already occurred naturally.
Concept tested: VM Component Protection APD restart conditions and limitations
Source: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-availability/GUID-F01F7EB8-FF9D-45E2-A093-5F56A788D027.html
Topics
Community Discussion
No community discussion yet for this question.