You need to ensure that running the disk maintenance tool does not cause a failover to occur

Your network contains an Active Directory domain named contoso.com. The domain contains two
member servers named Server1 and Server2. All servers run Windows Server 2012 R2.
Server1 and Server2 have the Failover Clustering feature installed. The servers are configured as
nodes in a failover cluster named Guster1. Cluster1 contains a file server role named FS1 and a
generic service role named SVC1. Server1 is the preferred node for FS1. Server 2 is the preferred
node for SVC1.
You plan to run a disk maintenance tool on the physical disk used by FS1.
You need to ensure that running the disk maintenance tool does not cause a failover to occur.
What should you do before you run the tool?

Your network contains an Active Directory domain named contoso.com. The domain contains two
member servers named Server1 and Server2. All servers run Windows Server 2012 R2.
Server1 and Server2 have the Failover Clustering feature installed. The servers are configured as
nodes in a failover cluster named Guster1. Cluster1 contains a file server role named FS1 and a
generic service role named SVC1. Server1 is the preferred node for FS1. Server 2 is the preferred
node for SVC1.
You plan to run a disk maintenance tool on the physical disk used by FS1.
You need to ensure that running the disk maintenance tool does not cause a failover to occur.
What should you do before you run the tool?

A.
Run Suspend-ClusterResource.

B.
Run Suspend-GusterNode.

C.
Run cluster.exe and specify the pause parameter.

D.
Run cluster.exe and specify the offline parameter.



Leave a Reply 6

Your email address will not be published. Required fields are marked *


mostafa

mostafa

Agree chaser

kingces

kingces

Agree with A. From MS:

Suspend-ClusterResource: Turns on maintenance for a disk resource or Cluster Shared Volume so that you can run a disk maintenance tool without triggering failover.

RonP

RonP

I could see the answer above being correct, if you consider the /offline parameter coupled with WAIT, which could wait indefinitely, which would seem to satisfy the “does not cause a failover” piece. What do you guys think about that?

kurt

kurt

thank u Kingces