Examkin

Soru

Zorluk: OrtaHybrid and VMware Cloud on AWS Migrations

An enterprise is planning to migrate its workloads from an on-premises VMware vSphere environment to a VMware Cloud on AWS Software-Defined Data Center (SDDC). The workloads consist of a critical 2 TB database virtual machine (VM) that must remain online with zero downtime during the migration, and 40 application server VMs that can tolerate a brief service interruption of under 15 minutes. The migration must be scheduled to switch over during a weekend maintenance window. The network connectivity is a dedicated 1 Gbps AWS Direct Connect connection with a round-trip latency of 35 ms. Which migration strategy meets these requirements with the least operational impact?

  1. Configure VMware HCX. Use HCX vMotion to migrate the critical database VM with zero downtime, and use HCX Bulk Migration to replicate and schedule the switchover of the 40 application server VMs during the maintenance window.Cevap
  2. B
    Configure VMware HCX. Use HCX Bulk Migration for all virtual machines, including the database VM, to perform parallel replication and ensure consistent switchover times for all workloads.
  3. C
    Install the AWS Application Migration Service (MGN) agent on all virtual machines, replicate the volumes over the AWS Direct Connect connection, and launch the instances directly into the VMware Cloud on AWS SDDC cluster.
  4. D
    Configure VMware HCX. Use HCX Replication-Assisted vMotion (RAV) for all virtual machines. Route the migration traffic over the Direct Connect connection through an AWS Transit Gateway directly to the VMware ESXi hosts without establishing an HCX L2 Network Extension.

Cevap

Configure VMware HCX. Use HCX vMotion to migrate the critical database VM with zero downtime, and use HCX Bulk Migration to replicate and schedule the switchover of the 40 application server VMs during the maintenance window.
The correct strategy combines VMware HCX vMotion and HCX Bulk Migration. Since the database VM requires zero downtime and the Direct Connect link latency (35 ms) is below the 150 ms threshold, HCX vMotion is the ideal choice. For the remaining 40 application VMs, HCX Bulk Migration allows them to be replicated in parallel over time and switched over with a minimal reboot downtime (less than 15 minutes) during the weekend maintenance window, reducing the risk and complexity of migrating all hosts simultaneously via live migration.

Adım Adım Çözüm

1
Analyze the downtime constraints for each workload class: the database VM requires zero downtime (ruling out Bulk Migration for it), while the 40 application servers can tolerate up to 15 minutes of downtime.
Identify that a live migration method (such as HCX vMotion or RAV) is required for the database VM, while a bulk/replicated method (HCX Bulk Migration) is suitable for the application servers.
Matching migration methods to the recovery/downtime objectives ensures business continuity requirements are met.
2
Verify network prerequisites for HCX vMotion, including checking the latency and bandwidth of the AWS Direct Connect connection.
Confirm that the 35 ms latency is well below the 150 ms maximum limit required for HCX vMotion.
vMotion is latency-sensitive; verifying latency ensures the migration will not fail mid-process.
3
Select the appropriate HCX migration type for each workload.
Choose HCX vMotion for the database VM to achieve zero downtime, and HCX Bulk Migration for the 40 application VMs to allow parallel replication and scheduled cutover.
Combining these methods optimizes bandwidth utilization and minimizes overall risk during the scheduled maintenance window.

Anahtar Kavram

Selecting the correct VMware HCX migration method based on virtual machine downtime tolerance, latency limits, and target architecture.
Bu soruyu puanla

Konular

Hybrid and VMware Cloud on AWS Migrations

Bu konudan daha fazla soru