Which action specifically supports performing live migration of VMs by isolating migration traffic?

Which action specifically supports performing live migration of VMs by isolating migration traffic?

• A. Tag the live migration VLAN on the trunk to the new servers.
• B. Correctly size and provision NFS LUNs on the new storage.
• C. Zone HBAs.
• D. Prep mirror VMs on new hosts for data migration.

Answer: (A)

Isolating live migration traffic by using a dedicated VLAN on the trunk to the new servers ensures that the memory and state data moved during a live migration travels on its own network path, free from contention with regular VM data and management traffic. By tagging the live migration VLAN on the trunk, the switch and NICs know which traffic belongs to vMotion and keep it isolated, which improves migration performance and reduces the chance of interference or security concerns from other network loads. The other options don’t target the migration network specifically: sizing NFS LUNs pertains to storage capacity and performance for VM data, not the path used for live migration; zoning HBAs controls access to the Fibre Channel storage fabric, not the isolation of IP-based migration traffic; and prep-mirroring VMs on new hosts is about creating standby or synchronized copies, not about segregating the vMotion traffic.

Isolating live migration traffic by using a dedicated VLAN on the trunk to the new servers ensures that the memory and state data moved during a live migration travels on its own network path, free from contention with regular VM data and management traffic. By tagging the live migration VLAN on the trunk, the switch and NICs know which traffic belongs to vMotion and keep it isolated, which improves migration performance and reduces the chance of interference or security concerns from other network loads.

The other options don’t target the migration network specifically: sizing NFS LUNs pertains to storage capacity and performance for VM data, not the path used for live migration; zoning HBAs controls access to the Fibre Channel storage fabric, not the isolation of IP-based migration traffic; and prep-mirroring VMs on new hosts is about creating standby or synchronized copies, not about segregating the vMotion traffic.