VCAP-Storage 3V0-23.25 Reddit Questions

NFS v3 is the best recommendation because the scenario provides only Ethernet-based host connectivity and no budget for additional hardware. Fibre Channel would require appropriate FC HBAs, SAN zoning, and array presentation to all hosts. The provided hosts only have Ethernet NICs and local boot/storage devices, so they are not prepared for FC without additional hardware. VMware Cloud Foundation supports NFS as principal storage for VI workload domains, but the supported principal NFS protocol version is NFS v3. NFS v4.1 is supported as supplemental storage, not as principal storage for this use case. The documentation also states that when NFS is used as principal storage with vSphere Lifecycle Manager images, only two hosts are required, matching this two-host scenario. Fibre Channel over Ethernet is not the appropriate supported principal storage option in this VCF storage model. Therefore, NFS v3 uses the existing network capability, avoids new hardware spend, and aligns with the supported VCF principal storage model. Reference topics: Principal Storage, NFS Storage Model, VI Workload Domain Storage, Fibre Channel Prerequisites.

Windows Server Failover Cluster shared disks require coordinated access to shared block storage. vSAN supports Windows Server Failover Clusters by providing SCSI-3 Persistent Reservation support at the virtual disk level, which allows cluster nodes to arbitrate access to a shared disk resource. One supported approach is to use the vSAN iSCSI Target Service, which presents vSAN-backed LUNs to initiators and can be used for clustered workloads that require shared block access. Another supported approach is to configure a shared virtual disk using a VMware Paravirtual SCSI controller with physical bus sharing. Physical bus sharing allows multiple VMs to access the same shared virtual disk in a WSFC configuration where supported. Raw Device Mapping is not the vSAN ESA-native solution for this requirement. NFS v4.1 is a file datastore protocol, not a WSFC shared block disk mechanism. “LSI SCSI controller per disk” does not satisfy the required shared-disk bus sharing configuration. Reference topics: vSAN Support for Windows Server Failover Clusters, SCSI-3 Persistent Reservations, vSAN iSCSI Target Service, Shared VMDK Configuration.

The administrator must validate that the vSphere Native Key Provider has been backed up. When a Native Key Provider is created, vCenter pushes the key provider configuration to clustered ESX hosts, but the provider is not usable for encryption tasks until it has been backed up. The documentation states that after adding a Native Key Provider, it appears as not backed up, and that it must be backed up before use. The backup process changes the provider status from Not Backed Up, to Warning while vCenter propagates information to hosts, and then to Active when the information has been pushed to all hosts. A TPM 2.0 device is not required when using Native Key Provider with default settings, although TPM can provide enhanced security and can optionally be enforced. Crypto Safe Mode and disabling Secure Boot are not prerequisites for enabling vSAN Data-at-Rest Encryption with NKP. Therefore, the validation step is to confirm that the NKP backup has been created and the provider is active on the hosts. Reference topics: vSphere Native Key Provider, Back Up Native Key Provider, vSAN Data-at-Rest Encryption, Key Provider Availability.

vSAN datastores are not managed through datastore clusters and Storage DRS in the same way as traditional VMFS or NFS datastore collections. A vSAN cluster exposes a distributed vSAN datastore, and VM placement, resilience, space efficiency, and compliance are controlled through vSAN Storage Policy Based Management rather than Storage DRS. The scenario also includes mixed vSAN OSA and vSAN ESA storage across clusters, which introduces an additional compatibility concern. vSAN OSA and vSAN ESA datastores are different architectures and are not combined into a single datastore-cluster construct for uniform Storage DRS placement. A datastore cluster should not combine different storage architectures such as vSAN, Fibre Channel, and NFS because Storage DRS assumes similar, interchangeable datastore resources. Creating a datastore cluster through APIs does not make vSAN datastores supported in this model. Therefore, the administrator should consider that vSAN datastores are not supported in datastore clusters and should use vSAN storage policies and appropriate datastore selection instead. Reference topics: vSAN Datastores, Storage Policy Based Management, Datastore Cluster Requirements, vSAN OSA and ESA Compatibility.