3V0-23.25 Advanced VMware Cloud Foundation 9.0 Storage Question and Answers

Option D is the only design that uses supported non-vSAN storage models while matching the workload characteristics. VMFS over Fibre Channel is a supported enterprise block-storage option for the Management Domain and provides shared, resilient storage with SAN fabric pathing, zoning, LUN masking, and multipathing. Production requires low-latency block storage, and VMFS over NVMe/FC aligns with that requirement by using NVMe over Fibre Channel transport for high-performance block access. Non-production requires high-capacity file-based storage, and NFS v4.1 is the supported file-based option listed in the design. Option A is invalid because SMB is not a supported vSphere datastore protocol for VCF workload domain storage. Option B fails because local VMFS datastores do not provide the required shared storage model for a VCF Management Domain, and iSCSI is not presented as the complete best-fit block-storage design in the choices. Option C violates the explicit non-vSAN requirement by using vSAN ESA, vSAN HCI Mesh, and vSAN File Services. Reference topics: Supported Non-vSAN Storage, Fibre Channel Storage Model, NVMe/FC, NFS Storage Model, Principal and Supplemental Storage.

vSAN Stretched Clusters meet the availability-zone requirement by extending a single logical vSAN cluster across two availability zones and using a witness for quorum. This provides rapid recovery from a site or availability-zone failure because workloads remain protected by the stretched topology and vSAN site-failure tolerance. vSAN Storage Cluster addresses the need for scalable, high-performance storage that can grow independently as application capacity requirements increase. In VCF 9.0, a vSAN Storage Cluster is based on vSAN ESA and provides disaggregated storage to vSAN compute or HCI clusters. This design supports storage-dense NVMe-based nodes, high IOPS, low latency, independent capacity scaling, and centralized storage services. Encryption at rest and in transit are native vSAN capabilities that can be enabled on the vSAN-backed storage architecture. vSAN File Service is for file shares, and vSAN iSCSI Target Service is for presenting block LUNs to external initiators; neither is required by the stated application-storage design. vSAN Data Protection is valuable for snapshots and recovery points, but the core architecture requirements are best satisfied by stretched site resilience plus scalable vSAN storage clustering. Reference topics: vSAN Storage Cluster, vSAN Stretched Cluster, vSAN ESA, vSAN Encryption.

The correct configuration is to create distinct SPBM storage policies mapped to supported shared NFS datastore resources and assign them to the matching Supervisor storage functions. Supervisor uses storage policies to represent datastores and to manage placement of components and workload storage. The documentation states that storage policies support shared datastores such as VMFS, NFS, vSAN, and vSAN ESA. At the Supervisor level, administrators configure storage policies for control plane VMs and, when vSphere Pods are used, assign policies for ephemeral disks and container image disks. Persistent storage for workloads is also made available through storage policies assigned at namespace level. Option A is too narrow because it forces all policies to reference one datastore merely for logical isolation, while the supported model allows distinct policies mapped to one or more shared NFS datastores. Option B is incorrect because DRS is compute placement, and datastore clusters are not the Supervisor mechanism for persistent volume policy assignment. Option D is incorrect because the Supervisor does not automatically create these storage policies. Reference topics: Supervisor Storage Policies, SPBM, NFS Shared Datastores, Ephemeral Disks, Container Images, Persistent Volumes.

vSAN File Share SMB services are required because the storage must be consumed by Windows workstations and the application requires native NTFS permissions. SMB is the Windows-native file sharing protocol and integrates with Active Directory authentication. vSAN File Service supports SMB file shares, and Windows clients joined to the Active Directory domain configured with vSAN File Service can access those shares by using the SMB path. vSAN File Service also supports Microsoft Management Console for SMB shares, including Access Control List management, open file viewing, active sessions, and client connection management. These capabilities align directly with NTFS-style permission expectations for Windows-based graphic design workstations. vSAN File Service also supports two-node vSAN configurations, which matches the remote-site rack-space constraint of two hosts with a witness deployed remotely or in a shared location. NFSv3 does not provide native NTFS permissions for Windows clients. vSAN Storage Cluster and vSAN HCI Mesh address remote datastore capacity sharing, not SMB file access for Windows users. Reference topics: vSAN File Service, SMB File Shares, Active Directory Integration, Two-Node vSAN Support.

