Immutable snapshots are intended to provide hardened recovery points for cyber-recovery scenarios.
In vSAN Data Protection, immutability is enabled at the protection group level. Once enabled, snapshots are read-only recovery points that cannot be modified or deleted, even by an attacker with administrative privileges. This immutability model imposes operational restrictions. A VM with immutable snapshots should not have its virtual hardware changed because hardware changes can alter the VM configuration state associated with protected recovery points. In addition, a protection group cannot be configured as both replicated and immutable, because replication and immutable local snapshot protection are separate protection behaviors with different lifecycle and retention handling.
The statement that a VM cannot be part of multiple protection groups is not the specific limitation tested here. The number of snapshot schedules is not limited to seven by this requirement. Virtual hardware version 10 is also not the controlling condition for immutable snapshot configuration in this context. Reference topics: vSAN Data Protection, Immutable Snapshots, Protection Groups, Cyber- Recovery Snapshot Restrictions.

The administrator must validate that the vSphere Native Key Provider has been backed up. When a Native Key Provider is created, vCenter pushes the key provider configuration to clustered ESX hosts, but the provider is not usable for encryption tasks until it has been backed up. The documentation states that after adding a Native Key Provider, it appears as not backed up, and that it must be backed up before use. The backup process changes the provider status from Not Backed Up, to Warning while vCenter propagates information to hosts, and then to Active when the information has been pushed to all hosts. A TPM 2.0 device is not required when using Native Key Provider with default settings, although TPM can provide enhanced security and can optionally be enforced. Crypto Safe Mode and disabling Secure Boot are not prerequisites for enabling vSAN Data-at-Rest Encryption with NKP. Therefore, the validation step is to confirm that the NKP backup has been created and the provider is active on the hosts. Reference topics: vSphere Native Key Provider, Back Up Native Key Provider, vSAN Data-at-Rest Encryption, Key Provider Availability.

Option D is the only design that uses supported non-vSAN storage models while matching the workload characteristics. VMFS over Fibre Channel is a supported enterprise block-storage option for the Management Domain and provides shared, resilient storage with SAN fabric pathing, zoning, LUN masking, and multipathing. Production requires low-latency block storage, and VMFS over NVMe/FC aligns with that requirement by using NVMe over Fibre Channel transport for high-performance block access. Non-production requires high-capacity file-based storage, and NFS v4.1 is the supported file- based option listed in the design. Option A is invalid because SMB is not a supported vSphere datastore protocol for VCF workload domain storage. Option B fails because local VMFS datastores do not provide the required shared storage model for a VCF Management Domain, and iSCSI is not presented as the complete best-fit block-storage design in the choices. Option C violates the explicit non-vSAN requirement by using vSAN ESA, vSAN HCI Mesh, and vSAN File Services. Reference topics:
Supported Non-vSAN Storage, Fibre Channel Storage Model, NVMe/FC, NFS Storage Model, Principal and Supplemental Storage.