HOTSPOT
You have an Exchange Server 2013 organization that contains four servers named EX1, EX2, EX3, and
EX4. All of the servers run Windows Server 2012 R2 and are members of a database availability
group (DAG) named DAG1. All of the mailbox databases replicate to all of the Mailbox servers.
From EX1, you run the Get-ClusterNode | fl cluster, state,*name*,*weight* command and you
receive the following output.
Use the drop-down menus to select the answer choice that completes each statement.
Answer: 
Explanation:
* up to one more node
Ex4 is already down. If Ex3 fails as well, then there would be still be Ex1 and Ex2. The Dag1 would be
still be operational if either of these node fail.
Important:
The advantage of Dynamic Quorum, is that it is now possible for a cluster to run even if the number
of nodes remaining in the cluster is less than 50%! By dynamically adjusting the quorum majority
requirement, the cluster can sustain sequential node shutdowns down to a single node and still keep
running.
* A DynamicWeight value of 1 indicates the node has a vote, and a value of 0 indicates the node
does not have a vote.
Note: Windows Server 2012 introduced a new model called Failover Clustering Dynamic Quorum,
which we can use with Exchange. When using Dynamic Quorum, the cluster dynamically manages
the vote assignment to nodes based on the state of each node. When a node shuts down or crashes,
it loses its quorum vote. When a node successfully re-joins the cluster, it regains its quorum vote. By
dynamically adjusting the assignment of quorum votes, the cluster can increase or decrease the
number of quorum votes that are required to keep it running. This enables the cluster to maintain
availability during sequential node failures or shutdowns.
* Both Ex1 and Ex2 go offline
The idea behind DQ (Dynamic Quorum) is that, by adjusting the assignment of quorum votes and
dynamically increasing or decreasing the number of quorum votes required to keep running, the
cluster can sustain sequential node shutdowns (or failures) all the way down to a single node
(referred to as a “last man standing”).
Windows Server 2012 R2 and Database Availability Groups
http://blogs.technet.com/b/scottschnoll/archive/2014/02/25/database-availability-groups-andwindows-server-2012-r2.aspx