Examkin

Question

Difficulty: Very hardHybrid and VMware Cloud on AWS Migrations

A financial services company is planning to migrate 200200 VMware-based virtual machines (VMs) containing transactional databases and application servers from its on-premises data center to a VMware Cloud on AWS (VMC) SDDC. The migration has strict requirements: a near-zero recovery time objective (RTO), zero data loss during cutover, and the preservation of existing IP addresses due to hardcoded application configurations. The hybrid network architecture is managed across multiple AWS accounts: a central AWS Transit Gateway (TGW) in a Shared Services account is connected to on-premises via an AWS Direct Connect (DX) Gateway with a Transit VIF, and multiple application VPCs are attached to this central TGW. The VMC SDDC is connected via VMware Cloud on AWS Transit Connect (VTGW), which is peered with the central TGW. During initial configuration, replication traffic between the on-premises VMware HCX instance and the HCX Cloud destination in the VMC SDDC fails to establish connectivity. Which configuration change must the solutions architect implement to resolve the connectivity issues and enable zero-downtime migrations over the Direct Connect link?

  1. Associate the existing Direct Connect Gateway directly with the VMware Cloud on AWS Transit Connect (VTGW) by accepting an association proposal in the AWS account. Configure HCX to use this direct path for replication, and deploy HCX Replication-Assisted vMotion (RAV) to migrate the VMs while extending the L2 network to preserve IP addresses.Answer
  2. B
    Configure static routing on the central Transit Gateway to route traffic destined for the VMC SDDC CIDR block to the Transit Connect (VTGW) attachment, and advertise the on-premises IP ranges from the Direct Connect Gateway to the VTGW. Configure VMware HCX to route replication traffic through the central Transit Gateway peered connection.
  3. C
    Create a new AWS Direct Connect Private VIF on the same connection, associate it with a new virtual private gateway (VGW) in the VMC management VPC, and configure a Route 53 Private Hosted Zone associated with both the VMC VPC and the Shared Services VPC. Perform the migration using VMware HCX Bulk Migration to ensure zero data loss.
  4. D
    Deploy AWS Application Migration Service (MGN) replication agents on all on-premises VMs. Route the replication traffic over the peered Transit Connect link by configuring Transit Gateway Connect attachments to run BGP over GRE tunnels between the VMC SDDC and the central Transit Gateway.

Answer

Associate the existing Direct Connect Gateway directly with the VMware Cloud on AWS Transit Connect (VTGW) by accepting an association proposal in the AWS account. Configure HCX to use this direct path for replication, and deploy HCX Replication-Assisted vMotion (RAV) to migrate the VMs while extending the L2 network to preserve IP addresses.
The correct option addresses the transit routing limitation by directly associating the Direct Connect Gateway with the VMware Transit Connect (VTGW). This allows routing traffic directly from the on-premises routers to the VMC SDDC over the Direct Connect Transit VIF. Furthermore, VMware HCX Replication-Assisted vMotion (RAV) ensures zero data loss and near-zero downtime by combining bulk background replication with a hot vMotion-based switchover, while the HCX L2 Network Extension preserves VM IP addresses.

Step-by-Step Solution

1
Analyze routing paths in Transit Gateway peered architectures.
Identify that AWS Transit Gateway peered connections are non-transitive for Direct Connect Gateway (DXGW) traffic.
Traffic from on-premises via DXGW cannot traverse the Central TGW over a peered connection to reach the VMware Transit Connect (VTGW).
2
Establish direct routing between on-premises and VMware Cloud on AWS.
Associate the DXGW directly with the VMware Transit Connect (VTGW).
Direct association allows direct BGP prefix exchange between on-premises routers and the SDDC via the DX connection.
3
Select the correct VMware migration mechanism to meet recovery objectives.
Choose VMware HCX Replication-Assisted vMotion (RAV).
RAV combines bulk parallel replication with a zero-downtime live vMotion switchover, satisfying the near-zero RTO and zero data loss requirements.
4
Select the technology to preserve VM IP configurations.
Utilize HCX L2 Network Extension.
Extending the L2 network allows VMs to run on VMC with their original on-premises IP addresses without requiring immediate IP changes.

Key Concept

Direct Connect Gateway association with VMware Cloud on AWS Transit Connect to bypass non-transitive routing limitations of Transit Gateway peering.
Estimated Time:3m 0s
Rate this question

Topics

Hybrid and VMware Cloud on AWS Migrations

More questions from this topic