A financial company is planning to migrate a critical payment application from an on-premi… — AWS Certified Solutions Architect - Professional

A financial company is planning to migrate a critical payment application from an on-premises VMware vSphere cluster to VMware Cloud on AWS (VMC). The application consists of $40$ application server virtual machines (VMs) that can tolerate a brief service interruption (less than $5$ minutes) during switchover, and $2$ transactional database VMs that must remain online with zero downtime and zero data loss ( $RPO = 0$ , $RTO = 0$ ) during the migration.

The company's AWS multi-account environment is structured as follows:
* Account A hosts the VMC on AWS Software-Defined Data Center (SDDC).
* Account B hosts a Shared Services VPC containing Active Directory servers and Amazon Route 53 Private Hosted Zones (PHZs).
* Account C hosts native production spoke VPCs.

A customer-managed AWS Transit Gateway (TGW) in a central network account connects the Shared Services VPC and the Account C production spoke VPCs. Physical connectivity to the on-premises datacenter is established via a $2\text{ Gbps}$ AWS Direct Connect connection terminated on a customer-managed Direct Connect Gateway (DXGW).

The target architecture must enable bidirectional DNS resolution between all environments, allow on-premises administrators to manage the SDDC VMs post-migration, and enable private communication between SDDC VMs and native AWS resources.

Which combination of migration techniques and network configurations will meet these requirements?

Use VMware HCX Bulk Migration for the $40$ application VMs and VMware HCX Replication Assisted vMotion (RAV) for the $2$ database VMs. Configure VMware Transit Connect (VTGW) for the SDDC, peer VTGW with the customer-managed TGW, and associate the DXGW with both VTGW and the customer-managed TGW. Associate the Route 53 PHZs in Account B with the SDDC's connected VPC, and configure Route 53 Resolver outbound endpoints to forward on-premises DNS queries.Answer
B
Use VMware HCX Bulk Migration for all $42$ VMs. Configure VMware Transit Connect (VTGW) for the SDDC, peer VTGW with the customer-managed TGW, and associate the DXGW with the customer-managed TGW. Route all SDDC traffic to the on-premises datacenter transitively through the customer-managed TGW. Associate the Route 53 PHZs with the SDDC's connected VPC, and use Route 53 Resolver endpoints for hybrid DNS.
C
Use VMware HCX Bulk Migration for the $40$ application VMs and VMware HCX Replication Assisted vMotion (RAV) for the $2$ database VMs. Peer VMware Transit Connect (VTGW) with the customer-managed TGW, and associate the DXGW only with the customer-managed TGW. Route SDDC traffic to the on-premises datacenter transitively via the TGW peering connection. Associate the Route 53 PHZs with the SDDC's connected VPC, and configure Route 53 Resolver endpoints.
D
Use VMware HCX Replication Assisted vMotion (RAV) for all $42$ VMs. Peer VMware Transit Connect (VTGW) with the customer-managed TGW, and associate the DXGW with both VTGW and the customer-managed TGW. Associate the Route 53 PHZs in Account B only with the Shared Services VPC, relying on default VPC DNS delegation to resolve native AWS resource names from the SDDC overlay networks. Configure Route 53 Resolver endpoints for hybrid DNS.

Answer

Use VMware HCX Bulk Migration for the application servers and VMware HCX Replication Assisted vMotion (RAV) for the databases. Configure VMware Transit Connect (VTGW), peer it with the customer-managed TGW, and associate the Direct Connect Gateway (DXGW) with both VTGW and the customer-managed TGW. Associate the Route 53 Private Hosted Zones in Account B with the SDDC's connected VPC, and configure Route 53 Resolver outbound endpoints to forward on-premises DNS queries.

The correct solution correctly maps the migration tools to the workload requirements: HCX Bulk Migration is ideal for parallel, low-downtime replication of the

40

application VMs, and HCX Replication Assisted vMotion (RAV) ensures zero-downtime live migration for the database VMs. For networking, associating the Direct Connect Gateway (DXGW) with both VMware Transit Connect and the customer-managed Transit Gateway is required because AWS Transit Gateway peering does not support transitive routing to/from a DXGW. Finally, associating the Route 53 Private Hosted Zones in Account B with the SDDC's connected VPC in Account A allows the SDDC VMs to resolve internal AWS domain names, and Route 53 Resolver endpoints enable hybrid DNS resolution.

Step-by-Step Solution

Determine the appropriate migration technique for each workload tier based on downtime requirements.

Identify that the

40

application VMs can use HCX Bulk Migration since they tolerate a reboot, whereas the

2

database VMs require Replication Assisted vMotion (RAV) to achieve live migration with zero downtime.

HCX Bulk Migration replicates data in parallel and executes a cold switchover (reboot), while RAV combines replication with vMotion to perform a hot switchover with no downtime.

Design the network routing architecture between VMware Cloud on AWS, native AWS VPCs, and on-premises.

Deploy VMware Transit Connect (VTGW), peer it with the customer-managed AWS Transit Gateway (TGW), and associate the Direct Connect Gateway (DXGW) to both VTGW and the customer TGW.

AWS Transit Gateway peering does not support transitive routing to/from a Direct Connect Gateway. Therefore, to ensure on-premises connectivity for both SDDC and native VPCs, the DXGW must be directly associated with both Transit Gateways.

Configure DNS resolution for the hybrid multi-account environment.

Associate the Route 53 Private Hosted Zones (PHZs) in Account B with the SDDC's connected VPC in Account A, and configure Route 53 Resolver endpoints for hybrid DNS forwarding.

Since SDDC VMs query the Amazon Provided DNS (169.254.169.253) of the connected VPC, the PHZs must be associated with the connected VPC to resolve native AWS DNS names.

Key Concept

Designing hybrid VMware migrations and multi-account connectivity using HCX, VMware Transit Connect, Transit Gateway peering, and Route 53 Resolver associations while adhering to transitive routing limits.

Estimated Time:3m 0s

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic