A multinational enterprise is migrating its vSphere-based workloads to a VMware Cloud on A… — AWS Certified Solutions Architect - Professional

A multinational enterprise is migrating its vSphere-based workloads to a VMware Cloud on AWS Software-Defined Data Center (SDDC) linked to a multi-account AWS environment. The workloads to migrate consist of:

1. A production cluster of $12$ critical database virtual machines (VMs) that must remain online during the initial data synchronization phase and experience near-zero downtime during the final switchover.
2. A development and testing environment consisting of $150$ VMs that can tolerate up to $3$ hours of downtime during a scheduled cutover window.

The enterprise has configured a $10\text{ Gbps}$ AWS Direct Connect connection to the on-premises data center.
Additionally, the migrated VMs in the SDDC must resolve internal service endpoints in a Private Hosted Zone (PHZ) for `corp.local` hosted in a Shared Services VPC in a separate AWS account. The SDDC is connected to this Shared Services VPC using VMware Cloud on AWS Transit Connect.

Which two actions should the solutions architect take to meet these requirements? (Select two.)

Configure VMware HCX Replication Assisted vMotion (RAV) to migrate the $12$ database VMs to achieve parallel replication and live switchover, and use VMware HCX Bulk Migration to migrate the $150$ development and testing VMs in scheduled waves.Answer
Deploy Route 53 Resolver Inbound Endpoints in the Shared Services VPC, and configure the SDDC DNS Forwarder in the VMware Cloud Console to route queries for `corp.local` to the IP addresses of the Inbound Endpoints.Answer
C
Configure VMware HCX Cold Migration for the $12$ database VMs to ensure zero write activity during the transfer, and use VMware HCX vMotion to migrate the $150$ development and testing VMs concurrently.
D
Associate the `corp.local` Private Hosted Zone directly with the VMC SDDC management VPC, and configure the migrated VMs to query the AWS default VPC resolver ( $169.254.169.253$ ) of the associated VPC.
E
Configure a Virtual Private Gateway (VGW) in the Shared Services VPC, attach it to the Direct Connect Gateway (DXGW) used by the SDDC, and configure transitive routing to pass DNS traffic from the SDDC to the Shared Services VPC.

Answer

Configure VMware HCX Replication Assisted vMotion (RAV) for the database VMs and VMware HCX Bulk Migration for the development/testing VMs, and deploy Route 53 Resolver Inbound Endpoints in the Shared Services VPC while configuring the SDDC DNS Forwarder to route queries to them.

The correct choices are the options recommending the use of VMware HCX Replication Assisted vMotion (RAV) for the databases and HCX Bulk Migration for the development/testing workloads, alongside deploying Route 53 Resolver Inbound Endpoints in the Shared Services VPC and configuring the SDDC DNS Forwarder. VMware HCX RAV provides parallel replication with a live vMotion switchover, ensuring the database VMs remain online and experience near-zero downtime. HCX Bulk Migration allows efficient, parallel scheduled switchover (with a brief reboot) of the 150 development/testing VMs within their downtime window. For DNS resolution, Route 53 Resolver Inbound Endpoints are required to receive forwarded queries from the VMC SDDC NSX-T DNS forwarder, as VMC subnets cannot query the default Route 53 resolver directly.

Step-by-Step Solution

Analyze the database migration requirements.

The database VMs require zero replication downtime and near-zero downtime during switchover, which points to VMware HCX Replication Assisted vMotion (RAV) or HCX vMotion. However, because there are multiple VMs (

12

) that need parallel replication, RAV is the appropriate choice as standard vMotion replicates serially.

HCX RAV allows parallel replication and scheduling of a live migration switchover, meeting the near-zero downtime and parallel migration needs.

Analyze the development/testing environment migration requirements.

The

150

VMs can tolerate up to

3

hours of downtime. A bulk migration approach is optimal.

HCX Bulk Migration allows parallel replication and scheduled switchover (with a reboot), which is highly efficient for migrating a large volume of non-production VMs that can tolerate downtime.

Determine the DNS resolution architecture.

The migrated VMs in the SDDC need to resolve records in a Private Hosted Zone in the Shared Services VPC. Because Route 53 resolvers do not accept direct queries from outside the local VPC CIDR, the VMC SDDC must forward DNS requests to Route 53 Resolver Inbound Endpoints deployed in the Shared Services VPC.

This enables cross-VPC DNS resolution from the VMC SDDC over the Transit Connect peering connection.

Key Concept

Selecting appropriate VMware HCX migration methods (RAV vs. Bulk) based on downtime requirements and designing cross-account DNS resolution using Route 53 Resolver Inbound Endpoints over VMware Transit Connect.

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic