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 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 resource for 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:
A) The number of heartbeats that can be missed before failover occurs is known as the
heartbeat threshold
http://technet.microsoft.com/en-us/library/dn265972.aspx
http://technet.microsoft.com/en-us/library/dd197562(v=ws.10).aspx
http://blogs.msdn.com/b/clustering/archive/2012/11/21/10370765.aspx
Not sure this scenario is possible as I don’t believe you can set a threshold per role, only per cluster. For example the only command I can find provided on TechNet for missed heartbeats would be:
(get-cluster).SameSubnetThreshold = 2
http://blogs.msdn.com/b/clustering/archive/2012/11/21/10370765.aspx
D. It is the only option that makes some sense
I don’t get how you can 2 different threshholds : 2 missed heartbeats for DHCP, and 5 for 5 for File Server.
Can anyone explain ?
You configure this setting in the individual roles, so you can have different settings per role.
ok, but how??
the described command to change heartbeat config is:
cluster /cluster: /prop SameSubnetThreshold=
I don’t find anything like how to define a target role to configure individually…?!
D – failover settings is the only place you can specify number of missed heartbeats
When I go to the Failover tab of a cluster role properties window (only failover options I could find) then the description says “Specify the number of times the Cluster service will attempt to restart or fail over the clustered role in the specified period. If the clustered role fails more than the maximum in the specified period, it will be left in the failed state.” Further there are fallback settings…
So, what does this have to do with role specific heartbeat settings?
i am pretty sure the answer supplied is correct. here is why:
once you configure the failover cluster you then assign the roles to the cluster nodes. In the failover cluster manager, select the roles node and click configure role and its specific props.
so it is possible to configure individual failover settings for specific roles.
I havent tried this in my lab though
u can change the node who will receive the role in case of failover and heartbeats
You definitely cannot configure different thresholds per role, only per subnet type (cross-subnet or same-subnet). And you do it via powershell, not from the failover settings.
Failover settings will let you specify the number of failures in a time period that the cluster will attempt to fail over, it has nothing to do with heartbeats or thresholds.
so D is 100% wrong.
Fact is, none of the other answers makes sense, neither.
https://social.technet.microsoft.com/Forums/exchange/en-US/96bfe139-a46c-426a-be62-c7d5b1a33d67/anyone-can-help-me-to-answer-this-question?forum=winserverClustering
I saw this question in my exam yesterday. So there is no problem in this question because they are still asking it in the exams.