A VCF Deployment Specialist is configuring a new Tanzu Kubernetes Grid (TKG) cluster. The developers require a StorageClass that provisions volumes on the vSAN datastore using an existing SPBM policy named "K8s-Gold-Policy".
```
# Kubernetes StorageClass Definition
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: vsan-gold-sc
provisioner: csi.vsphere.vmware.com
parameters:
[ ? ] : "K8s-Gold-Policy"
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
```
Which parameter key MUST be inserted at the [ ? ] placeholder to correctly bind this StorageClass to the vSphere storage policy?

A Cloud Administrator is troubleshooting a complex VCF failure where a virtual machine (VM-DB-
01) became completely inaccessible.
The environment utilizes a deeply integrated storage architecture:
- VM-DB-01 runs on Compute-Cluster-01 (Client).
- The VM's storage policy dictates FTT=1 (RAID-1).
- The storage resides on Storage-Cluster-02 (Server), which is
configured as a vSAN Stretched Cluster spanning Site A and Site B.
A massive fiber cut occurs, completely isolating Site A from the rest of the network. Compute- Cluster-01 and Site B remain connected to each other and the Witness.
The administrator pulls the vmkernel.log from Compute-Cluster-01 hosts:
```
2026-10-14T09:00:15Z ERROR cmmds - Cannot reach any hosts in Storage-
Cluster-02 (Site A).
2026-10-14T09:00:16Z WARN vsan - Remote datastore 'vsanDatastore-
Storage-02' object 5543... entering DEGRADED state.
2026-10-14T09:00:18Z INFO vsan - Remote datastore components shifted to Site B. Quorum maintained.
2026-10-14T09:00:30Z ERROR vobd - VM 'VM-DB-01' reported I/O timeout.
```
Given the interaction between HCI Mesh and Stretched Cluster mechanics, why did the VM experience an I/O timeout despite the log indicating "Quorum maintained"? (Select all that apply.)

A Network Administrator and Storage team are deploying a VCF Workload Domain with vSAN Data Protection configured for "Remote Replication" to a secondary cluster.
The security policy mandates Data-at-Rest Encryption for all production VMs.
```
# SPBM Policy: "Prod-Encrypted-DP"
[Capabilities]
Host.FailuresToTolerate: 1 (RAID-1)
Data.Encryption: Enabled (KMS-Prod)
DataProtection.RemoteTarget: "Sec-Site-Cluster"
DataProtection.RPO: 30 minutes
```
A VM is instantiated with this policy. A remote snapshot is successfully taken and replicated to the Sec- Site-Cluster.
How does the interaction between vSAN Native Encryption, SPBM, and Data Protection snapshots function to secure the data at the secondary site? (Select all that apply.)

Which vSAN feature ensures data availability across sites?

A VCF Deployment Specialist is troubleshooting a complex partition in a vSAN ESA cluster.
Following a vCenter restore from backup, the cluster split into 3 separate partition groups. The specialist uses Ruby vSphere Console (RVC) to dump the CMMDS cluster table:
```
[RVC Output: vsan.cluster_info ~cluster]
Partition Group 1: esx-01 (Master), esx-02 (Backup), esx-03
Partition Group 2: esx-04 (Master)
Partition Group 3: esx-05 (Master), esx-06
[root@esx-04:~] vmkping -I vmk2 192.168.10.1 (esx-01) -s 8972 -d
Response: sendto() failed: Message too long
```
Based on the RVC topology and vmkping output, which TWO configurations are directly causing this cluster segmentation? (Choose 2.)