An enterprise is migrating a business-critical multi-tier application from an on-premises VMware vSphere cluster to a VMware Cloud (VMC) on AWS Software-Defined Data Center (SDDC). The application consists of a write-heavy database VM with an virtual disk that requires zero downtime during migration, and fifty stateless web servers that can tolerate a brief reboot of less than . The on-premises network () must be extended to VMC on AWS to maintain IP addresses. The VMC on AWS SDDC is connected to native AWS VPCs containing shared services via an AWS Transit Gateway. The network path between the on-premises environment and VMC on AWS is established over a AWS Direct Connect connection.
To optimize the migration timeline, minimize downtime, and prevent sub-optimal routing (hairpinning) for migrated VMs communicating with native AWS services, which actions should the Solutions Architect take? (Select TWO.)
- Use VMware HCX Replication Assisted vMotion (RAV) to migrate the write-heavy database VM, and enable VMware HCX Mobility Optimized Routing (MOR) on the extended network segment.Cevap
- Use VMware HCX Bulk Migration to migrate the fifty stateless web server VMs, scheduling the switchover to occur during a maintenance window.Cevap
- CUse VMware HCX Cold Migration to migrate the write-heavy database VM to ensure data consistency, and establish a VMware HCX Network Extension without enabling Mobility Optimized Routing (MOR).
- DUse VMware HCX Bulk Migration to migrate the database VM, and attach the VMware Cloud on AWS SDDC directly to a Direct Connect Gateway to route traffic between the extended network and the native AWS VPCs.
- EUse VMware HCX vMotion to migrate the fifty stateless web server VMs in parallel, and configure a Route 53 Private Hosted Zone associated only with the native VPCs to resolve the on-premises gateway IP address.