3V0-23.25 Exam Dumps - VMware VCAP-Storage Questions and Answers

A witness host for a 2-node vSAN cluster must be external to the 2-node vSAN-enabled data cluster. The witness provides quorum and must be placed outside the protected data-node pair so that it can arbitrate availability during host or site failure. If the proposed witness host resides inside the 2-node vSAN enabled cluster, it is not eligible and therefore does not appear as an available selection during the replacement workflow. Having a VMkernel adapter configured with vSAN traffic enabled is required for witness communication, so that is not the cause of the issue. Connectivity to the data hosts is also expected and does not make the witness invalid. A witness host already assigned to another 2-node vSAN cluster is not necessarily disqualified because shared witness configurations are supported within scale and sizing limits. The core eligibility issue is that the witness host cannot be a member of the same 2-node vSAN cluster that it is intended to witness. Reference topics: 2-Node vSAN Cluster, Witness Host Placement, Replace Witness Host, Shared Witness Support.

The Live! vSphere Heavy Hitter VM dashboard is the correct place to identify which virtual machines are driving storage IOPS and disk throughput problems. In VCF Operations, heavy hitter dashboards are designed to isolate the consumers creating the highest demand on shared infrastructure resources. For storage troubleshooting, this dashboard identifies VMs producing significant I/O load, including IOPS and throughput. This is especially useful when a Fibre Channel datastore is reporting performance alerts because the datastore itself may show contention, but the root cause is often one or more high-demand VMs consuming disproportionate backend storage resources. The vSAN Health dashboard is not correct because the affected datastore is Fibre Channel, not vSAN. The vSphere Storage Inventory dashboard is useful for topology and inventory visibility, but it is not the best view for identifying the VM-level consumers causing IOPS and throughput pressure. The Storage Operations page is broader and less targeted than the Live heavy hitter view. Reference topics: VCF Operations Performance Dashboards, Storage Heavy Hitters, VM IOPS and Throughput Troubleshooting.

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.

Option B satisfies every requirement because it separates management and workload storage onto dedicated Fibre Channel-backed VMFS datastores while relying on array-based encryption at rest. This avoids VMware native encryption and vSAN-specific encryption mechanisms, matching the regulatory requirement. Fibre Channel is a supported non-vSAN storage architecture for VCF and provides enterprise block storage with multipathing, LUN masking, zoning, and consistent datastore presentation. SPBM storage policies allow storage placement and compliance to align with array and LUN characteristics, supporting automated placement and operational consistency. For scalable file-based workloads, NFS v4.1 is appropriate as supplemental file storage, and Kerberos privacy mode provides authentication, integrity, and encryption in transit for NFS traffic. Restricting cross-domain datastore access preserves strict management/workload segregation. Option A does not properly address file workload scaling or NFS encryption. Option C violates the requirement for array-based encryption by using VMware VM encryption. Option D violates segregation by sharing one NAS platform across domains and relies on application-level encryption instead of the mandated storage architecture. Reference topics: Fibre Channel Storage Model, SPBM, Array-Based Encryption, NFS v4.1 Kerberos, Workload Domain Storage Segregation.

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.

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 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.

With vSAN ESA and Failures to tolerate set to 1 using RAID-5/6 Erasure Coding, vSAN creates an optimized RAID-5 format based on the number of available fault domains. The documentation states that if five or fewer fault domains are available, ESA lists three components for RAID-5. This corresponds to a 2+1 erasure-coded layout, where two data components and one parity component are created. The stretched-cluster setting affects the site disaster tolerance rule, while the stated Failures to tolerate rule with erasure coding defines the local object protection method. The policy note also states that in a vSAN stretched cluster, the RAID-5/6 erasure coding failure tolerance method applies to the Site disaster tolerance setting. Given the answer choices, the ESA optimized RAID-5 component layout that matches FTT=1 erasure coding is three components. One or two components would not provide erasure-coded protection, and four components represents a generic RAID-5 fault-domain requirement rather than the ESA optimized component count shown in placement details. Reference topics: vSAN ESA RAID-5, Failures to Tolerate, Erasure Coding, Stretched Cluster Storage Policy.

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 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.