You are a network administrator for your company. The network contains four Windows Server 2003 computers configured as a four-node server cluster.
Each cluster node is the preferred owner of a clustered instance of Microsoft SQL Server 2000, and each cluster node is configured as a possible owner of all other instances of SQL Server.
All nodes have identically configured hardware. All four nodes operate at a sustained 70 percent CPU average. You add a server that has identically configured hardware to the cluster as a fifth node. You want each SQL Server instance to continue operating at the same level of performance in the event of a single node failure.
What should you do?
A.
Clear the Affect group check box in the cluster resource properties for each SQL Server instance.
B.
Configure the fifth node as the only possible owner other than the existing preferred owner of the cluster resources that are associated with each SQL Server instance.
C.
Configure the fifth node as the preferred owner of each cluster group that contains an SQL Server instance.
D.
Enable failback on each group that contains an SQL Server instance.
Explanation:
Clustering is intended for organizations running applications that must be available, making any server downtime unacceptable. In a server cluster, each computer is running the same critical applications, so that if one server fails, the others detect the failure and take over at a moment’s notice. This is called failover. In the question it is mentioned that a fifth node is added. The other four nodes are each configured as preferred owner. Thus if you configure the added node as the only possible other that are associated with each SQL Serer instance, then each SQL Server instance will continue at the same level of performance in case a single node fails.Reference:
http://support.microsoft.com/default.aspx?scid=kb;en-us;296799&Product=winsvr2003
Craig Zacker, MCSE Self-Paced Training Kit (Exam 70-293): Planning and Maintaining a Microsoft Windows Server 2003 Network Infrastructure, Microsoft Press, Redmond, Washington, 2004, p. 7: