3V0-23.25 Practice Questions

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.

vSAN HCI Cluster = A cluster that provides both compute and storage to Virtual Machines;

vSAN Storage Cluster = A vSAN cluster that provides disaggregated storage for vSAN and vSphere clusters;

vSAN Compute Cluster = A vSphere cluster that does not have local vSAN storage, but instead, it mounts a remote vSAN datastore;

vSAN Stretched Cluster = A vSAN Cluster topology that extends a single logical vSAN cluster across two availability zones. A vSAN stretched cluster can tolerate a site failure.

These mappings describe the primary vSAN storage models used in VMware Cloud Foundation 9.0. A vSAN HCI Cluster is the traditional hyperconverged model where the same cluster provides compute resources and contributes local storage devices to the vSAN datastore for running virtual machines. A vSAN Storage Cluster is a disaggregated storage model based on vSAN ESA; it provides storage capacity and performance to other vSAN or vSphere clusters instead of primarily running workloads itself. A vSAN Compute Cluster is a vSphere cluster that does not contribute local vSAN capacity. Instead, it consumes a remote datastore exported by a vSAN Storage Cluster, enabling compute and storage to scale separately. A vSAN Stretched Cluster extends a single logical vSAN cluster across two availability zones or sites and uses a witness to maintain quorum, allowing workloads to tolerate a full site failure. These distinctions are essential for choosing between HCI, disaggregated storage, remote storage consumption, and availability-zone resilience. Reference topics: vSAN HCI Cluster, vSAN Storage Cluster, vSAN Compute Cluster, vSAN Stretched Cluster, VCF Storage Models.

ESA evaluates available capacity and fault domains to satisfy policy compliance.

vSAN detects the failure and marks affected objects as non-compliant.

Resync completes and objects transition to Compliant status.

New components are instantiated on eligible capacity devices, and resync begins.

A failed NVMe device in a vSAN ESA cluster is handled as a storage pool device failure. vSAN first detects the failure and marks affected objects as non-compliant when their assigned storage policy requirements are no longer satisfied. ESA then evaluates available capacity and fault domains to determine whether replacement components can be placed in a way that restores compliance. If sufficient placement resources exist, vSAN creates new components on eligible capacity devices and begins resynchronization. After the resync completes, the affected objects transition back to Compliant status. The Repair Delay Timer is primarily associated with absent components, such as a host or device that may return, and is not the required step for a permanent NVMe failure. The administrator does not have to manually trigger Repair Objects Immediately for the normal automatic repair process. A full cluster rebalance is separate from repair and is not performed before rebuilding missing or degraded components. Reference topics: vSAN ESA Storage Pool Device Failure, Object Compliance, Automatic Reprotection, Resynchronization.

The requirement is to alternate the primary site every six months, which requires a disaster recovery design that can reverse protection direction after failover. Inventory mappings define how resources such as compute resources, folders, networks, and datastores map between the protected and recovery sites. Using “Prepare reverse mappings” during inventory mapping creation ensures that the same mapping structure can be used when the recovery site later becomes the protected site. After a failover or planned migration succeeds, VMware Live Site Recovery uses the re-protect operation to reverse the protection relationship. This makes the formerly recovered site the new protected source and prepares replication and recovery plans for failback or for the next scheduled site rotation. A test recovery plan validates recovery without changing the primary site. Extending the network can simplify workload mobility but is not required for reprotection. Reconfiguring vSAN Data Protection manually is not the Live Site Recovery workflow for reversing protected and recovery site roles. Reference topics: VMware Live Site Recovery, Inventory Mappings, Reverse Mappings, Recovery Plans, Reprotect.

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.

The administrator must create a datastore cluster from the three NFS datastores that are intended to host virtual machine workloads. The ISO datastore should not be included because datastore clusters should contain similar or interchangeable datastores used for the same purpose. All three NFS datastores must be available to each ESX host server so Storage DRS recommendations and VM placement are valid across the cluster. Storage DRS should be configured in Manual mode because the requirement states that migrations must occur only after administrator approval. Manual mode displays placement and migration recommendations but does not execute them automatically. The Storage DRS space threshold should be set to 50% so recommendations are generated when a datastore exceeds that utilization level. Setting the storage space utilization difference to 50% is not correct because that value controls the minimum difference between source and destination datastore utilization, not the trigger threshold itself. Fully Automated mode would violate the approval requirement by automatically applying migrations. Reference topics: Datastore Cluster Requirements, Storage DRS, Manual Automation Mode, Space Utilization Thresholds, NFS Datastores.

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.

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.