AZ-801 · Question #167
You have a Hyper-V failover cluster named Cluster1. Cluster1 contains a virtual machine named VM1 that runs Windows Server. VM1 contains a Windows service named Service1. You need to ensure that Clust
This question tests knowledge of Hyper-V Virtual Machine Monitoring in a Windows Server Failover Cluster, specifically how to make the cluster react to a Windows service failure inside a guest VM, not just a VM crash.
Question
Explanation
This question tests knowledge of Hyper-V Virtual Machine Monitoring in a Windows Server Failover Cluster, specifically how to make the cluster react to a Windows service failure inside a guest VM, not just a VM crash.
Approach. The correct approach is to configure VM Monitoring on VM1 and add Service1 to the list of monitored services. This is done using the PowerShell cmdlet 'Add-ClusterVMMonitoredItem -VirtualMachine VM1 -Service Service1', or equivalently through Failover Cluster Manager by right-clicking VM1 > More Actions > Configure Monitoring and selecting Service1. VM Monitoring uses Hyper-V integration services (specifically the guest heartbeat) to detect service failures inside the VM and trigger a configurable cluster recovery action - such as restarting the VM on the same node or failing it over to another node - without requiring the VM itself to crash first.
Concept tested. Hyper-V Virtual Machine (VM) Monitoring in Windows Server Failover Clustering - specifically the ability to monitor Windows services running inside a clustered guest VM and trigger cluster-level recovery actions (restart or live migration) when those services fail, using Add-ClusterVMMonitoredItem or Failover Cluster Manager.
Reference. https://learn.microsoft.com/en-us/windows-server/failover-clustering/health-service-overview - also 'Add-ClusterVMMonitoredItem' in Microsoft Docs
Topics
Community Discussion
No community discussion yet for this question.