You have a failover cluster named Cluster1.
A virtual machine named VM1 is a highly available virtual machine that runs on Cluster1. A custom application
named App1 runs on VM1.
You need to configure monitoring on VM1. If App1 adds an error entry to the Application even log, VM1 should
be automatically rebooted and moved to another cluster node.
Which tool should you use?
A.
Resource Monitor
B.
Failover Cluster Manager
C.
Server Manager
D.
Hyper-V Manager
Explanation:
Do you have a large number of virtualized workloads in your cluster? Have you been looking for a solution that allows you to detect if any of the virtualized workloads in your cluster are behaving abnormally? Would you like the cluster service to take recovery actions when these workloads are in an unhealthy state? In Windows
Server 2012/2016, there is a great new feature, in Failover Clustering called “VM Monitoring”, which does exactly that – it allows you monitor the health state of applications that are running within a virtual machine andthen reports that to the host level so that it can take recovery actions.
VM Monitoring can be easily configured using the Failover Cluster Manager through the following steps:
Right click on the Virtual Machine role on which you want to configure monitoring
Select “More Actions” and then the “Configure Monitoring” options
You will then see a list of services that can be configured for monitoring using the Failover Cluster Manager.
References: https://blogs.msdn.microsoft.com/clustering/2012/04/18/how-to-configure-vm-monitoring-inwindows-server-2012/