Yournetwork 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.
Youconfigure File Services and DHCP as clustered resources for Cluster1. Server1 is the active node
for both clustered resources.
Youneed 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:
The number of heartbeats that can be missed before failover occurs is known as the heartbeat
threshold. Heartbeat threshold is failover clustering setting.
Tuning Failover Cluster Network Thresholds
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
for someone who doesn’t do much with Failover Clusters on one hand but do much via GUI tools on the other hand, then this question is tricky because the setting is only to set with command line respective Powershell command. Trying to modify heartbeat threshold via Failover Cluster Manager won’t work as no options available…
0
0
Correct. This is very tricky and advanced.
from Microsoft blog:
“Cluster heartbeat configuration settings are considered advanced settings which are only exposed via PowerShell. These setting can be set while the cluster is up and running with no downtime and will take effect immediately with no need to reboot or restart the cluster.”
0
0