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



Leave a Reply 3

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


noname

noname

It must be D

https://technet.microsoft.com/en-us/library/dn265972.aspx

By default, cluster nodes exchange heartbeats every one second. The number of heartbeats that can be missed before failover occurs is known as the heartbeat threshold. In Windows Server 2012 R2, the default heartbeat threshold has been increased for Hyper-V failover clusters.

I can’t find the actual screen where they would show this option

den

den

all I could find, too…but isn’t this affecting the file services also? If so, then how would you “ensure that Server1 remains the active node for the File Services clustered resource for up to five missed heartbeat messages”??

JeanMalot

JeanMalot

It would affect both roles.
Configuring different thresholds per role on a failover cluster is just not possible.

I guess the question has been wrongly transcripted.