Which TWO actions are required to enable encrypted vSphere vMotion for all virtual machines in a cluster?
Trap 1: Configure a Key Management Server (KMS) for the cluster.
Incorrect: A KMS is required for VM encryption or encrypted vSAN, not for vMotion encryption.
Trap 2: Enable Storage DRS on the cluster.
Incorrect: Storage DRS is unrelated to vMotion encryption; it deals with storage load balancing.
Trap 3: Ensure all ESXi hosts in the cluster are joined to the same Active…
Incorrect: Active Directory domain membership is not required. Hosts use built-in certificates for vMotion encryption; domain membership is an alternative for certificate trust but not a requirement.
- A
Set the vMotion encryption policy to 'Encrypt all data' in the cluster settings.
Required: Setting 'Encrypt all data' in the cluster forces encryption for all vMotion migrations, ensuring data protection.
- B
Configure a Key Management Server (KMS) for the cluster.
Why wrong: Incorrect: A KMS is required for VM encryption or encrypted vSAN, not for vMotion encryption.
- C
Enable Storage DRS on the cluster.
Why wrong: Incorrect: Storage DRS is unrelated to vMotion encryption; it deals with storage load balancing.
- D
Ensure all ESXi hosts in the cluster are joined to the same Active Directory domain.
Why wrong: Incorrect: Active Directory domain membership is not required. Hosts use built-in certificates for vMotion encryption; domain membership is an alternative for certificate trust but not a requirement.
- E
Set the vMotion encryption policy to 'Encrypt when supported' in the cluster settings.
Why wrong: Incorrect: 'Encrypt when supported' only encrypts when both hosts support it, not enforcing encryption for all VMs.