Exam 3V0-23.25 Topic 1 Question 12 Discussion

Actual exam question for VMware's 3V0-23.25 exam
Question #: 12
Topic #: 1

A CTO is defining the StorageClass strategy for a new Tanzu Kubernetes cluster running on vSAN ESA. The workloads are heavy write-intensive databases.
The CTO is debating whether to enforce "Object Space Reservation: Thick" (100% reserved) in the SPBM policy attached to the K8s StorageClass, or leave it as the default "Thin" provisioned.
```
[vSAN Performance / Capacity View Projection]
Option 1: Thick Provisioning (100% OSR) -> 50 TB PVCs consume 50 TB immediately.
Option 2: Thin Provisioning (0% OSR) -> 50 TB PVCs consume only written data (e.g., 5 TB initially).
```
Which of the following statements correctly evaluate the trade-offs of enforcing "Thick" provisioning via a Kubernetes StorageClass on vSAN ESA? (Select all that apply.)

A. Using "Thin" provisioning creates a race condition where thousands of K8s pods could oversubscribe the datastore, causing an APD event when physical space runs out. B. Thick provisioning on vSAN ESA accelerates database write performance by zeroing out the physical NVMe blocks during PVC creation. C. Thick provisioning prevents "Out of Space" (OOS) runtime crashes for database pods; if the datastore fills up, the thick-provisioned database is already guaranteed its 50 TB. D. In vSAN ESA, "Thick" provisioning does not pre-allocate physical NVMe blocks; instead, it logically reserves the capacity quota in the DOM to guarantee space for the pod's lifetime. E. Kubernetes CSI drivers are incompatible with Thick provisioning; the feature was deprecated in vSphere 8.0.

Comments

0 Satisfied Customers

0 Shares

0 Demo Downloads

10 Years in Business