You have two servers that run Windows Server 2008 R2 Enterprise. Both servers have the Failover
Clustering feature installed. You configure the servers as a two-node cluster. The cluster nodes are
named NODE1 and NODE2. You have an application named PrintService that includes a print spooler
resource. You need to configure the cluster to automatically return the PrintService application to
NODE1 after a failover. Which two actions should you perform? (Each correct answer presents part
of the solution. Choose two.)
A.
Set the Period (hours) option to 0 in the properties of the print spooler resource.
B.
Move NODE1 to the top of the list of preferred owners for the PrintService application.
C.
Enable the Allow Failback and Immediate options for the PrintService application.
D.
Disable the If restart is unsuccessful, failover all resources in this server or application option in
the properties of the print spooler resource.
Explanation:
Preferred nodes list defined
If you define a complete preferred nodes list for a group (that is, one listing all the nodes in the
cluster), then the Cluster service uses this defined list as its internal list. However, if you define a
partial preferred nodes list for a group, then the Cluster service uses this defined
list as its internal list and appends any other installed nodes not on the preferred list, ordered by
their node IDs. For example, if you created a 5-node cluster (installing the nodes in the order Node1,
Node2, Node3, Node4, and Node5) and defined Node3, Node4, and Node5 as preferred owners for
the resource group, PRINTGR1, the Cluster service would maintain this ordered list for PRINTGR1:
Node3, Node4, Node5, Node1, Node2. How the Cluster service uses this list depends on whether the
resource group move is due to a resource/node failure or a manual move group request.
Preferred lists and resource or node failures
For resource group or node failures, the group fails over to the node next to the current owner on
the preferred nodes list. In the example above, if the resource group PRINTGR1 on Node3 fails, then
the Cluster service would fail that group over to the next node on the
list, Node4. If you allow failback for that group, then when Node3 comes up again, the Cluster
service will fail back PRINTGR1 to that node.
Source: http://technet.microsoft.com/en-us/library/cc737785.aspx