Your network contains an Active Directory domain. The domain contains two servers named Server1
and Server2. You connect Server1 and Server2 to a logical unit number (LUN) on a Storage Area

Network (SAN). You need to ensure that you can use the LUN in a failover cluster. What should you
do?

A.
From Server Manager, run the Best Practices Analyzer.

B.
From File Server Resource Manager, generate a storage report.

C.
From Failover Cluster Manager, run the Validate a Configuration Wizard.

D.
From Share and Storage Management, verify the advanced settings of the LUN.

Explanation:
Ensure that the disks (LUNs) that you want to use in the cluster are exposed to the servers you will
cluster (and only those servers). You can use any of the following interfaces to expose disks or LUNs:
1. Microsoft Storage Manager for SANs (part of the operating system in Windows Server
2008). To use this interface, you need to contact the manufacturer of your storage for a
Virtual Disk Service (VDS) provider package that is designed for your storage.
2. If you are using iSCSI, an appropriate iSCSI interface.
3. The interface provided by the manufacturer of the storage.
Source: http://technet.microsoft.com/es-es/library/dd197507(WS.10).aspx
Considerations when including storage tests : When cluster validation is performed on an already
configured cluster, if the default tests (which include storage tests) are selected, only disk resources
that are in an Offline state or are not assigned to a clustered service or application will be used for
testing the storage. This builds in a safety mechanism, and the cluster validation wizard warns you
when storage tests have been selected but will not run on storage in an Online state, that is, storage
used by clustered services or applications. This is by design to avoid disruption to highly available
services or applications that depend upon these disk resources being online.
One scenario where Microsoft CSS may request you to run validation tests on production clusters is
when there is a cluster storage failure that could be caused by some underlying storage
configuration change or failure. By default, the wizard warns you if storage tests have been selected
but will not be run on storage that is online, that is, storage used by clustered services or
applications. In this situation, you can run validation tests (including storage tests) by creating or
choosing a new logical unit number (LUN) from the same shared storage device and presenting it to
all nodes. By testing this LUN, you can avoid disruption to clustered services and applications already
online within the cluster and still test the underlying storage subsystem
How to run the cluster validation wizard for a failover cluster
To validate a new or existing failover cluster
Identify the server or servers that you want to test and confirm that the failover cluster feature is
installed:
If the cluster does not yet exist, choose the servers that you want to include in the cluster, and make
sure you have installed the failover cluster feature on those servers. To install the feature, on a
server running Windows Server 2008 or Windows Server 2008 R2, click Start, click Administrative
Tools, click Server Manager, and under Features Summary, click Add Features. Use the Add Features
wizard to add the Failover Clustering feature.
If the cluster already exists, make sure that you know the name of the cluster or a node in the
cluster.
Review network or storage hardware that you want to validate, to confirm that it is connected to the
servers. For more information, see http://go.microsoft.com/fwlink/?LinkId=111555.

Decide whether you want to run all or only some of the available validation tests. For
detailed information about the tests, see the topics listed in
http://go.microsoft.com/fwlink/?LinkId=111554.
The following guidelines can help you decide whether to run all tests:
For a planned cluster with all hardware connected: Run all tests.
For a planned cluster with parts of the hardware connected: Run System Configuration tests,
Inventory tests, and tests that apply to the hardware that is connected (that is, Network tests if the
network is connected or Storage tests if the storage is connected).
For a cluster to which you plan to add a server: Run all tests. Before you run them, be sure to
connect the networks and storage for all servers that you plan to have in the cluster. For
troubleshooting an existing cluster: If you are troubleshooting an existing cluster,
you might run all tests, although you could run only the tests that relate to the apparent issue.
Important If a clustered service or application is using a disk when you start the wizard, the wizard
will prompt you about whether to take that clustered service or application offline for the purposes
of testing. If you choose to take a clustered service or application offline, it will remain offline until
the tests finish.
In the failover cluster snap-in, in the console tree, make sure Failover Cluster
Management is selected and then, under Management, click Validate a Configuration.

Follow the instructions in the wizard to specify the servers and the tests, and run the tests.
Note that when you run the cluster validation wizard on unclustered servers, you must enter the
names of all the servers you want to test, not just one.
The Summary page appears after the tests run.
While still on the Summary page, click View Report to view the test results. To view the results of the
tests after you close the wizard, see SystemRoot

\Cluster\Reports\Validation Report date and time.html where SystemRoot is the folder in which the
operating system is installed (for example, C:
\Windows).
To view Help topics that will help you interpret the results, click
More about cluster validation tests.
To view Help topics about cluster validation after you close the wizard, in the failover cluster snap-in,
click Help, click Help Topics, click the Contents tab, expand the contents for the failover cluster Help,
and click\ Validating a Failover Cluster Configuration
Source: http://technet.microsoft.com/en-us/library/cc732035(WS.10).aspx