C is correct. For stretched clusters, read locality is force to 100% to ensure that data is read from the local site. Reference below from: https://core.vmware.com/resource/vsan-stretched-cluster-guide#the-vsan-witness-host In traditional vSAN clusters, a virtual machine’s read operations are distributed across all replica copies of the data in the cluster. In the case of a policy setting of NumberOfFailuresToTolerate =1, which results in two copies of the data, 50% of the reads will come from replica 1 and 50% from replica 2. In the case of a policy setting of NumberOfFailuresToTolerate =2 in non-stretched vSAN clusters, it results in three copies of the data, 33% of the reads will come from replica 1, 33% of the reads will come from replica 2, and 33% will come from replica 3. In a vSAN Stretched Cluster, we wish to avoid increased latency caused by reading across the inter-site link. The read locality mechanism was introduced to ensure that 100% of reads occur on the site the VM resides on. Read locality overrides the NumberOfFailuresToTolerate=1 policy’s behavior to distribute reads across the components.

My answer is C