Following a company merger, there are two data centers running vSphere environments. Both data centers are leveraging separate Layer 3 vMotion networks. Which requirement must be met in order to…

Question

Options

• AThe vMotion service must be configured on the Management VMkernel adapter
• BA dedicated TCP/IP stack for vMotion with a dedicated gateway must be configured
• CA stretched vMotion network must be configured between data centers
• DVirtual machines must be powered off in order to migrate them between data centers

• A
  2% (1)
• B
  82% (47)
• C
  5% (3)
• D
  11% (6)

Explanation

When two data centers use separate Layer 3 networks (routed, not the same broadcast domain), vMotion traffic must cross a router - meaning each side needs its own gateway. Option B is correct because the vMotion TCP/IP stack in vSphere provides a dedicated network stack with its own default gateway, allowing vMotion traffic to be routed between L3-separated sites without conflicting with the management or default TCP/IP stack's gateway.

• A is wrong because vMotion runs on its own VMkernel adapter, not the Management adapter - mixing them is a configuration anti-pattern and doesn't solve the L3 routing problem.
• C is wrong because a stretched (Layer 2) vMotion network would eliminate the L3 boundary, but the question states L3 networks are already in place - you can't just "configure" a stretch without physical/VXLAN infrastructure changes, and doing so isn't required when the vMotion TCP/IP stack handles L3 routing.
• D is wrong because live (hot) vMotion across L3 is exactly what this feature enables - powering off VMs would be Cold Migration, which doesn't require vMotion at all.

Memory tip: Think "L3 = needs a gateway." The vMotion TCP/IP stack is the only stack that lets you assign a dedicated gateway specifically for vMotion, making it the go-to solution any time vMotion must cross a router.

No community discussion yet for this question.