A vSAN administrator has an existing cluster where each ESXi host has the following: - Disk group #1 with one cache device and three capacity devices. - Disk group #2 with one cache device and two…

Question

Options

• ACreate a new disk group with a single capacity device and then migrate the existing capacity
• BAdd the new capacity device to the disk group and vSAN will automatically rebalance
• CPut the entire ESXi host in maintenance mode, evacuate all data, then add the new capacity
• DPut the disk group in maintenance mode, evacuate all data, then add the new capacity device

• B
  95% (35)
• C
  3% (1)
• D
  3% (1)

Explanation

Adding a capacity device to an existing vSAN disk group is a hot-add operation - vSAN supports non-disruptive expansion, so you simply add the device and vSAN automatically incorporates it and rebalances data across the disk group without any downtime (B is correct).

A is wrong because you never need to create a new disk group just to add capacity to an existing one - that wastes resources and creates unnecessary complexity. C is wrong because full host maintenance mode with data evacuation is a drastic, disruptive operation reserved for hardware replacement or decommissioning a host entirely, not for adding capacity. D is similarly wrong - putting a disk group in maintenance mode to add capacity is not required; disk group maintenance mode is used when removing or replacing a device, not adding one.

Memory tip: Think of vSAN capacity expansion like adding a drawer to a filing cabinet while it's still in use - you just slide it in (hot-add) and the system figures out the rest. Any answer involving evacuation or maintenance mode implies removal, not addition.

No community discussion yet for this question.