The architect should highlight that quotas and Access Based Enumeration are configured when creating the vSAN file share, with ABE available for SMB shares. In the vSAN File Service create-share workflow, the General page allows the administrator to choose the protocol and configure protocol-specific options. When SMB is selected, the share can be configured with Access Based Enumeration, which displays only files and folders that the user has permission to access and hides files or folders where the user lacks Read or equivalent permissions. The same create-share workflow also includes Storage space quotas, including a share warning threshold and a share hard quota. Therefore, the design implication is operational: quotas and ABE must be planned and applied at the file-share configuration level for SMB shares that require both controls. Quotas are not limited only to NFS shares, and ABE is not a cluster-level setting. Separate file service servers are also unnecessary because vSAN File Service supports SMB and NFS shares through the same file service architecture. Reference topics: vSAN File Service, Create vSAN File Share, SMB Access Based Enumeration, Storage Space Quotas.

Dedicated VMFS datastores on assigned Fibre Channel arrays meet both the performance and separation requirements. VCF supports Fibre Channel-backed VMFS as principal storage for workload domains, making it valid as the primary datastore type for the tier-1 business application cluster. Fibre Channel provides low-latency block storage, resilient pathing, SAN zoning, LUN masking, and mature enterprise performance characteristics. Because the existing FC arrays are partitioned by business unit, dedicated datastores preserve organizational separation and avoid mixing business-unit workloads on shared storage resources. The same dedicated FC-backed VMFS approach can also be used as supplemental storage after the workload domain exists, allowing extra capacity or specialized tiers while maintaining separation. Shared VMFS datastores do not satisfy the organizational separation requirement because they allow multiple business units to consume the same datastore boundary. vSAN is explicitly excluded, so the design must rely on supported non-vSAN storage. Automated VM placement can be supported by VMFS datastore clusters and Storage DRS where datastores are compatible and similarly managed. Reference topics: Fibre Channel Storage Model, VMFS Datastores, Principal Storage, Supplemental Storage, Datastore Clusters.

Run the Python reboot helper script only on one ESXi host to recover the cluster.

Enable cluster member updates from vCenter Server on all ESXi hosts.

Exit all hosts from maintenance mode.

During a manual vSAN cluster restart after a planned outage, the hosts must first be brought back and exited from maintenance mode so the cluster can begin recovery. The vSAN reboot helper recovery script must then be run on only one ESXi host. Running the script on multiple hosts can create race conditions and unexpected cluster state. After the recovery script completes, cluster member updates from vCenter Server must be enabled on all ESXi hosts so that normal membership updates resume across the cluster. Enabling updates on only one host is incomplete because all hosts must return to normal cluster-member update behavior. Running the Python reboot helper script on all ESXi hosts is explicitly incorrect because the recovery operation must be initiated from a single host only. Disabling cluster member updates is a shutdown-side activity, not the required restart-side recovery action in this question. Reference topics: Manual vSAN Cluster Restart, Reboot Helper Script, Maintenance Mode Exit, Cluster Member Updates.

Because the vSAN cluster uses vSphere Lifecycle Manager images, the least disruptive remediation method from the provided choices is to enable Quick Boot in the host remediation settings for images. Quick Boot reduces host remediation time by skipping the full hardware reboot, including the BIOS or UEFI firmware reboot. This reduces the amount of time each ESX host spends in maintenance mode and lowers operational disruption during patching. The documentation states that Quick Boot can be configured for clusters or standalone hosts managed with vSphere Lifecycle Manager images, and that it reduces reboot time during remediation. The baseline options are incorrect because the cluster is explicitly managed by images, not baselines. Disabling Quick Boot would increase disruption because hosts would require a full reboot path. Disabling HA admission control is not the least-disruption patching mechanism and is listed for baseline-oriented remediation behavior in the offered answer. In a vSAN cluster, hosts enter maintenance mode one at a time, so reducing each host’s maintenance window through Quick Boot is the appropriate method. Reference topics: vSphere Lifecycle Manager Images, Host Remediation Settings, Quick Boot, vSAN Cluster Remediation.

