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

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.

The user account used by the application.

The Active Directory used by the application.

The password used by the application.

NFSv4.1 with Kerberos requires identity integration through Active Directory and a valid Kerberos-capable user credential. In vSphere, Kerberos authentication for NFS 4.1 uses Active Directory credentials so ESX can authenticate securely when mounting Kerberos-protected NFS datastores. The required inputs are the Active Directory domain, the user account, and the password associated with that account. The storage guide also states that when several ESX hosts access the same NFS 4.1 datastore, all hosts must use the same Active Directory credentials to ensure consistent access. The Organizational Unit is not the required credential element for datastore mounting. The DNS name of a Kerberos server may be resolved through Active Directory and DNS infrastructure, but it is not one of the required configuration values selected here. A “Kerberos Key Management Server” is not part of the vSphere NFSv4.1 Kerberos datastore configuration model. Therefore, the required options are the application’s user account, its Active Directory, and the account password. Reference topics: NFSv4.1 Datastores, Kerberos Authentication, Active Directory Credentials, Kerberos Security for NFS.

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.

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.

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.

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.

Supplemental storage is intended for adding storage capacity to an existing workload domain or cluster after the principal storage has already been deployed. Principal storage is the datastore used during workload domain or cluster creation and is normally used for live workload placement. Supplemental storage can be added later for additional workloads, templates, ISO images, backup data, or other data-at-rest requirements. In this scenario, the administrator specifically needs additional capacity for backup data and ISO images without changing or impacting the principal storage used for production workloads. Attaching additional NFS volumes or iSCSI datastores satisfies this requirement because both can be used as supplemental storage options in VCF. Migrating the Management Domain storage is unrelated and unnecessary. Increasing the existing VMFS principal storage allocation does not provide the requested separation between production and backup or ISO storage. Replacing all existing datastores with NVMe devices would be disruptive and does not match the supplemental-storage use case. Reference topics: Principal Storage, Supplemental Storage, NFS Supplemental Storage, iSCSI Supplemental Storage, Day-2 Storage Expansion.

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 correct mapping comes from the VCF 9.0 Principal and Supplemental Storage model. vSAN ESA is supported as principal storage for the Management Domain default cluster, Management Domain additional clusters, and VI Workload Domains. A vSAN Storage Cluster is not supported for the Management Domain default cluster because the initial management cluster requires a standard principal storage model, but it is supported as principal storage for Management Domain additional clusters and VI Workload Domains. Fibre Channel is supported as both principal and supplemental storage across all three domain or cluster categories, allowing either initial cluster creation or later datastore expansion. NFS v4.1 is supplemental-only across these categories. NFS can be principal only when using NFS v3; NFS v4.1 is used as supplemental storage after the domain or cluster exists. These statuses align with VCF’s distinction between principal storage, which is used during workload domain or cluster creation, and supplemental storage, which is added after creation for workloads or data-at-rest use cases. Reference topics: Storage Models, Principal Storage, Supplemental Storage, vSAN ESA, Storage Cluster, Fibre Channel, NFS.

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.

Four hosts are required to meet the 12 TB usable-capacity requirement after applying the protection policy, data reduction, reserves, and overhead. Each host contributes 8 TB raw capacity from two 4 TB NVMe devices. Three hosts provide 24 TB raw capacity, but once host rebuild reservation, 10% operational reserve, RAID-5 protection overhead, and 25% filesystem/object overhead are considered, the remaining effective usable capacity falls below the required 12 TB target. Four hosts provide 32 TB raw capacity. With vSAN ESA and FTT=1/RAID-5, vSAN uses erasure coding to improve capacity efficiency compared with mirroring. The vSAN sizing guidance states that RAID-5 with FTT=1 provides approximately 75% usable capacity before other reserves and overhead. Host Rebuild Reserve must also be planned so the cluster has enough free capacity to rebuild components after a host failure. After applying the expected 1.5 data reduction ratio and the required reserves, four hosts provide enough usable capacity while three hosts do not. Reference topics: vSAN ESA Capacity Sizing, RAID-5 Erasure Coding, Host Rebuild Reserve, Operations Reserve, vSAN Object Overhead.

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.

