2V0-13-25 Practice Questions

To meet all requirements, the administrator must configure Storage DRS (SDRS) correctly. First, SDRS requires that all datastores in the cluster be accessible by all ESXi hosts, making option E mandatory. Second, the administrator must create a Datastore Cluster containing only the three workload NFS datastores (option C), excluding the ISO datastore to prevent workload VMs from being placed there. Third, to trigger migration recommendations when a datastore reaches 50% utilization, the SDRS space threshold must be explicitly set to 50% (option A). Finally, to ensure VMs are placed automatically during provisioning (via recommendation acceptance) but migrated only after administrator approval, the Datastore Cluster must be configured with Manual Storage DRS (option F), which generates recommendations rather than executing them automatically.

B. Setting the utilization difference to 50% triggers migrations only when the difference between datastores is 50%, not when a single datastore reaches 50% capacity.

D. Fully Automated Storage DRS would execute migrations automatically without administrator approval, violating the explicit requirement for manual approval.

G. Including all four datastores would mix the ISO datastore with workload datastores, leading to inappropriate placement of workload VMs on the ISO datastore.

VMware vSphere 8.0 Documentation

"Creating a Datastore Cluster

" VMware

2023

Section: Storage DRS Prerequisites and Configuration.

VMware vSphere 8.0 Documentation

"Storage DRS Automation Levels

" VMware

2023

Section: Manual vs. Fully Automated SDRS.

Option B perfectly aligns with all technical and regulatory constraints for this VMware Cloud Foundation design. By utilizing dedicated Fibre Channel arrays with array-based encryption, it satisfies both the strict domain segregation requirement and the mandate for hardware-level data-at-rest encryption, explicitly avoiding vSAN or VMware native encryption mechanisms. The use of Storage Policy Based Management (SPBM) ensures automated VM placement and maintains operational integrity with VCF Operations by abstracting storage capabilities. Furthermore, implementing NFS v4.1 with Kerberos provides robust, native data-in-transit encryption specifically tailored for scalable file-based workloads in the workload domain. This comprehensive approach fulfills the transit security requirements while maintaining strict cross-domain isolation, ensuring compliance with the agency's stringent security policies.

A: Encrypted VLANs are not a standard vSphere storage encryption mechanism. iSCSI SEDs lack native file-based workload scaling and in-transit encryption capabilities provided by NFS v4.1 with Kerberos.

C: Explicitly violates the design requirements by utilizing VMware native VM-level encryption (NKP) instead of array-based encryption. Additionally, manual allocation directly contradicts the automated VM placement requirement.

D: Sharing a unified NAS across management and workload domains violates the strict data segregation requirement. Furthermore, application-level encryption fails the mandate for storage array-based data-at-rest encryption.

1. VMware vSphere 8.0 Product Documentation. vSphere Storage Guide. Section: "NFS Storage" -> "Using Kerberos for NFS 4.1". (Details the use of AES-256 encryption for data-in-transit over NFS v4.1).

2. VMware Cloud Foundation 5.x Design Guide. Section: "Storage Design for the Workload Domain". (Covers the use of Fibre Channel and NFS as principal/supplemental storage

SPBM for automated placement

and physical segregation of domains).

3. VMware vSphere 8.0 Product Documentation. vSphere Security Guide. Section: "Data at Rest Encryption". (Differentiates between vSphere Native Key Provider/VM Encryption and hardware-based Self-Encrypting Drives/Array-based encryption).

In VMware vSphere, Storage Policy Based Management (SPBM) governs how storage policies are applied to Virtual Machines. When a vSAN administrator manually modifies an existing, assigned VM storage policy (such as changing the "Failures to tolerate" rule from RAID-5 to RAID-6), the underlying storage objects are not automatically reconfigured by the mere act of saving the policy edit. Instead, the compliance status of the associated VMs immediately changes to "Out of Date." To instantiate the new RAID-6 configuration on the vSAN ESA datastore, the administrator must explicitly reapply the storage policy to the affected VMs. Once reapplied, vSAN evaluates the 6-node cluster's capacity and initiates the component resynchronization to meet the new FTT=2 requirements.

B: SPBM policies are vCenter-wide and not rejected during editing based on cluster size. The policy saves successfully, but VMs become non-compliant if requirements cannot be met.

C: When reapplied, vSAN processes object reconfigurations concurrently across the cluster, managed by resync throttling mechanisms, rather than strictly applying them serially to one VM at a time.

D: The 60-minute delay refers to the vSAN Object Repair Timer (CLOMRepairDelay), which is triggered by unexpected host or component failures, not by administrative storage policy changes.

1. VMware vSphere 8.0 Product Documentation

vSphere Storage Guide