The correct process is to present the Fibre Channel LUNs from the storage array, rescan HBAs on each ESX host, create the VMFS datastore once, verify that the datastore is visible on all hosts, and confirm the result in vCenter. Fibre Channel storage requires correct SAN fabric zoning, LUN masking, host registration, and HBA discovery so that all hosts in the workload domain cluster can see the same shared LUN. After the array presents the LUN, each host must rescan its HBAs to discover the new storage device. VMFS is a clustered file system, so the datastore is created only once on the shared LUN. The datastore then becomes available to all hosts that have access to that device; it must not be independently formatted on each host. Creating the VMFS datastore separately on each host would risk datastore corruption or duplicate formatting. The final validation step is confirming datastore visibility and accessibility for all cluster hosts in vCenter. Reference topics: Fibre Channel Storage Model, HBA Rescan, Create VMFS Datastore, Shared VMFS Datastore Visibility.

The cluster must not include hosts from different subnets or networks (L3).

The default management vSphere cluster must already be stretched.

The cluster must not include DPU-backed hosts.

The cluster must not share a vSAN Storage Policy with any other cluster.

To stretch a vSAN cluster in a VCF Workload Domain, the environment must satisfy specific VCF stretch prerequisites and avoid unsupported configurations. The default management vSphere cluster must already be stretched so the management plane remains available if an availability zone fails. The workload cluster must not include hosts from different subnets or Layer 3 networks because the stretch workflow expects supported site and network placement assumptions for the cluster being stretched. The cluster must also not include DPU-backed hosts, because clusters with DPU-backed hosts are excluded from this stretch operation. In addition, the cluster must not share a vSAN Storage Policy with any other cluster, because shared policies can create policy scope and compliance conflicts during stretch configuration. SSH does not need to be manually activated on all hosts as a prerequisite. The default management cluster being “not stretched” is the opposite of the required condition. Host self-signed certificates are not the listed blocking condition for this workflow. Reference topics: Stretch vSAN Cluster in VCF, Workload Domain Stretch Prerequisites, vSAN Storage Policy Constraints, Unsupported Stretch Configurations.

vSAN HCI Mesh is the correct feature because the application must continue running on the existing compute cluster, but that cluster lacks enough unused vSAN capacity and has no available NVMe slots for expansion. HCI Mesh, also known as vSAN datastore sharing, allows independent vSAN clusters to share remote datastore capacity with other compatible vSAN clusters. The remote datastore can be mounted and used as if it were local storage, allowing VMs running on the current cluster to consume storage from another vSAN cluster that has sufficient capacity and performance. This satisfies the requirement without purchasing hosts, reassigning hosts, or moving the application away from the cluster that provides the required CPU and memory. vSAN Data Protection addresses snapshots and recovery, not capacity expansion. vSAN File Services provides SMB/NFS file shares, not additional VM datastore capacity. vSAN Stretched Clusters provide availability-zone resilience, not cross-cluster capacity borrowing. VCF documentation describes HCI Mesh as cross-cluster capacity sharing that enables multiple independent vSAN HCI clusters to consume storage from adjacent vSAN storage resources. Reference topics: vSAN HCI Mesh, vSAN Datastore Sharing, Cross-Cluster Capacity Sharing, Remote vSAN Datastore.

The design requires four hardware corrections. First, RAID-6 with FTT=2 requires six fault domains or hosts because RAID-6 erasure coding must place data and parity components across enough independent hosts to tolerate two failures. Therefore, four hosts are insufficient and the host count must increase to at least six. Second, Storage Traffic Separation requires sufficient physical NICs to support separate storage and non-storage traffic paths. With two distributed switches and redundant uplinks, the design must increase to four 25 GbE NICs per host. Third, vSAN ESA requires at least 128 GB of host memory; the provided 96 GB is below the minimum. Fourth, NVMe devices attached to a SATA/SAS/NVMe Tri-mode controller are not supported for vSAN storage pools. The documentation states that vSAN supports SAS and SATA devices on Tri-mode controllers, but NVMe devices must be directly connected to PCIe or use a supported NVMe design. The CPU count does not need to increase because 24 cores satisfies the stated vSAN ESA minimum in the referenced design guidance. Reference topics: vSAN ESA Hardware Requirements, RAID-6 FTT=2, Storage Traffic Separation, NVMe Controller Support.

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.

