You have five servers that run Windows Server 2012 R2. The servers have the Failover
Clustering feature installed.
You deploy a new cluster named Cluster1. Cluster1 is configured as shown in the following table.
Server1, Server2/ and Server3 are configured as the preferred owners of the cluster roles.
Dynamic quorum management is disabled.
You plan to perform hardware maintenance on Server3.
You need to ensure that if the WAN link between Site1 and Site2 fails while you are
performing maintenance on Server3, the cluster resource will remain available in Site1.
What should you do?
A.
Remove the node vote for Server3.
B.
Enable DrainOnShutdown on Cluster1.
C.
Add a file share witness in Site1.
D.
Remove the node vote for Server4 and Server5.
Answer: pending
I think is
D. Remove the node vote for Server4 and Server5.
Agree with D
The correct answer is D. Remove the node vote for Server4 and Server5.
Because suppose you add a file share witness in Site1 and during the maintenance the file share witness and either Server1 or Server2 failed at the same time then the clients at Site2 will start accessing Server4 and Server5 which is contrary to the question requirements.
You need to keep the clients in both sites accessing cluster resource in Site1 and if the WAN link failed then any client should not access cluster resources in Site2 because cluster resources in Site1 are the preferred owners.
D
This ability to control whether a cluster resource has a vote or not is not limited to the witness. Starting in Windows Server 2012 (and back ported to Windows Server 2008/2008 R2) the concept of the cluster property “nodeweight” was introduced. By setting a cluster nodes nodeweight=0, you are able to remove the voting rights of any cluster node. This is ideal in multisite cluster configurations where a large number of cluster nodes might reside in a different data center. In that case a failure of a WAN link may cause you to lose quorum, bringing down the remaining nodes in your primary data center. However, if you took the votes away from the nodes in your DR site they would not be able to impact the availability of your cluster nodes in your primary data center.
I believe it’s C
As a general rule when you configure a quorum, the voting elements in the cluster should be an odd number. Therefore, if the cluster contains an even number of voting nodes, you should configure a disk witness or a file share witness. The cluster will be able to sustain one additional node down. In addition, adding a witness vote enables the cluster to continue running if half the cluster nodes simultaneously go down or are disconnected.
info found here: https://technet.microsoft.com/en-us/library/jj612870.aspx
I’m leaning towards C also.
C. Why remove the votes from the nodes in Site2 if the WAN Link fails? It’s about the nodes in site 1, dynamic quorum is disabled and recommended number of votes should be odd. So configure a fileshare witness.
Answer is D. in the link posted by noname on February 9, 2015 @ 10.20am
https://technet.microsoft.com/en-us/library/jj612870.aspx
see the Node vote assignment section. it particularly mentions multisite and DR scenarios
Then again this link suggests it’s C.
https://technet.microsoft.com/en-us/library/jj612870.aspx#BKMK_disaster
Quorum considerations for DR configurations. I give up. Don’t know the answer
After reading comments and Technet, I think the answer needs to be C File Share Witness.
As a general rule when you configure a quorum, the voting elements in the cluster should be an odd number. Therefore, if the cluster contains an even number of voting nodes, you should configure a disk witness or a file share witness. The cluster will be able to sustain one additional node down. In addition, adding a witness vote enables the cluster to continue running if half the cluster nodes simultaneously go down or are disconnected.
It’s D.
I think is C. Witness Share may be in HA. If you remove the votes of Server4 & 5 then is Server 3 goes into maintenance then there is not quorum
I think C is the correct answer. With a Witness share in site 1, in the case thet wan link goes down, the cluster will remain operative.
The details talked about in the write-up are a few of the top readily available.