An enterprise is planning to migrate a mission-critical multi-tier application from an on-premises VMware vSphere cluster to a newly provisioned VMware Cloud on AWS (VMC on AWS) Software-Defined Data Center (SDDC). The application comprises:
* `` transactional database virtual machines (VMs) requiring zero downtime and continuous replication to meet a Recovery Time Objective (RTO) of zero during switchover.
* `` web and application server VMs that can tolerate a brief service interruption (maximum `` of downtime for a reboot) during cutover.
The network architecture requires transitive routing between the on-premises datacenter, the VMC on AWS SDDC, and four spoke VPCs in a multi-account AWS Organization. An existing `` AWS Direct Connect (DX) connection terminates at a Direct Connect Gateway (DXGW) in a shared network account. The migrated VMs must also resolve private DNS records in an AWS Route 53 Private Hosted Zone (PHZ) managed in a Shared Services account.
Which combination of actions will meet these requirements with the least operational overhead? (Select TWO.)
- Deploy VMware HCX. Configure Replication-Assisted vMotion (RAV) to migrate the `` transactional database VMs to ensure zero downtime during switchover. Configure HCX Bulk Migration for the `` web and application server VMs to replicate data in the background and execute a scheduled switchover with a brief reboot.Cevap
- Establish a VMware Cloud on AWS Transit Connect to peer the SDDC with an AWS Transit Gateway in the network account. Attach the Direct Connect Gateway to the AWS Transit Gateway using a Transit Virtual Interface (Transit VIF) for transitive routing. Associate the Route 53 Private Hosted Zone with the SDDC's connected VPC.Cevap
- CInstall the AWS Application Migration Service (MGN) agent on all VMs. Replicate the `` database VMs using MGN replication over a Public Virtual Interface (Public VIF) on the Direct Connect connection to ensure zero-downtime switchover.
- DAttach the Direct Connect Gateway directly to the VMware Cloud on AWS SDDC and the spoke VPCs using Private Virtual Interfaces (Private VIFs). Configure static routing on the Direct Connect Gateway to enable direct transitive routing between the VMC on AWS SDDC and the spoke VPCs.
- EConfigure a Route 53 inbound resolver endpoint in the Shared Services VPC. Direct all DNS queries from the VMC on AWS SDDC VMs to the inbound resolver endpoint IP addresses without associating the Private Hosted Zone with the SDDC's connected VPC.