Refer to the exhibit. An administrator is tasked with adding new capacity to an existing software- defined data center (SDDC). - The SDDC currently hosts two vSphere clusters (ClusterA and ClusterB) w

If the 'evc1' VM has its own Enhanced vMotion Compatibility (EVC) setting configured at a generation higher than the target Clusters A or B, disabling this VM-level EVC allows the VM to adopt the EVC baseline of the cluster it is powered on in, enabling broader migration.

While a reboot restarts the VM, a full power cycle (power off followed by power on) is typically required to apply fundamental CPU feature changes or EVC settings by resetting the virtual CPU mask.

Configuring the VM's EVC to Intel Skylake would raise its CPU compatibility requirements, further restricting its ability to migrate to older or less capable Clusters A or B, which is counter to the goal of enabling broad migration.

Any changes to a virtual machine's CPU compatibility or EVC configuration, such as disabling VM-level EVC, require the VM to be powered off and then powered back on for the new virtual CPU mask to take effect.

To support live migration of virtual machines across clusters with different physical CPU generations, including the new Intel Skylake hosts, all vSphere clusters (A, B, and the new hosts) must be configured with a consistent, lowest common denominator EVC baseline.

While powering off the VM would be a necessary intermediate step to apply EVC changes, it is not one of the final three steps to support the functionality, as the VM must be powered back on to be operational and migratable.