The Repair Delay Timer expires, and vSAN starts automatic repair evaluation.

Once data resync completes, objects are marked as Compliant again.

vSAN verifies policy requirements and rebuilds missing components on available capacity devices.

When a host goes offline unexpectedly, vSAN treats the missing components as absent and waits for the configured repair delay timer before initiating rebuild operations. This prevents unnecessary resynchronization when a host or device returns quickly. In this scenario, the host is offline for more than an hour, so the repair delay timer expires and vSAN begins automatic repair evaluation. vSAN then checks the assigned storage policies, available capacity, and fault-domain placement requirements to determine whether missing components can be rebuilt safely on available capacity devices. If sufficient capacity and fault domains exist, vSAN creates replacement components and starts resynchronization. When the resync process finishes and the affected objects again satisfy their assigned policies, the objects are marked Compliant. The administrator does not need to manually run a resync task from vCenter, and the host does not need to be placed into maintenance mode for automatic repair. A full cluster rebalance is a separate capacity-balancing operation and is not required before object repair. Reference topics: vSAN Repair Delay Timer, Object Compliance, Resynchronization, ESA Object Repair.

Deploy ESX at 9.x

Deploy vCenter 9.x

Create Storage and General dvS

Configure VMkernel Binding for the NVMe over TCP Adapter

Add Software NVMe over TCP Adapters

Import the workload domain to VCF

The correct sequence starts by preparing the vSphere environment that will later be imported into VMware Cloud Foundation. ESX 9.x must be deployed first on the six blade hosts because the hosts provide the compute foundation for the workload domain. After the hosts are available, vCenter 9.x is deployed to manage the cluster and provide the required vSphere inventory. The two distributed switches are then created: one for storage isolation and one for general host and workload traffic. Because the external array supports NVMe/TCP only and multipathing is required, VMkernel binding must be configured for the NVMe over TCP adapter before the software NVMe over TCP adapters are added. This ensures the NVMe/TCP storage paths are correctly associated with the intended storage network. After the software NVMe over TCP adapters are created and the hosts can access the external storage, the prepared workload domain can be imported into the existing VCF environment. Reference topics: NVMe over TCP Configuration, VMkernel Binding, Software NVMe/TCP Adapters, Existing vCenter Import, VCF Workload Domain Import.

LUN Masking = A security process performed on the storage array by which specific storage components are hidden to prevent unauthorized access to data;

Datastore Cluster = A collection of shared resources with a shared management interface that enables resource allocation policies;

SAN Fabric = A dedicated high-performance network infrastructure for storage devices;

Datastore = A manageable storage entity used as a repository for Virtual Machine files including log files, scripts, configuration files and virtual disks;

Host Bus Adapter (HBA) = Added to an ESX host server to allow the host access to the dedicated storage area network;

Zoning = A security process completed on the Storage Area Network to ensure only certain devices can communicate with each other.

These definitions describe the core components of a Fibre Channel SAN design in a VCF Workload Domain. LUN masking is performed on the storage array and controls which hosts can see specific LUNs, preventing unauthorized access to storage. A datastore cluster is a collection of datastores managed as a shared resource pool, allowing placement and balancing policies through Storage DRS. A SAN fabric is the dedicated high-performance network that interconnects ESX hosts, Fibre Channel switches, and storage arrays. A datastore is the vSphere logical storage container where VM configuration files, virtual disks, logs, and related files reside. A Host Bus Adapter is the physical or virtual adapter in the ESX host that connects the host to the Fibre Channel storage area network. Zoning is performed on the Fibre Channel fabric and controls which initiators and targets can communicate. Together, zoning and LUN masking provide layered access control, while datastores and datastore clusters provide the vSphere consumption model. Reference topics: Fibre Channel SAN Concepts, SAN Fabric, Zoning, LUN Masking, VMFS Datastores, Datastore Clusters.

Site A = Data Site; Site B = Witness Site; Site C = Data Site; Site A ↔ Site C = Layer 3, RTT < 5 ms; Site A ↔ Site B = Layer 3, RTT < 200 ms; Site B ↔ Site C = Layer 3, RTT < 200 ms

