A vSAN administrator has two identical VMware vSAN clusters, one for staging workloads and another for production workloads. Due to an unforeseen capacity requirement, the vSAN administrator is…

Question

Options

• ADisable vSAN Services
• BDelete all Disk Groups
• CEnable File Services
• DDelete all partitions from the capacity disks
• EMark the disks for partial reservation
• FRemove all capacity drives

• A
  74% (29)
• C
  8% (3)
• E
  15% (6)
• F
  3% (1)

Explanation

Before moving vSAN nodes to a new cluster, the staging cluster must be cleanly decommissioned at the software level. Disabling vSAN Services (A) formally removes the cluster's vSAN configuration and stops all vSAN-related processes, ensuring no data conflicts occur. Deleting all Disk Groups (B) removes the vSAN cache and capacity tier groupings, releasing the disks from vSAN management so they can be repurposed. Deleting all partitions from the capacity disks (D) wipes any residual vSAN metadata and partition tables that remain after disk groups are deleted - without this step, disks may be rejected or behave unexpectedly when added to the production cluster.

The distractors are wrong for these reasons:

• C (Enable File Services): File Services is an NFS/SMB sharing feature - irrelevant to cluster decommissioning.
• E (Mark disks for partial reservation): Not a real vSAN decommissioning step; this concept doesn't apply here.
• F (Remove all capacity drives): Physically removing drives before properly deleting disk groups (B) would be disruptive and out of order; deleting disk groups already handles releasing those drives.

Memory tip: Think of the process as "Stop → Strip → Scrub" - Stop vSAN (A), Strip the disk groups (B), Scrub the partitions (D). You must clean at each layer before hardware can safely move.

No community discussion yet for this question.