2V0-21.23 Question 43
Single answerAn organization is planning to implement a vSphere cluster with vSphere Enhanced vMotion Compatibility (EVC) to support vMotion across different generations of CPUs. However, during the configuration process, a host fails to join the EVC cluster. What could be a possible reason for the failure?
- A
The host has vSphere DRS disabled.
- B
The host's CPU does not support the required EVC baseline.
- C
The EVC mode is already enabled on the vCenter Server instance.
- D
The host is running virtual machines that are powered on.
Show answer and explanation
Correct answer: B
Explanation
EVC ensures that all hosts in a cluster present a consistent CPU feature set to virtual machines, enabling seamless vMotion between hosts with different CPU generations. If a host’s CPU is not compatible with the EVC baseline configured for the cluster, the host cannot join the cluster. This ensures vMotion operations remain reliable and consistent across the environment. The other options either describe unrelated features or misinterpret the requirements for EVC configuration.
- A. Incorrect.
vSphere DRS is not a requirement for enabling EVC. While DRS can be used in conjunction with EVC for load balancing, its status does not affect EVC configuration.
- B. Correct.
EVC relies on a specific CPU baseline for compatibility. If a host’s CPU does not meet the required EVC baseline, it will fail to join the EVC cluster.
- C. Incorrect.
EVC mode is configured at the cluster level, not at the vCenter Server level. This statement is incorrect and does not explain why a host cannot join an EVC cluster.
- D. Incorrect.
While powered-on virtual machines might temporarily prevent EVC mode changes, they do not stop a host from joining an EVC-enabled cluster. The host can still join the cluster, but certain actions might be restricted.