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:
http://social.technet.microsoft.com/Forums/en/operationsmanagergeneral/thread/6b6acdf3e921-
4c9f-b496-cd81f556d246
all I could find:
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
but I miss the point how to configure it the way that these two cluster roles would behave differently:
– DHCP should move over when 2 heartbeats are missed
– File Services should move over after 5 missed heartbeats
So, who would you configure these different settings per role instead described settings for the whole cluster?
0
0
My best choice isn’t listed at all. Each resouce is based on a resource type. There is a DHCP resource type and a File Server resource type. You can manipulate the “LooksAlive” and “IsAlive” settings per resource type. If a resource misses the “IsAlive” check, it is considered failed.
This woul give the option to differentiate per resource type.
http://blogs.msdn.com/b/clustering/archive/2013/01/24/10388009.aspx
0
0