Site A and Site C should be the data sites because Site A hosts production services and Site C has been commissioned to replace the capacity-constrained Site B. Site B should be used as the witness site because it has no space for additional physical hosts, and a vSAN witness appliance does not run workload VMs. A vSAN Stretched Cluster requires two availability zones for data nodes and a third site for the witness appliance. The data-site-to-data-site connection carries synchronous vSAN data traffic and must meet less than 5 ms RTT. The witness site carries metadata traffic only, so the data-site-to-witness links support higher latency, with less than 200 ms RTT for up to 10 hosts per site. Because the requirement specifically calls out minimizing disruption from STP, Layer 3 is the preferred network type between sites. VMware states that Layer 3 helps avoid STP redirecting traffic across undesirable links, such as constrained witness links. Reference topics: vSAN Stretched Cluster Network Design, Data Site and Witness Site Placement, Layer 3 Recommendation, RTT Requirements.

Run the esxcli storage nfs list command.

Use vCenter Datastore Performance view to monitor NFS datastore latency, IOPS and throughput.

Create a vCenter performance alarm for “Datastore Latency (NFS)” to trigger when thresholds are exceeded.

The correct monitoring workflow is to verify NFS datastore presentation at the host layer, then use vCenter performance views and alarms for operational monitoring. The esxcli storage nfs list command confirms that the NFS datastore is mounted and visible to the ESX host, which is the first validation point before any performance assessment. vCenter Datastore Performance views provide the correct datastore-level telemetry for latency, IOPS, and throughput, including NFS-backed datastores. Creating a vCenter performance alarm for NFS datastore latency allows proactive alerting when the datastore exceeds the required latency threshold. The esxcli storage core device list command is intended for block storage devices and paths, not NFS datastores. The --verbose NFS option listed here is not the required method for collecting detailed performance metrics in this scenario. VCF Operations Logs is log-focused, not the correct graph source for NFS throughput validation. vSAN Performance Service applies to vSAN performance, not external NFS datastore monitoring. Reference topics: NFS Datastore Monitoring, vCenter Datastore Performance, NFS Host Validation, vCenter Performance Alarms.

In vSAN ESA, the observed three disk stripes are expected behavior for objects using RAID-1, even when the storage policy shows “Number of disk stripes per object = 1.” The vSAN policy rule defines the minimum number of capacity devices across which each replica of an object is striped, and the default value is 1. However, VMware documentation explicitly notes that objects in a vSAN ESA cluster with RAID-0 or RAID-1 configuration have 3 disk stripes, even if the default storage policy defines only 1 disk stripe. Therefore, the three stripes are not caused by site mirroring itself, nor by the VM having three objects. Site mirroring controls placement across the preferred and secondary sites in a stretched cluster, while Failures to tolerate with RAID-1 controls local host/device protection. The behavior is also not evidence that a VM-level policy override exists. The datastore-level policy can still be applied correctly; ESA’s internal RAID-1 object layout uses three stripes as part of its optimized storage architecture. Reference topics: vSAN ESA Default Storage Policy Characteristics, Number of Disk Stripes per Object, RAID-1 Mirroring, vSAN Stretched Cluster Storage Policies.

In a three-node vSAN ESA cluster, the maximum practical storage policy failure tolerance is one failure. RAID-1 mirroring with Failures to tolerate set to 1 is supported because vSAN can place mirrored data components across the available hosts while maintaining quorum. RAID-5 erasure coding with Failures to tolerate set to 1 is also supported in vSAN ESA three-host clusters. The documentation specifically states that RAID-5 in vSAN ESA supports three ESX host clusters. RAID-6 with FTT=2 is not supported because it requires at least six ESX hosts in the vSphere cluster. RAID-1 with FTT=2 would also require additional fault domains because vSAN requires 2n+1 fault domains for n failures tolerated. HA reserved failover capacity for CPU and memory does not change the number of vSAN fault domains available for storage object placement. It only affects compute admission control. Therefore, the two valid maximum protection levels for this three-node ESA cluster are RAID-1 mirroring with one failure and RAID-5 erasure coding with one failure. Reference topics: vSAN ESA Storage Policies, Failures to Tolerate, RAID-1 Mirroring, RAID-5 Erasure Coding, RAID-6 Requirements.