An architect is designing a vSAN stretched cluster and needs to ensure that data remains on a given site in case of a network partition between the sites.
Which configuration would do this?
An architect is designing a vSAN stretched cluster and needs to ensure that data remains on a given site in case of a network partition between the sites.
Which configuration would do this?
To ensure that data remains on a given site in case of a network partition between sites in a vSAN stretched cluster, the appropriate configuration is the use of preferred and secondary sites. This configuration allows for establishing a preferred site for data storage, ensuring data locality and minimizing the risk of data inconsistencies. Other options such as vCenter High Availability, Distributed Resource Scheduler, and vSphere High Availability do not address the specific requirement of keeping data on a given site in the event of a network partition.
To ensure that data remains on a given site in case of a network partition between sites in a vSAN stretched cluster, the architect could configure the preferred and secondary sites. This configuration establishes which site is preferred and ensures that the data remains on that preferred site unless communication between the sites is restored. Therefore, option A is the correct answer. This configuration can be helpful in maintaining data locality and minimizing the risks of inconsistencies in the stretched-cluster environment.
C. https://docs.vmware.com/en/VMware-vSphere/8.0/vsan-planning/GUID-1BDC7194-67A7-4E7C-BF3A-3A0A32AEECA9.html
The requirement here is to keep the data on a given site. So answer is A. The other answer have nothing to see with data placement, only VM or vCenter availability or placement.
A is correct