What should you configure on the virtual machine?

Your network contains an Active Directory domain named contoso.com. The domain
contains two member servers named Server1 and Server2. All servers run Windows Server
2012 R2.
Server1 and Server2 are nodes in a Hyper-V cluster named Cluster1. Cluster1 hosts 10
virtual machines. All of the virtual machines run Windows Server 2012 R2 and are members
of the domain.
You need to ensure that the first time a service named Service1 fails on a virtual machine,
the virtual machine is moved to a different node.
You configure Service1 to be monitored from Failover Cluster Manager.
What should you configure on the virtual machine?

Your network contains an Active Directory domain named contoso.com. The domain
contains two member servers named Server1 and Server2. All servers run Windows Server
2012 R2.
Server1 and Server2 are nodes in a Hyper-V cluster named Cluster1. Cluster1 hosts 10
virtual machines. All of the virtual machines run Windows Server 2012 R2 and are members
of the domain.
You need to ensure that the first time a service named Service1 fails on a virtual machine,
the virtual machine is moved to a different node.
You configure Service1 to be monitored from Failover Cluster Manager.
What should you configure on the virtual machine?

A.
From the General settings, modify the Startup type.

B.
From the General settings, modify the Service status.

C.
From the Recovery settings of Service1, set the First failure recovery action to Take No
Action.

D.
From the Recovery settings of Service1, set the First failure recovery action to Restart the
Service.

Explanation:
Configure the virtual machine to take no action through Hyper-V if the physical computer
shuts down by modifying the Automatic Stop Action setting to None. Virtual machine state
must be managed through the Failover Clustering feature.
Virtual machine application monitoring and management
In clusters running Windows Server 2012, administrators can monitor services on clustered
virtual machines that are also running Windows Server 2012. This functionality extends the
high-level monitoring of virtual machines that is implemented in Windows Server 2008 R2
failover clusters. If a monitored service in a virtual machine fails, the service can be
restarted, or the clustered virtual machine can be restarted or moved to another node
(depending on service restart settings and cluster failover settings).
This feature increases the uptime of high availability services that are running on virtual
machines within a failover cluster.
Windows Server 2012 Failover Cluster introduces a new capability for Hyper-V virtual
machines (VMs), which is a basic monitoring of a service within the VM which causes the
VM to be rebooted should the monitored service fail three times. For this feature to work the
following must be configured:
Both the Hyper-V servers must be Windows Server 2012 and the guest OS running in theVM
must be Windows Server 2012.
The host and guest OSs are in the same or at least trusting domains.
The Failover Cluster administrator must be a member of the local administrator’s group
inside the VM.
Ensure the service being monitored is set to Take No Action (see screen shot below) within
the guest VM for Subsequent failures (which is used after the first and second failures) and
is set via the Recovery tab of the service properties within the Services application (services. msc).

Within the guest VM, ensure the Virtual Machine Monitoring firewall exception is enabled for
the Domain network by using the Windows Firewall with Advanced Security application or by

using the Windows PowerShell command below: Set-NetFirewallRule -DisplayGroup “Virtual
Machine Monitoring” -Enabled True
After the above is true, enabling the monitoring is a simple process:
1. Launch the Failover Cluster Manager tool.
2. Navigate to the cluster – Roles.
3. Right click on the virtual machine role you wish to enable monitoring for and under
More Actions select Configure Monitoring. . .

4. The services running inside the VM will be gathered and check the box for the
services that should be monitored and click OK.

You are done!
Monitoring can also be enabled using the Add-ClusterVMMonitoredItemcmdlet and VirtualMachine, with the -Service parameters, as the example below shows: PS
C:\Windows\system32> Add-ClusterVMMonitoredItem -VirtualMachine savdaltst01 -Service
spooler
http: //sportstoday. us/technology/windows-server-2012—continuous-availability-%28part-
4%29—failover-clustering-enhancements—virtual-machine-monitoring-. aspx
http: //windowsitpro. com/windows-server-2012/enable-windows-server-2012-failovercluster-hyper-v-vm-monitoring
http: //technet. microsoft. com/en-us/library/cc742396. aspx



Leave a Reply 12

Your email address will not be published. Required fields are marked *


Pirulo

Pirulo

Is this for the 70-411 ?

ward

ward

Yes ofcourse ..

larry

larry

this came up in my 70-412 exam today, fucking BS. got 696/700
These new exams are a fucking joke.

MJG

MJG

WTF? You got this on 412… but its also on 411?

Saad

Saad

I believe it is C

Ex

Ex

You configure Service1 to be monitored from Failover Cluster Manager.
So VM Monitoring was configured.

If Properties of service > Recovery tab :
First failure : Restart the service
Second failure : Restart the service
Subsequent failure : Take no Action

Then :
When a monitored service encounters an unexpected failure, the sequence of recovery actions is
determined by the Recovery actions on failure for the service. These recovery actions can be
viewed and configured using Service Control Manager inside the guest. In the example below, on
the first and second service failures, the service control manager will restart the service.
On the third failure, the service control manager will take no action and defer recovery actions to
the cluster service running in the host.

More info : http://blogs.msdn.com/b/clustering/archive/2012/04/18/10295158.aspx

Correct answer is : C.

Ex

Ex

Additional info :
Recovery action is taken on the virtual machine in “Application Critical” state

a. The virtual machine is first restarted on the same node

Note: The restart of the virtual machine is forced but graceful

b. On the second failure, the virtual machine restarted and failed over to another node in the cluster.

Note: The decision on whether to failover or restart on the same node is configurable and determined by the failover properties for the virtual machine.

Gilbert

Gilbert

This is not a 70-411 question.

Jeff

Jeff

Why do you say that Gilbert?

Alex

Alex

Because someone said it appeared on his 70-412 exam/

a.l.i

a.l.i

Failover is not in 411, indeed. it is in 412