A three-node vSAN OSA cluster with business critical intensive I/O workload is running out of capacity. Each host consists of five disk groups with four capacity disks. The administrator needs to expand the capacity of the vSAN datastore as soon as possible.
What should the administrator do?
The best approach to expand the capacity of a vSAN datastore in a three-node cluster, especially with a business-critical intensive I/O workload, is to add an additional vSAN ReadyNode to the cluster. This will not only increase the overall capacity but also enhance the cluster's performance and resilience. Adding additional capacity disks to each disk group (option D) would increase capacity, but it might be more time-consuming and could temporarily impact performance due to the high I/O workload. Adding a new node provides immediate capacity and additional resources with less impact on the existing workload.
i do not agree and go for C. question states expand capacity as soon as possible. adding disks to each diskgroup (5) in three hosts wil take a lot of time. simply adding a host to the cluster is quick
D - Correct
Answer D is correct - reason see below, storage pool is in ESA, so not the right option. Rest see the options below - Scaling up adds additional storage capacity. • Scaling up a vSAN cluster can also perform the following actions in the vSAN environment: • Add capacity devices to an existing disk group or storage pool • Add new disk groups • Replace existing capacity devices with larger devices
To expand the capacity of a vSAN datastore in a three-node vSAN OSA cluster with five disk groups per host and four capacity disks per disk group, the administrator would need to add additional capacity disks to each disk group to increase the capacity. Therefore, the correct answer is option D. By adding capacity disks to each disk group, the administrator can increase the storage capacity of the datastore in the cluster.
The correct answer is D, each disk group can have 7 disks capacity
While technically C makes more sense, I would look at delays considering a sales cycle of procurement, rack/stack etc.. hence my selection being D
given it is a business critical intensive I/O workload, adding disk to existing setup will impact performance. A better way is to add nodes to increase capacity