What should you configure?

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?

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:
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



Leave a Reply 4

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


MalotJean

MalotJean

I’m really dying to know what the actual answer to this question is.
You can’t set thresholds from the “Failover” tab, and even if you do it in powershell, you can’t set them differently for two roles on the same node.

So failover settings is wrong. But so are all the other answers.

kurt

kurt

you can set individual properties per role on the failover tab. the “maximum failures int eh specified period” can be altered. this is the closest answer.

Gilbert

Gilbert

I agreed with Kurt, set “Maximum Failures in the specified pediod:” 2 for DHCP cluster role and 5 for File Services cluster role.

kurt

kurt

sometimes the questions are a little wrong in this forum. i cannot see any other way to adjust the heartbeat settings for a role. for a cluster it is below:
(get-cluster).SameSubnetThreshold = 20