3V0-23.25 VMware Advanced VMware Cloud Foundation 9.0 Storage Free Practice Exam Questions (2026 Updated)

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.

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.

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.

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.

vSAN ESA Storage Clusters are the optimal choice because the workload profile is capacity-heavy and benefits from disaggregated storage. The requirement for 2.5 PB of application data, archival workloads, gateways, and development/test applications indicates a need to scale storage capacity independently from compute resources. VMware Cloud Foundation describes a vSAN storage cluster as a disaggregated storage solution based on vSAN ESA. It provides storage resources but not compute resources, and its datastore can be mounted by vSAN compute clusters or vSAN HCI clusters. This model is designed for storage-dense environments where capacity and performance can be expanded without adding unnecessary compute. A standard vSAN ESA HCI cluster is excellent for high-performance workloads, but it scales compute and storage together. vSAN OSA all-flash and hybrid use the older disk-group architecture and are less suitable for this large-capacity, storage-centric design. Therefore, the principal storage recommendation should be vSAN ESA Storage Clusters to meet scalability, performance, and capacity growth requirements. Reference topics: vSAN Storage Cluster, Disaggregated Storage, vSAN ESA, Storage Models.

After vSAN File Services has been deployed, the editable settings are primarily related to the File Service domain network configuration. The vSAN File Service workflow allows modification of primary IP addresses, static IP addresses, and DNS names. These values define how the file service endpoints are presented to clients and how file server instances are resolved on the network. The File Service domain can be adjusted by editing the network configuration and adding or removing IP addresses as needed. The Active Directory domain is not treated as a simple post-deployment editable field because changing domain membership can disrupt authentication, permissions, and file-share access. The Active Directory username and Organizational Unit are part of the directory integration and domain-join configuration, but they are not the three standard settings identified for modification after the initial File Services configuration. Therefore, the three modifiable settings are Static IP addresses, Primary IP addresses, and DNS names. Reference topics: vSAN File Service, Edit File Service Domain, File Service Network Configuration, Active Directory Integration.

To deliver vSAN File Service for NFS shares in an Edge environment, the administrator must prepare the vSAN File Service network correctly. When a vSphere Distributed Switch is used, vSAN File Services are supported on DVS and require a dedicated distributed port group for vSAN File Services. During vSAN File Services enablement, MAC Learning and Forged Transmits are enabled for the provided DVS port group. If the design uses an NSX-based network, MAC Learning must be enabled on the provided NSX network entity from the NSX admin console, and the hosts and File Service nodes must be connected to the desired NSX network. For Edge-style network behavior, DVS 6.6.0 or later is required to support MAC Learning on the distributed port group, with ESX 6.7 or later. MAC Learning and Forged Transmits being disabled is therefore incorrect. Jumbo frames are not listed as a vSAN File Service requirement in this workflow. vSAN Witness functionality on each VMkernel is also unrelated; witness traffic applies to two-node or stretched-cluster quorum, not file-service delivery. Reference topics: vSAN File Service Network Considerations, DVS Port Group Requirements, NSX MAC Learning, Edge Networking.

Seven hosts per availability zone is required for this design. In a vSAN ESA stretched cluster, data components are distributed across two data sites, while a witness site provides quorum. The first requirement is a secondary level of resilience of FTT=2 using RAID-6 erasure coding. RAID-6 requires enough fault domains to place data and parity components while tolerating two failures. The second requirement is more restrictive: vSAN must be able to regain its prescribed level of resilience after a sustained host outage. This means the site must have enough remaining placement capacity to rebuild components and return objects to policy compliance after a host is lost. A six-host site can satisfy the RAID-6 placement minimum, but it does not provide the additional host needed to rebuild cleanly after a sustained host outage. Therefore, the design requires seven hosts in each availability zone. This produces fourteen data hosts across the stretched cluster, plus the witness. Reference topics: vSAN ESA Stretched Cluster Design, Secondary Level of Resilience, RAID-6 Erasure Coding, Availability Zone Host Count.

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 correct design is to use VMFS datastores on the existing Fibre Channel SAN as principal storage for each workload domain. VCF supports Fibre Channel storage as a principal storage model for workload domains, and FC-backed VMFS datastores integrate directly with vSphere storage operations, VCF Operations monitoring, datastore clusters, Storage DRS, and Storage Policy Based Management. Assigning multiple storage policies based on array and LUN performance tiers allows VM placement and operational control to reflect the service levels provided by the SAN. This aligns with large-scale VI best practices where block storage arrays provide resilient paths, LUN masking, zoning, multipathing, and consistent performance tiers. Option A fails because it limits FC use to the Management Domain and uses local disks for workload domains, which does not match the requirement to leverage enterprise FC SAN for workloads. Option C is invalid because an external FC SAN cannot be mounted as a vSAN datastore. Option D incorrectly routes workload storage through management-cluster vVols and does not match the requested VMFS-on-FC architecture. Reference topics: Fibre Channel Storage Model, VMFS Datastores, Principal Storage, SPBM, Datastore Clusters.

