DRAG DROP
Your network contains an Active Directory domain named contoso.com. The domain contains four
member servers named Server1, Server2, Server3, and Server4. All servers run Windows Server 2012
R2.
Server1 and Server3 are located in a site named Site1. Server2 and Server4 are located in a site
named Site2. The servers are configured as nodes in a failover cluster named Cluster1.
Dynamic quorum management is disabled.
Cluster1 is configured to use the Node Majority quorum configuration.
You need to ensure that users in Site2 can access Cluster1 if the network connection between the
two sites becomes unavailable.
What should you run from Windows PowerShell?
To answer, drag the appropriate commands to the correct location. Each command may be used
once, more than once, or not at all. You may need to drag the split bar between panes or scroll to
view content.
Answer: 
Explanation:
NodeWeight settings are used during quorum voting to support disaster recovery and multi-subnet
scenarios for AlwaysOn Availability Groups and SQL Server Failover Cluster Instances.
Example (Powershell)
The following example changes the NodeWeight setting to remove the quorum vote for the
“AlwaysOnSrv1” node.
Import-Module FailoverClusters
$node = “AlwaysOnSrv1”
(Get-ClusterNode $node).NodeWeight = 0Configure Cluster Quorum NodeWeight Settings.
When the link between the sites are lost, there are no Majority on both sides. The configuration with Node Majority and Dynamic Quorum Management disabled, would lead to have no working cluster on both sides, because 2 of 4 are still 50%, which is not a Majority. So to have the cluster running in site 2, you need to take out a host in site 1 from voting. You can reach this configuration with:
Get-ClusterNode Server1 | $_.NodeWeight = 0