An enterprise is planning to migrate its on-premises VMware vSphere environment to VMware Cloud (VMC) on AWS. The migration scope includes virtual machines (VMs) running multi-tier applications, including a critical Oracle database VM that requires zero replication-induced downtime during the cutover. The on-premises data center is connected to AWS via a AWS Direct Connect connection terminated on a Direct Connect Gateway (DXGW).
Additionally, the architecture requires:
- Transitive routing between the VMC on AWS Software-Defined Data Center (SDDC), the on-premises environment, and multiple spoke VPCs across different AWS accounts.
- Resolution of the private domain `corp.internal` hosted in a Route 53 Private Hosted Zone (PHZ) in a shared-services VPC.
Which TWO actions should the Solutions Architect take to migrate these workloads and configure the network connectivity?
- Use VMware HCX Replication-Assisted vMotion (RAV) to migrate the Oracle database VM and other application workloads to enable parallel replication with a zero-downtime hot switchover.Cevap
- Deploy VMware Cloud (VMC) Transit Connect to connect the SDDC to an AWS Transit Gateway, and associate the Direct Connect Gateway with the Transit Connect to enable transitive routing between the SDDC, spoke VPCs, and the on-premises environment.Cevap
- CUse VMware HCX Bulk Migration to replicate all VMs in parallel, scheduling the database VM switchover to occur during a brief maintenance window.
- DAttach the Direct Connect Gateway directly to the Virtual Private Gateways (VGWs) of both the VMC on AWS SDDC and the spoke VPCs to allow direct transitive routing.
- EAssociate the Route 53 Private Hosted Zone `corp.internal` directly with the VMC on AWS management VPC from the shared-services AWS account, relying on automated Route 53 propagation across Transit Gateway.