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. Server1 and Server2 have the Failover Clustering feature installed.
The servers are configured as nodes in a failover cluster named Cluster1.
You configure File Services and DHCP as clustered resources for Cluster1.
Server1 is the active node for both clustered resources.
You need to ensure that if two consecutive heartbeat messages are missed between Server1 and Server2,
Server2 will begin responding to DHCP requests.
The solution must ensure that Server1 remains the active node for the File Services clustered resourcefor up
to five missed heartbeat messages.
What should you configure?
A.
Affinity – None
B.
Affinity – Single
C.
The cluster quorum settings
D.
The failover settings
E.
A file server for general use
F.
The Handling priority
G.
The host priority
H.
Live migration
I.
The possible owner
J.
The preferred owner
K.
Quick migration
L.
The Scale-Out File Server
Explanation:
well on the internet, we can only find aboutcluster.exeCLI to confugre tolerance to heartbeat failures
however, i found ONE page (waw) where the guy says to check the “failover settings” to troubleshoot heartbeat
alert problems…
i know it’s not an evidence, but that’s the only thing i could find… and at least it’s not a rebuttal evidence !
and if you check explanations of the other questions with the same answer choices (where almost every
answers are explained), by a process of elimination, you can be sure it’s the correct answer.
==========
http://social.technet.microsoft.com/Forums/en/operationsmanagergeneral/thread/6b6acdf3-e921-4c9f-b496-cd81f556d246
Answered Agent Failover Set…Still Getting Heartbeat Alerts
[…]
Hi,
Please see the methods in the following post are helpful:
[…]
Meanwhile, please also verify the failover settings:
Powershell Commands to configure Gateway Server / Agent Failover