How does the design need to be changed to support the new requirement?

The architect of a multi-site VMware Cloud Foundation solution is tasked with ensuring that the prerequisites for vSAN data at rest encryption have been achieved. The existing design calls for use of the vSphere Native Key Provider. NSX-T is configured with Federation, and both sites benefit from a stretched TO and T1 network topology.

A new security policy requires the use of vSphere Virtual Machine encryption, in addition to the at-rest encryption already configured. During a failover test from Site-A to Site-B using Site Recovery Manager, the virtual machines were unable to power-on.

How does the design need to be changed to support the new requirement?
A . Use a third-party KMS solution that allows for key replication.
B . Use a third-party KMS solution at each site.
C . Ensure that a TPM 2.0 certified module is installed on all ESXi hosts at Site-B.
D . Ensure that the Site Recovery Manager service account has Cryptographer ReadKeyServerslnfo privileges.

View Answer

Answer: A

Explanation:

This is because according to VMware documentation1, vSphere Native Key Provider (NKP) is a simple key management solution that does not support key replication across sites or clusters. It also does not support vSphere Virtual Machine encryption which requires a third-party KMS solution2. Therefore, to enable both vSAN data at rest encryption and vSphere Virtual Machine encryption in a multi-site VCF solution, you need to use a third-party KMS solution that allows for key replication across sites.

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.security.doc/GUID-54B9FBA2-FDB1-400B-A6AE-81BF3AC9DF97.html