In vSAN Original Storage Architecture, a disk group consists of one flash cache device and one or more capacity devices. The cache device is a required component of the disk group, so a failed cache device cannot be replaced as an isolated drive while preserving the same disk group. The supported operational approach is to remove the affected disk group, physically replace the failed cache device, verify that ESX detects the new device, and then manually recreate the disk group using the replacement cache device and the appropriate capacity devices. The scenario states that vSAN has already completed resynchronization and that all objects are healthy and compliant, so removing the failed disk group no longer risks object noncompliance. Selecting Full Data Migration on a failed cache device is not the correct workflow because the cache failure affects the entire disk group. Simply inserting a replacement drive does not cause vSAN OSA to automatically rebuild the disk group. Reference topics: vSAN OSA Disk Groups, Replace a Cache Device, Remove Disk Group, Recreate Disk Group.

The approximate expected usable capacity is 40 TB. The cluster contains six hosts, each with two 4 TB NVMe disks, giving 48 TB of raw capacity. Because the policy uses FTT=1 with RAID-5 erasure coding, vSAN provides better capacity efficiency than mirroring. RAID-5 with FTT=1 typically uses approximately 1.33x overhead, leaving roughly 75% of raw capacity before additional reserves and data-reduction assumptions. The design also requires Host Rebuild Reservation, which reserves enough capacity to rebuild data after a host failure, and an Operational Reserve of 10% to support internal operations such as resynchronization and policy changes. The expected filesystem and object overhead of 25% further reduces available capacity, while the deduplication/compression ratio of 2 increases the effective usable capacity. After accounting for protection overhead, capacity reserves, operational overhead, and the stated data-reduction assumption, the closest expected usable value from the available choices is 40 TB. Reference topics: vSAN Capacity Sizing, RAID-5 Erasure Coding, Deduplication and Compression, Host Rebuild Reserve, Operational Reserve.

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.

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 available custom recovery steps are top-level commands, message prompts, and per-machine commands. VMware Live Site Recovery recovery plans operate like automated runbooks, and administrators can insert custom steps to match business continuity requirements. Broadcom TechDocs states that custom recovery steps can run commands or present messages to the user during a recovery. Command recovery steps are divided into two categories: top-level commands and per-virtual-machine commands. Top-level commands are inserted directly into the recovery plan and run on the VMware Live Site Recovery server. Per-machine commands are associated with individual recovered VMs and run before or after that VM is powered on, depending on placement in the workflow. Message prompts are interactive steps that pause the plan until an operator acknowledges the message, making them useful for manual validation, external approvals, or runbook checkpoints. IP reconfiguration is handled through recovery plan networking and guest customization, not as a custom step type. Writable storage snapshots are part of test recovery/storage behavior, not a custom recovery step. Reference topics: VMware Live Site Recovery Recovery Plans, Creating Custom Recovery Steps, Top-Level Commands, Message Prompts, Per-VM Commands.

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.

The minimum total number of nested fault domains is six. In a two-node vSAN design, site disaster tolerance is provided through host mirroring between the two data hosts, with a witness maintaining quorum. The requirement adds another layer: the solution must also survive a disk group or local storage failure in addition to a host failure. vSAN’s two-node host mirroring rule states that each data host must have at least three disk groups, or three disks in a storage pool, to use the rule. In ESA, the equivalent construct is disks in the storage pool rather than OSA-style disk groups. Because there are two data hosts, and each data host requires three nested placement units, the minimum total is 3 + 3 = 6 nested fault domains. Four would not meet the host-mirroring rule requirement, and two would only represent the two hosts without local storage fault isolation. Reference topics: vSAN Two-Node Cluster, Host Mirroring, Nested Fault Domains, vSAN ESA Storage Pool Placement.