Question

Difficulty: HardHybrid and VMware Cloud on AWS Migrations

An enterprise is migrating 150 VMware-based workloads from an on-premises data center to VMware Cloud (VMC) on AWS. The destination architecture requires deploying these workloads across two separate Software-Defined Data Centers (SDDCs), SDDC 1 and SDDC 2, located in different AWS accounts for resource isolation. The migration and network architecture must meet the following technical requirements:

- Workloads must be migrated with zero application downtime to satisfy a strict recovery time objective (RTO) of zero.
- Workloads in SDDC 1 must communicate directly with workloads in SDDC 2 over the private network.
- Both SDDCs must connect back to the on-premises data center using an existing 10 Gbps10\text{ Gbps} AWS Direct Connect connection.
- All migrated workloads must resolve private domain names hosted in a central Route 53 Private Hosted Zone (PHZ) in a shared services VPC.

Which combination of migration method, network connectivity, and DNS configuration meets these requirements with the lowest operational complexity?

  1. Use VMware HCX Replication-Assisted vMotion (RAV) for the migrations. Attach SDDC 1, SDDC 2, and the shared services VPC to a VMware Cloud Transit Connect (VTGW), and associate the VTGW with the Direct Connect Gateway. Associate the central Route 53 PHZ with the connected VPCs of both SDDCs, and configure the SDDC Compute Gateway (CGW) DNS to forward queries to the AmazonProvidedDNS IP address of their respective connected VPCs.Answer
  2. B
    Use VMware HCX Bulk Migration for the migrations. Connect both SDDCs and the shared services VPC directly to a Direct Connect Gateway using private virtual interfaces (VIFs) to establish hybrid and inter-SDDC routing. Associate the central Route 53 PHZ with the shared services VPC, and configure the SDDC Compute Gateway (CGW) DNS to forward queries to the shared services VPC DNS resolver.
  3. C
    Use VMware HCX Replication-Assisted vMotion (RAV) for the migrations. Attach SDDC 1, SDDC 2, and the shared services VPC to a VMware Cloud Transit Connect (VTGW), and associate the VTGW with the Direct Connect Gateway. Configure the SDDC Compute Gateway (CGW) DNS to forward queries directly to the AmazonProvidedDNS IP address of their respective connected VPCs, without creating any cross-account associations for the central Route 53 PHZ.
  4. D
    Use VMware HCX Cold Migration for the migrations. Establish an IPsec VPN mesh between the on-premises environment and both SDDCs over a Direct Connect public virtual interface (VIF) to enable routing. Associate the central Route 53 PHZ with the connected VPCs, and configure a Route 53 Resolver Inbound Endpoint in each connected VPC to handle DNS queries from the SDDCs.

Answer

Use VMware HCX Replication-Assisted vMotion (RAV) for the migrations. Attach SDDC 1, SDDC 2, and the shared services VPC to a VMware Cloud Transit Connect (VTGW), and associate the VTGW with the Direct Connect Gateway. Associate the central Route 53 PHZ with the connected VPCs of both SDDCs, and configure the SDDC Compute Gateway (CGW) DNS to forward queries to the AmazonProvidedDNS IP address of their respective connected VPCs.
The correct option satisfies all constraints. VMware HCX Replication-Assisted vMotion (RAV) allows zero-downtime, bulk hot migrations of VMs. VMware Cloud Transit Connect (VTGW) provides high-bandwidth, transitive routing between SDDCs and VPCs, and connects to the Direct Connect Gateway for hybrid pathing. Associating the Route 53 Private Hosted Zone (PHZ) with the connected VPCs ensures that queries forwarded to the AmazonProvidedDNS IP address resolve the private records correctly.

Step-by-Step Solution

1
Determine the migration method that guarantees zero downtime.
Identify VMware HCX Replication-Assisted vMotion (RAV) as the correct choice since it combines the parallel operations of Bulk Migration with the zero-downtime hot-migration properties of HCX vMotion. Reject Bulk Migration (requires a reboot) and Cold Migration (requires VM power-off).
Satisfies the strict RTO of zero.
2
Design the hybrid and inter-SDDC routing architecture.
Use VMware Cloud Transit Connect (VTGW) to interconnect SDDC 1 and SDDC 2, and connect the VTGW to the Direct Connect Gateway (DXGW) for the on-premises connection.
Direct Connect Gateway alone does not support transitive routing (SDDC-to-SDDC or VPC-to-VPC), making Transit Connect necessary to allow direct communication between the two SDDCs and the on-premises data center over the same Direct Connect connection.
3
Establish the private DNS resolution flow.
Associate the Route 53 Private Hosted Zone (PHZ) in the shared services account with the connected VPCs of SDDC 1 and SDDC 2, and point the SDDC CGW DNS to the AmazonProvidedDNS IP address (base + 2) of their respective connected VPCs.
Allows VMs inside the SDDCs to query the connected VPC resolver, which can only resolve names in the PHZ if it is associated with that VPC.

Key Concept

VMware Cloud on AWS hybrid migration planning and routing topology using HCX RAV, VMware Cloud Transit Connect, and cross-account Route 53 PHZ associations.
Rate this question