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

Site A = Data Site; Site B = Witness Site; Site C = Data Site; Site A ↔ Site C = Layer 3, RTT < 5 ms; Site A ↔ Site B = Layer 3, RTT < 200 ms; Site B ↔ Site C = Layer 3, RTT < 200 ms

Site A and Site C should be the data sites because Site A hosts production services and Site C has been commissioned to replace the capacity-constrained Site B. Site B should be used as the witness site because it has no space for additional physical hosts, and a vSAN witness appliance does not run workload VMs. A vSAN Stretched Cluster requires two availability zones for data nodes and a third site for the witness appliance. The data-site-to-data-site connection carries synchronous vSAN data traffic and must meet less than 5 ms RTT. The witness site carries metadata traffic only, so the data-site-to-witness links support higher latency, with less than 200 ms RTT for up to 10 hosts per site. Because the requirement specifically calls out minimizing disruption from STP, Layer 3 is the preferred network type between sites. VMware states that Layer 3 helps avoid STP redirecting traffic across undesirable links, such as constrained witness links. Reference topics: vSAN Stretched Cluster Network Design, Data Site and Witness Site Placement, Layer 3 Recommendation, RTT Requirements.

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 correct steps are to create an NFS export on the storage array and mount the NFS datastore on each ESX host in the cluster. NFS datastore creation begins on the storage system, where the storage administrator creates and exports the NFS volume or directory with the required access permissions for the ESX hosts. After the export exists, vSphere mounts that export as a datastore. For a clustered VCF workload domain, the datastore must be mounted consistently across all ESX hosts in the cluster so that HA, DRS, vMotion, and VM placement can operate correctly. Mounting the datastore on only one host would create inconsistent datastore accessibility and could prevent workloads from moving or restarting on other hosts. “Attach NFS as a secondary datastore” is not the correct procedural step; the datastore is created and mounted as a vSphere datastore. Configuring vSAN is irrelevant because the workload domain already uses NFS storage and the task is to add another NFS datastore. Reference topics: NFS Datastore Creation, NFS Export, Host Accessibility, VCF Workload Domain Storage Administration.

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.

The support status is based on 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 Virtual Infrastructure Workload Domains. A vSAN Storage Cluster is not supported for the Management Domain default cluster, but it is supported as principal storage for Management Domain additional clusters and VI Workload Domains. NFS storage supports principal and supplemental usage when the protocol is NFS v3; the table states “Principal (NFS v3)” and “Supplemental (NFSv3 and NFSv4.1)” across all three domain categories, so NFS v3 maps to Both. iSCSI is supported only as supplemental storage across the Management Domain default cluster, Management Domain additional clusters, and VI Workload Domains. This follows the VCF distinction where principal storage is used during workload domain or cluster creation, while supplemental storage is added after creation for workloads or data-at-rest use cases such as templates, backups, and ISO images. Reference topics: Storage Models, Principal Storage, Supplemental Storage, vSAN ESA, vSAN Storage Cluster, NFS, iSCSI.

Deploy ESX at 9.x

Deploy vCenter 9.x

Create Storage and General dvS

Configure VMkernel Binding for the NVMe over TCP Adapter

Add Software NVMe over TCP Adapters

Import the workload domain to VCF

The correct sequence starts by preparing the vSphere environment that will later be imported into VMware Cloud Foundation. ESX 9.x must be deployed first on the six blade hosts because the hosts provide the compute foundation for the workload domain. After the hosts are available, vCenter 9.x is deployed to manage the cluster and provide the required vSphere inventory. The two distributed switches are then created: one for storage isolation and one for general host and workload traffic. Because the external array supports NVMe/TCP only and multipathing is required, VMkernel binding must be configured for the NVMe over TCP adapter before the software NVMe over TCP adapters are added. This ensures the NVMe/TCP storage paths are correctly associated with the intended storage network. After the software NVMe over TCP adapters are created and the hosts can access the external storage, the prepared workload domain can be imported into the existing VCF environment. Reference topics: NVMe over TCP Configuration, VMkernel Binding, Software NVMe/TCP Adapters, Existing vCenter Import, VCF Workload Domain Import.

The workload domain should use Fibre Channel as principal storage because the existing five hosts already have resilient HBAs and are connected to a dedicated, highly resilient storage area network. The third-party block storage is also stated to have sufficient scale, capacity, and IOPS for the new workload requirements only, so it should be reused where it directly fits: the VI workload domain. VMware Cloud Foundation supports Fibre Channel as both principal and supplemental storage for VI workload domains. The management domain should use VMware vSAN as principal storage because the four new servers are being purchased for the management domain, and the existing block storage is not sized for management workloads. vSAN is a native VCF principal storage model for management domains and provides automated deployment, policy-based management, lifecycle integration, and integrated operations. iSCSI is not the right answer because the scenario describes Fibre Channel SAN connectivity and HBAs, not an iSCSI design. vSAN for the workload domain would also fail the reuse requirement because it would ignore the existing block storage investment. Reference topics: Principal Storage, Fibre Channel Storage Model, vSAN Storage Model, Management Domain Storage.