You need to fail over VM1 automatically to a different node when a service named Service1 on VM1 fails. What should you do? To answer, select the appropriate options in the answer area.

This question tests your knowledge of Hyper-V VM Monitoring within Windows Server Failover Clustering (WSFC), specifically how to trigger automatic VM failover based on a service failure inside the guest OS.

Implement and manage Windows Server high availability

Question

You need to fail over VM1 automatically to a different node when a service named Service1 on VM1 fails. What should you do? To answer, select the appropriate options in the answer area.

Explanation

Approach. The correct approach is to configure VM Monitoring on the clustered VM resource. In Failover Cluster Manager, right-click VM1 and select 'More Actions > Configure Monitoring', then add Service1 as a monitored service. Alternatively, use the PowerShell cmdlet: Add-ClusterVMMonitoredItem -VirtualMachine VM1 -Service Service1. Once configured, if Service1 stops and cannot be restarted within the cluster's retry policy, the cluster will automatically fail over VM1 to another node. This requires the Failover Clustering feature and Hyper-V to be installed, VM1 to already be a clustered role, and the Hyper-V Guest Services integration component to be enabled inside VM1 so the host can communicate with the guest.

Concept tested. Hyper-V VM Monitoring (Add-ClusterVMMonitoredItem) within Windows Server Failover Clustering - enabling automatic guest-service-triggered VM failover without relying solely on host-level health checks.

Reference. Microsoft Docs: 'Virtual Machine Health and Recovery in Failover Clustering' - covers Add-ClusterVMMonitoredItem and Failover Cluster Manager VM Monitoring configuration.

Topics

#Failover Clustering#Hyper-V Clustered VMs#Service Monitoring#Automatic Failover

Community Discussion

No community discussion yet for this question.

Full AZ-801 Practice