Section: "Storage Policy Based Management" > "Edit or Clone a VM Storage Policy". (Specifically notes: "Until you reapply the policy

the compliance status of the virtual machine is Out of Date. You must reapply the policy to update the virtual machines.")

2. VMware vSAN 8.0 Administrator Guide

Section: "Managing Virtual Machine Storage Policies" > "Changing VM Storage Policies". (Details the requirement to trigger a reapply task to initiate object reconfiguration).

3. VMware vSAN 8.0 Monitoring and Troubleshooting Guide

Section: "vSAN Cluster Monitoring" > "Changing the Default Object Repair Timer". (Defines the default 60-minute delay for absent components

invalidating Option D).

vSAN File Services integrates directly with Storage Policy Based Management (SPBM). When an administrator creates a file share, they can assign a specific vSAN Storage Policy to that individual share. This policy dictates the protection level (such as Failures to Tolerate and RAID configuration) and placement rules for the underlying objects that make up the file share. Therefore, to satisfy the requirement of distinct protection levels and placement rules per department, the architect simply needs to assign the appropriate vSAN Storage Policy to each department's file share during its creation. This approach provides granular control over storage characteristics without requiring separate clusters or complex network configurations.

A: IP pools are used for network configuration of the file service VMs, not for assigning storage policies to individual shares.

B: Creating individual File Service clusters per department is unnecessary and adds administrative overhead, as policies can be applied per share.

C: vSphere Compute Policies apply to VM placement on hosts, not to the storage protection levels of vSAN file shares.

VMware vSAN 8.0 Administration Guide

Chapter 10: vSAN File Service

Section: "Create a File Share".

VMware vSAN 8.0 Design Guide

Section: "vSAN File Services Architecture".

To mount a remote vSAN datastore using vSAN HCI Mesh (or Cross-Cluster Capacity Sharing), the client cluster (the cluster mounting the datastore) must be configured as a vSAN compute cluster. This requires vSAN to be enabled on the client cluster, even if it does not have any local storage devices contributing to a local vSAN datastore. Once vSAN is enabled on the compute-only cluster, the Datastore Management option becomes available, allowing the administrator to mount the remote vSAN datastore from the vSAN ESA cluster.

- A: vSAN HCI Mesh supports sharing datastores across different clusters within the same vCenter Server; they do not need to be in different VCF Workload Domains.

- C: There is no strict 80% free space prerequisite on the remote vSAN storage cluster to simply mount the datastore.

- D: A vSphere compute cluster can mount a remote vSAN datastore with as few as two or three hosts; a fourth host is not a prerequisite.

- VMware vSAN 8.0 Administrator Guide

Section: "Mounting Remote vSAN Datastores" and "Prerequisites for HCI Mesh".

- VMware vSphere 8.0 Documentation

"Configuring a vSAN Compute Cluster".

===QUESTIONID:qxa2vc4p9

The official VMware procedure for manually restarting a vSAN cluster involves several distinct phases. The three valid steps from your provided image are:

1. Exit all hosts from maintenance mode so they can actively participate in forming the cluster.
2. Run the python reboot helper script only on one ESXi host (reboot_helper.py recover) to safely orchestrate the rebuild from a single node and prevent multi-host conflicts.
3. Enable cluster member updates from vCenter Server on all ESXi hosts. After the cluster has successfully recovered, you must run esxcfg-advcfg -s 0 /VSAN/IgnoreClusterMemberListUpdates on every host. This is the mandatory final step to re-enable normal vCenter updates across the cluster.

VMware vSphere 8.0 Documentation, vSAN Administration Guide, Section: "Restart the vSAN Cluster Manually". (Details the exact procedure, including the final instruction to re-enable vCenter cluster member list updates on all hosts once recovery is complete).

VMware vSphere 7.0 Documentation, vSAN Administration Guide, Chapter: "Shut Down and Restart the vSAN Cluster", Section: "Manually Restart the vSAN Cluster".

To import an existing brownfield environment into VMware Cloud Foundation (VCF) as a Workload Domain, the foundational infrastructure must be fully established and functional beforehand. The logical progression begins at the host level by deploying ESXi. A vCenter Server must then be deployed to manage the hosts and enable cluster-level configurations. Networking is configured next by establishing the required Distributed Virtual Switches (dVS) to isolate storage and general traffic. Once the network is operational, Software NVMe over TCP Adapters are added to the hosts. To fulfill the multi-pathing requirements over the storage dVS, the dedicated VMkernel ports are bound to the newly added NVMe/TCP adapters. Finally, with compute, network, and shared storage validated, the configured cluster is imported into VCF.

VMware, "vSphere Storage Guide," Chapter: VMware NVMe Storage Concepts and Requirements. (Details the prerequisites of configuring networking and adding software NVMe adapters before establishing VMkernel bindings for multipathing).

VMware, "VMware Cloud Foundation Administration Guide," Chapter: Importing an Existing vSphere Infrastructure. (Outlines the strict sequence of preparing ESXi, vCenter, networking, and shared storage prior to executing the VCF import process).

VMware Cloud Foundation (VCF) categorizes storage configurations into principal storage (required during workload domain or cluster creation) and supplemental storage (provisioned post-deployment). vSAN ESA is fully supported as the principal storage for the Management Workload Domain (WLD) default cluster, additional management clusters, and Virtual Infrastructure (VI) WLDs. A disaggregated vSAN Storage Cluster is not supported for the initial Management WLD default cluster since the initial cluster mandates a localized standard principal storage architecture, but it operates as principal storage for subsequent Management WLD clusters and VI WLDs. Fibre Channel uniquely acts as both principal and supplemental storage across all three domain categories. NFS v4.1 functions strictly as supplemental storage across all domains.

Broadcom TechDocs, VMware Cloud Foundation Concepts, "Storage Models" (v9.1), August 2026. (Backs the distinction between principal and supplemental storage configurations).

Dell/VMware InfoHub, Architecture Guide—VMware Cloud Foundation 5.1 on VxRail, "Storage Options," Table 15. (Backs vSAN ESA support as principal storage across Management and VI WLDs).

VMware Docs, vSAN FAQs, May 2026. (Backs the limitation that vSAN Storage Clusters are not supported as principal storage for the initial management domain cluster).

McDonald, Jonathan. "Converging VMware vSphere to VMware Cloud Foundation 9.0: The Top 10 Questions Answered," VMware Cloud Foundation Blog, April 16, 2026. (Backs Fibre Channel as a dual-role storage option and NFS restrictions).

In a VMware vSphere and Cloud Foundation environment, a Datastore Cluster aggregates datastores to enable Storage DRS resource allocation policies. LUN Masking is a storage-array-level security control dictating which host WWNs can view specific LUNs. The SAN Fabric provides the high-speed, dedicated Fibre Channel network connecting servers to storage arrays. A Host Bus Adapter (HBA) is the physical interface card in the ESXi host granting it physical access to the SAN. A Datastore serves as the logical storage container for virtual machine files (VMDKs, logs, configs). Zoning is a switch-level fabric security process controlling which specific SAN nodes (initiators and targets) are permitted to communicate with one another.

VMware Inc. vSphere Storage - ESXi 8.0, vCenter Server 8.0. VMware Official Documentation. Section: "Understanding Fibre Channel SANs" & "Working with Datastores", pp. 24-28, 145-148.

VMware Inc. vSphere Resource Management - ESXi 8.0, vCenter Server 8.0. VMware Official Documentation. Section: "Using Datastore Clusters", pp. 112-115.

EMC Corporation / Dell Technologies. Introduction to Storage Area Networks. Academic Courseware / Technical Publications. Section 3: SAN Security (Zoning and LUN Masking).

VMware Kubernetes Service (VKS) leverages the vSphere Container Storage Interface (CSI) plug-in to manage and provision persistent volumes (PVs). The vSphere CSI officially supports creating Static Persistent Volumes from pre-provisioned infrastructure storage. It enables dynamic resizing through both Online Volume Expansion (expanding a volume currently attached to a running pod) and Offline Volume Expansion (expanding a detached volume). Recent VCF updates also introduce 4kn Support for advanced format drives on VMFS-local, vSAN, and NFS datastores, and the ability to provision a Full Clone from Volume Snapshot. Conversely, Storage DRS and Flash Read Cache are not supported for CSI persistent volumes, and Storage vMotion with attached persistent volumes is natively restricted.

Broadcom TechDocs: "Storage for VKS Clusters." VMware Cloud Foundation 9.0 Documentation: vSphere Supervisor Concepts. (Document Identifier: storage-for-tanzu-kubernetes-grid-clusters.html). This document confirms that the vSphere CSI supports "Full Clone from Volume Snapshot", "4kn Support", "Static Persistent Volume", "Offline Volume Expansion", and "Online Volume Expansion".

Broadcom TechDocs: "Persistent Volume Expansion for TKG Service Clusters." VMware vSphere 8.0 Documentation: Managing Storage. (Document Identifier: persistent-volume-expansion-for-tkg-service-clusters.html). This section validates that Supervisor clusters natively support both offline and online volume expansions for block volumes.

Broadcom TechDocs: "Dynamic Storage." Tanzu Kubernetes Grid 2.5 Documentation: Workload Clusters Storage. (Document Identifier: workload-clusters-storage.html). This documentation explicitly confirms the architectural limitation that "vSphere CSI does not support Storage DRS."