Examkin

Soru

Zorluk: ZorHybrid and VMware Cloud on AWS Migrations

An enterprise is planning to migrate its workloads from an on-premises VMware vSphere data center to a newly deployed VMware Cloud on AWS Software-Defined Data Center (SDDC). The current hybrid network is configured as follows:

* On-premises resources connect to a centralized AWS Transit Gateway (TGW) in a central network account using a 10 Gbps10\text{ Gbps} AWS Direct Connect connection via a Direct Connect Gateway (DXGW).
* Multiple AWS VPCs are attached to the central TGW.
* A Route 53 Private Hosted Zone (PHZ) `internal.enterprise.com` is hosted in a Shared Services AWS account and associated with all AWS VPCs.

The migration must satisfy the following technical requirements:

1. A transactional Web Tier application must be migrated with zero downtime during the cutover.
2. A 12 TB12\text{ TB} database VM must be migrated with a maximum allowable downtime of 15 minutes15\text{ minutes} during a scheduled weekend maintenance window.
3. Migrated VMs in the SDDC must be able to resolve DNS queries for `internal.enterprise.com` and establish network connectivity with the on-premises data center over the Direct Connect connection.

Which architecture should the Solutions Architect implement to meet these requirements with the lowest operational complexity?

  1. Migrate the Web Tier application using VMware HCX Replication Assisted vMotion (RAV) and the database VM using VMware HCX Bulk Migration. Associate the Direct Connect Gateway directly with the VMware Transit Connect (VTGW) peer. Associate the Route 53 PHZ `internal.enterprise.com` with the SDDC's connected VPC, and configure the SDDC DNS servers to forward queries to the Route 53 Resolver IP address of the connected VPC.Cevap
  2. B
    Migrate the Web Tier application using VMware HCX Replication Assisted vMotion (RAV) and the database VM using VMware HCX Bulk Migration. Peer the VMware Transit Connect (VTGW) with the central AWS Transit Gateway (TGW) to route traffic between the SDDC and the on-premises data center. Associate the Route 53 PHZ `internal.enterprise.com` with the SDDC's connected VPC, and configure the SDDC DNS servers to forward queries to the Route 53 Resolver IP address of the connected VPC.
  3. C
    Migrate both the Web Tier application and the database VM using VMware HCX Bulk Migration. Associate the Direct Connect Gateway directly with the VMware Transit Connect (VTGW) peer. Deploy Route 53 Resolver Inbound Endpoints in the Shared Services VPC, and configure the SDDC DNS servers to forward queries for `internal.enterprise.com` directly to these endpoints without associating the PHZ with the connected VPC.
  4. D
    Migrate the Web Tier application using VMware HCX Cold Migration and the database VM using VMware HCX Replication Assisted vMotion (RAV). Associate the Direct Connect Gateway directly with the VMware Transit Connect (VTGW) peer. Associate the Route 53 PHZ `internal.enterprise.com` with the SDDC's connected VPC, and configure the SDDC DNS servers to forward queries to the Route 53 Resolver IP address of the connected VPC.

Cevap

Migrate the Web Tier application using VMware HCX Replication Assisted vMotion (RAV) and the database VM using VMware HCX Bulk Migration. Associate the Direct Connect Gateway directly with the VMware Transit Connect (VTGW) peer. Associate the Route 53 PHZ `internal.enterprise.com` with the SDDC's connected VPC, and configure the SDDC DNS servers to forward queries to the Route 53 Resolver IP address of the connected VPC.
The correct solution accurately maps the migration methods to the constraints: VMware HCX Replication Assisted vMotion (RAV) enables zero-downtime cutover for the active transactional Web Tier, while HCX Bulk Migration replicates the massive database VM offline and performs a quick switchover within the 1515-minute RTO. For network connectivity, associating the DXGW directly with the VTGW resolves the non-transitive routing issue across peered Transit Gateways. Lastly, associating the Private Hosted Zone with the VMC connected VPC and forwarding SDDC DNS traffic to the VPC DNS resolver (.2 IP) ensures seamless cross-environment name resolution.

Adım Adım Çözüm

1
Select the appropriate migration method based on application downtime requirements.
The Web Tier application is matched with HCX Replication Assisted vMotion (RAV) to guarantee zero downtime. The database VM is matched with HCX Bulk Migration to handle the 12 TB12\text{ TB} data footprint within a scheduled 1515-minute downtime window.
RAV provides zero-downtime live migrations by combining bulk replication with live vMotion switchover. Bulk Migration replicates data in the background and reboots the VM on destination, which is ideal for large, non-live migrations that can tolerate a brief reboot.
2
Determine the Direct Connect hybrid connectivity strategy that overcomes transitive routing limits.
Associate the Direct Connect Gateway (DXGW) directly with the VMware Transit Connect (VTGW).
AWS Transit Gateway peering does not allow transitive routing to a Direct Connect Gateway. To route traffic between the SDDC and on-premises over Direct Connect, the DXGW must be associated directly with the VTGW.
3
Establish Route 53 Private Hosted Zone (PHZ) resolution for VMC on AWS workloads.
Associate the PHZ with the VMC connected VPC and configure the SDDC DNS servers to forward queries to the Route 53 Resolver IP address.
Route 53 PHZs require explicit association with target VPCs to allow resolution. Forwarding queries to the connected VPC's Route 53 Resolver IP address (.2 address of the subnet) enables SDDC VMs on NSX-T segments to resolve the zone.

Anahtar Kavram

Bypassing non-transitive TGW peering constraints by associating the DXGW directly with the VTGW, combined with proper VMC DNS resolution and HCX migration mode selection.
Bu soruyu puanla

Konular

Hybrid and VMware Cloud on AWS Migrations

Bu konudan daha fazla soru