NFS must be used as principal storage because the hosts have no local storage available. vSAN OSA and vSAN ESA both require local storage devices on the ESX hosts to create the vSAN datastore, so neither can be selected as principal storage in this design. NVMe over RDMA is supported as a high-performance NVMe over Fabrics transport in vSphere, but in the VCF storage model it is treated as supplemental storage rather than principal storage for workload domain creation. Therefore, NVMe over RDMA cannot be the initial principal datastore used to build the Workload Domain. NFS is the valid principal storage option from the provided choices, and after the Workload Domain is created, NVMe over RDMA can be added as supplemental storage for additional performance or capacity use cases. This build order satisfies the lack of local disks, uses a supported principal storage type, and allows the NVMe over RDMA design requirement to be met after the domain exists. Reference topics: Principal Storage, Supplemental Storage, NFS Storage Model, NVMe over RDMA, VCF Workload Domain Storage Design.

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.

VMware Live Site Recovery uses VM readiness signals to control recovery sequencing between priority groups. Recovery Priority is used to start and validate higher-priority workloads before lower-priority workloads continue, which is important for application dependency chains such as identity services, databases, middleware, and application servers. A VM being registered or powered on does not prove that the guest operating system is usable. Similarly, final replication completion only confirms storage synchronization, not guest readiness. VMware Tools heartbeat provides a guest-level indication that the operating system has started and is responsive. This makes it the correct mechanism for determining that a recovery priority step has completed and that the recovery plan can continue to the next priority group. The “successfully recovered” state is the result of the recovery workflow, not the signal used to progress between priority groups. Reference topics: VMware Live Site Recovery, Recovery Plans, Recovery Priority, VMware Tools Heartbeat, Application Recovery Sequencing.

Cross-cluster capacity sharing, also known as vSAN datastore sharing or HCI Mesh, allows vSAN HCI clusters or vSAN storage clusters to share remote datastores with other vSAN HCI clusters or vSAN compute clusters. A required availability setting is to configure vSphere HA failure response for “Datastore with APD” on the client cluster to “Power off and restart VMs.” This ensures that if a remote vSAN datastore becomes unavailable to a host, vSphere HA can respond appropriately and restart affected virtual machines on hosts that can access the datastore. The latency option is incorrect because vSAN storage cluster guidance requires latency below five milliseconds between client and server ESX hosts, not a minimum of ten milliseconds. The VM object placement option is also incorrect because all objects that make up a VM must reside on the same datastore, not multiple datastores. Finally, client and server clusters must use compatible vSAN architectures; vSAN OSA and vSAN ESA cannot share datastores with each other. Reference topics: Cross-Cluster Capacity Sharing, vSAN Datastore Sharing, HCI Mesh, vSphere HA APD Response, vSAN OSA/ESA Compatibility.

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.

The two most relevant causes are insufficient vCenter permissions and incorrect DNS resolution. The VMware Live Recovery appliance must register with vCenter as a managed extension and service endpoint, so the account used during the Configure Appliance workflow must have the required vCenter privileges. A user that can authenticate but lacks registration or administration privileges can still cause the appliance registration to fail. DNS is equally critical because appliance registration depends on stable FQDN resolution, certificate validation, Lookup Service communication, and service endpoint registration. Forward and reverse DNS records must resolve correctly between the VMware Live Recovery appliance and vCenter Server. Deploying the appliance to a non-vSAN datastore is not the primary reason for vCenter registration failure. DHCP is not inherently invalid if the resulting address and DNS records are correct, though static addressing is usually preferred. A local Photon OS account on the VCSA is not the correct account type, but the direct technical issue is the lack of required vCenter permissions. Reference topics: vSAN Data Protection, VMware Live Recovery Appliance Registration, vCenter Permissions, DNS Forward and Reverse Resolution.

The required action is to deploy the VMware Live Recovery appliance. In VMware Cloud Foundation 9.0, vSAN Data Protection is powered by VMware Live Recovery and provides local virtual machine protection and remote virtual machine replication for supported vSAN ESA environments. The vSAN Services configuration workflow explicitly states that before vSAN Data Protection can be used, the VMware Live Recovery appliance must be deployed. This appliance provides the data protection control plane required for protection groups, native snapshots, recovery workflows, and replication-based protection. Enabling vSAN advanced options is not sufficient because those settings control cluster behaviors such as repair timers, read locality, thin swap, unmap, and rebalance. Data Services Manager is used for database/data-service lifecycle use cases, not vSAN VM data protection. vSphere Replication can be part of broader site-recovery scenarios, but it is not the required action to enable vSAN Data Protection from the vSAN services workflow. Reference topics: vSAN Data Protection, VMware Live Recovery Appliance, vSAN Services Configuration, Local VM Protection and Replication.

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.

Assigning different vSAN Storage Policies to each file share during creation satisfies the requirement because vSAN File Service allows each file share to be created with its own storage policy. The Create File Share workflow includes a Storage Policy selection, which controls how the file share’s underlying vSAN objects are protected and placed. This is the correct mechanism when each department requires distinct protection levels or placement rules. IP pools and file server bindings provide network endpoint capacity and service placement, but they do not define the protection level of file share data. Creating separate File Service clusters per department is unnecessary and operationally inefficient because file shares can be differentiated by policy within the same File Service deployment. vSphere Compute Policies influence compute placement, not vSAN object protection or file-share resilience. Therefore, the department-specific requirement is fulfilled directly by assigning the appropriate vSAN Storage Policy to each file share at creation time. Reference topics: vSAN File Service, Create File Share, Storage Policy, Placement and Protection Rules.