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.

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

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.

A shallow rekey operation rotates only the Key Encryption Key (KEK). In vSAN Data-at-Rest Encryption, vCenter obtains or generates the KEK through the configured key provider, while ESX hosts use Data Encryption Keys (DEKs) to encrypt the actual disk or object data. The KEK is used to protect, or wrap, those DEKs. When a shallow rekey is performed, the underlying encrypted data does not need to be rewritten because the DEKs remain the same; only the KEK changes, and the existing DEKs are re-encrypted with the new KEK. This is why shallow rekey is faster and less disruptive than a deep rekey. A deep rekey generates both a new KEK and new DEKs, requiring re-encryption of data. The Host Key is used for encrypted core dumps, not datastore data encryption. Key Derivation Key is not the key rotated in this vSAN shallow rekey workflow. Reference topics: vSAN Data-at-Rest Encryption, Generate New Encryption Keys, Shallow Rekey, Deep Rekey, KEK and DEK lifecycle.

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.

The required action is to deploy the VMware Live Recovery appliance. In VMware Cloud Foundation 9.0, vSAN Data Protection is powered by VMware Live Recovery and provides local virtual machine protection and remote virtual machine replication for supported vSAN ESA environments. The vSAN Services configuration workflow explicitly states that before vSAN Data Protection can be used, the VMware Live Recovery appliance must be deployed. This appliance provides the data protection control plane required for protection groups, native snapshots, recovery workflows, and replication-based protection. Enabling vSAN advanced options is not sufficient because those settings control cluster behaviors such as repair timers, read locality, thin swap, unmap, and rebalance. Data Services Manager is used for database/data-service lifecycle use cases, not vSAN VM data protection. vSphere Replication can be part of broader site-recovery scenarios, but it is not the required action to enable vSAN Data Protection from the vSAN services workflow. Reference topics: vSAN Data Protection, VMware Live Recovery Appliance, vSAN Services Configuration, Local VM Protection and Replication.

When vertically scaling a vSAN ESA cluster, adding the same model and capacity drives helps preserve a balanced and predictable cluster design. vSAN works best when hosts use uniform storage configurations. The guidance states that unbalanced host configurations reduce predictability of storage performance because vSAN does not store the same number of components on each host, can introduce different maintenance procedures, and can reduce performance on hosts with smaller or different device types. In ESA, each storage device contributes both capacity and performance through the storage pool model, so mixing device models, endurance classes, or capacities can create uneven consumption and inconsistent backend behavior. Using the same drive model and capacity across hosts improves capacity symmetry, keeps maintenance and replacement procedures consistent, and makes performance planning more predictable. The cache-drive option is incorrect because ESA is single-tier and does not use separate cache and capacity tiers. Equal cache and capacity tiers apply to OSA-style thinking, not ESA. vSAN File Services being configured does not drive the requirement to use identical drives. Reference topics: vSAN ESA Storage Pool Design, Balanced and Unbalanced Cluster Configuration, ESA Device Performance, Vertical Scaling.

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.

The extended resync behavior is best explained by deduplication and compression in a vSAN OSA design. In vSAN OSA, deduplication and compression are enabled at the cluster level but applied on a disk-group basis. The documentation states that deduplication occurs inline when data is written back from the cache tier to the capacity tier, and compression is then applied as data moves from cache to capacity. During resynchronization, vSAN must read, rewrite, deduplicate, compress, and destage data through this disk-group architecture. That additional processing can extend resync duration even when the physical network and hardware are healthy. “Ensure Accessibility” does not trigger a full component migration; it evacuates only enough data to maintain object accessibility and may leave objects temporarily noncompliant. The number of disk groups is not inherently the cause, and NVMe cache devices are not automatically limiting throughput simply because they are used in the cache tier. The key differentiator in the scenario is that deduplication and compression are enabled while heavy resync activity is occurring. Reference topics: vSAN OSA Deduplication and Compression, Disk Group Scope, Cache-to-Capacity Destaging, Maintenance Mode, Resynchronization.