Your network contains an Active Directory domain.
The domain contains 20 member servers.
The domain contains have two servers named Server1 and Server2 that run Windows Server 2008 R2.
You connect Server1 and Server2 to a logical unit number (LUN) on a Storage Area Network (SAN).
You create a failover cluster named Cluster1. You add Server1 and Server2 as nodes to Cluster1.
You discover that there are no cluster disks available for a new clustered file server service on Cluster1.
You need to ensure that you can add a clustered file server service to Cluster1.
What should you do?

A.
Enable cluster shared volumes.

B.
Run the Provision Storage Wizard.

C.
Configure Cluster1 to use a No Majority: Disk Only quorum configuration.

D.
Configure Cluster1 to use a Node and File Share Majority quorum configuration.

Explanation:
Quorum configuration choices
You can choose from among four possible quorum configurations:
Node Majority (recommended for clusters with an odd number of nodes)
* Can sustain failures of half the nodes (rounding up) minus one. For example, a seven node cluster can sustain three node failures.
Node and Disk Majority (recommended for clusters with an even number of nodes)
* Can sustain failures of half the nodes (rounding up) if the disk witness remains online.
For example, a six node cluster in which the disk witness is online could sustain three node failures.
* Can sustain failures of half the nodes (rounding up) minus one if the disk witness goes offline or fails.
For example, a six node cluster with a failed disk witness could sustain two (3-1=2) node failures.
Node and File Share Majority (for clusters with special configurations)
* Works in a similar way to Node and Disk Majority, but instead of a disk witness, this cluster uses a file share witness.
Note that if you use Node and File Share Majority, at least one of the available cluster nodes must contain a current copy of the cluster configuration before you can start the cluster. Otherwise, you must force the starting of the cluster through a particular node.
No Majority: Disk Only (not recommended)
* Can sustain failures of all nodes except one (if the disk is online).
However, this configuration is not recommended because the disk might be a single point of failure.
Source: http://technet.microsoft.com/en-us/library/cc731739.aspx