Examkin

Soru

Zorluk: ZorHybrid and VMware Cloud on AWS Migrations

A technology company is preparing to migrate its core application portfolio from a local VMware vSphere cluster to a VMware Cloud on AWS (VMC on AWS) Software-Defined Data Center (SDDC). The company's hybrid network architecture consists of a 10 Gbps AWS Direct Connect connection terminated at an AWS Transit Gateway in a centralized Network account using a Transit VIF. The migration candidates consist of 15 high-throughput transactional database virtual machines (VMs) that must remain online with zero operational downtime, and 120 web application VMs that can tolerate a brief service interruption of up to 15 minutes during a weekend maintenance window. Additionally, all migrated workloads must resolve internal service endpoints hosted in a Route 53 Private Hosted Zone for corp.internal in a separate Shared Services AWS account. Which two actions should a solutions architect recommend to satisfy these requirements? (Select two.)

  1. Configure VMware Transit Connect to peer with the customer's AWS Transit Gateway. Deploy Route 53 Resolver inbound endpoints in the Shared Services VPC, and configure the SDDC's DNS forwarder to route queries for corp.internal to the inbound endpoint IP addresses.Cevap
  2. Implement VMware HCX for the migration. Configure Replication-Assisted vMotion (RAV) to migrate the 15 transactional database VMs, and use Bulk Migration to migrate the 120 web application VMs with a scheduled switchover during the maintenance window.Cevap
  3. C
    Associate the Route 53 Private Hosted Zone corp.internal directly with the VMware Cloud on AWS SDDC management VPC by using the AWS CLI to authorize and associate the cross-account VPC.
  4. D
    Configure VMware Transit Connect to peer with the customer's AWS Transit Gateway, and configure the customer's AWS Transit Gateway to route HCX migration traffic transitively from the on-premises Direct Connect Transit VIF to the VMware Transit Connect.
  5. E
    Deploy the AWS Application Migration Service (MGN) replication agent on all on-premises VMs. Replicate the workloads over the Direct Connect connection to the VMC on AWS SDDC, and schedule a cutover window for the web application VMs while using live migration for the databases.

Cevap

The correct actions are implementing VMware HCX to migrate database VMs via Replication-Assisted vMotion (RAV) and application VMs via Bulk Migration, and configuring VMware Transit Connect peered with the customer's Transit Gateway while utilizing Route 53 Resolver inbound endpoints for DNS resolution.
Implementing VMware HCX with Replication-Assisted vMotion (RAV) ensures that the 15 database VMs migrate with zero downtime, as RAV performs bulk seeding followed by a live switchover. HCX Bulk Migration is ideal for the 120 application VMs because it schedules the switchover during the weekend maintenance window, resulting in a reboot and minimal downtime (under 15 minutes). For connectivity and DNS, peering VMware Transit Connect with the customer's AWS Transit Gateway establishes the necessary cross-account routing path. Because the customer cannot directly associate a Private Hosted Zone with the VMware-managed SDDC VPC, using Route 53 Resolver inbound endpoints in the Shared Services VPC and pointing the SDDC's DNS forwarder to them resolves queries for corp.internal correctly.

Adım Adım Çözüm

1
Analyze the virtual machine migration requirements to choose the correct migration tool and mechanisms.
Identify that since the destination is a VMware Cloud on AWS SDDC, VMware HCX is required (not AWS MGN). For the 15 database VMs needing zero downtime, choose Replication-Assisted vMotion (RAV). For the 120 application VMs that can tolerate minimal downtime, choose Bulk Migration.
HCX RAV enables live migration with zero downtime, while Bulk Migration allows scheduled switchover of multiple VMs with a brief reboot.
2
Establish hybrid network routing between the VMC SDDC and the multi-account AWS environment.
Configure VMware Transit Connect to peer with the customer's AWS Transit Gateway, and configure appropriate routing rules. Recognize that transitive routing from on-premises to VMware Transit Connect through the customer's peered AWS Transit Gateway is not supported.
VMware Transit Connect is the native way to connect SDDCs to AWS Transit Gateways, but Transit Gateway peering has a transitive routing limitation for on-premises attachments.
3
Design a private DNS resolution mechanism for SDDC workloads to resolve corp.internal in the Shared Services account.
Deploy Route 53 Resolver inbound endpoints in the Shared Services VPC (which is associated with the Private Hosted Zone) and configure the SDDC's DNS forwarder to forward corp.internal queries to these inbound endpoint IP addresses.
The VMC SDDC cannot directly associate with the customer's Route 53 Private Hosted Zone, so DNS queries must be forwarded to Route 53 Resolver inbound endpoints.

Anahtar Kavram

VMware Cloud on AWS migration using VMware HCX, coupled with private DNS resolution via Route 53 Resolver endpoints and hybrid network connectivity with VMware Transit Connect.
Bu soruyu puanla

Konular

Hybrid and VMware Cloud on AWS Migrations

Bu konudan daha fazla soru