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.

Cluster1 hosts an application named App1.

You need to ensure that Server2 handles all of the client requests to the cluster for App1. The solution must ensure that if Server2 fails, Server1 becomes the active node for App1.

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 u
F . The Handling priority
G . The host priority
H . Live migration
. The possible owner
. The preferred owner
. Quick migration
. The Scale-Out File Server

View Answer

Answer: J

Explanation:

The preferred owner in a 2 server cluster will always be the active node unless it is down. http://

www.sqlservercentral.com/Forums/Topic1174454-146-1.aspx#bm1174835

Difference between possible owners and preferred owners Possible owners are defined at the resource level and dictate which nodes in the Windows cluster are able to service this resource For instance, you have a 3 node cluster with Node A, Node B and Node C. You have a clustered disk resource "MyClusteredDisk", if you remove Node C from the possible owners of the clustered disk resource "MyClusteredDisk" then this disk will never be failed over to Node C. Preferred owners are defined at the resource group level and define the preferred node ownership within the Windows cluster For instance, you have a 3 node cluster with Node A, Node B and Node C. You have a cluster resource group "MyClusteredGroup" which contains various disk, IP, network name and service resources. Nodes A, B and C are all possible owners but Node B is set as the preferred owner and is currently the active node. The resource group fails over to Node C as Node B stops responding on the Public network due to a failed NIC. In the Resource group properties on the failback tab you have this set to immediate. You fix the NIC issue on Node B and bring it back up on the network. The resource group currently active on Node C will without warning immediately attempt to failback to Node B. Not a good idea if this is a Production SQL Server instance, so use caution when configuring preferred owners and failback http://support.microsoft.com/kb/299631/en-us

Failover behavior on clusters of three or more nodes

This article documents the logic by which groups fail from one node to another when there are 3 or more cluster node members. The movement of a group can be caused by an administrator who manually moves a group or by a node or resource failure. Where the group moves depends on how the move is initiated and whether the Preferred Owner list is set.