Examkin

Question

Difficulty: MediumHybrid and VMware Cloud on AWS Migrations

A company is planning to migrate its application workloads from an on-premises VMware vSphere cluster to a newly provisioned VMware Cloud on AWS SDDC. The migration project must accommodate two distinct workload requirements:

1. A group of critical, stateful transaction processing applications that cannot tolerate any downtime or service interruption during migration.
2. A group of multi-terabyte development database servers where data must replicate continuously in the background, with a scheduled reboot and switchover allowed during a weekend maintenance window to minimize the impact on network bandwidth.

Which two VMware HCX migration methods should the Solutions Architect select to meet these requirements? (Select TWO.)

  1. Utilize VMware HCX Replication-Assisted vMotion (RAV) to migrate the transaction processing applications in parallel batches with zero downtime.Answer
  2. Utilize VMware HCX Bulk Migration for the development database servers to enable background replication and schedule a low-downtime cutover.Answer
  3. C
    Choose VMware HCX Cold Migration to migrate the transaction processing applications while they continue to serve active client connections.
  4. D
    Deploy VMware HCX OS Assisted Migration to replicate the development database servers from the on-premises VMware ESXi hosts.
  5. E
    Use VMware HCX vMotion for the multi-terabyte database servers to queue and replicate their storage disks in parallel before the scheduled weekend cutover.

Answer

Utilize VMware HCX Replication-Assisted vMotion (RAV) for the critical transaction processing workloads, and utilize VMware HCX Bulk Migration for the development database servers.
The correct options are to utilize VMware HCX Replication-Assisted vMotion (RAV) for the transaction processing applications and VMware HCX Bulk Migration for the development database servers. HCX RAV combines the parallel scheduling benefits of Bulk Migration with the live migration capabilities of vMotion, providing parallel zero-downtime migrations. HCX Bulk Migration uses host-based replication to copy data in the background, allowing the administrator to schedule a cutover that involves a brief reboot to activate the target VM, which perfectly aligns with the requirements of the database servers.

Step-by-Step Solution

1
Analyze the requirements for the critical transaction applications.
Identify that the applications are stateful and require batch migrations with zero downtime.
This rules out migration methods that require powering off the VMs or executing them sequentially over high-latency links.
2
Analyze the requirements for the development database servers.
Identify that the databases are multi-terabyte and require background replication to minimize bandwidth usage, with a scheduled switchover window.
This rules out standard live vMotion, which transfers active memory and disk states continuously and does not support scheduled cutovers.
3
Map the analyzed requirements to VMware HCX migration capabilities.
Match the transaction applications to VMware HCX Replication-Assisted vMotion (RAV) and the databases to VMware HCX Bulk Migration.
RAV supports zero-downtime migrations in parallel batches, and Bulk Migration replicates disk data in the background to prepare for a scheduled cutover with a brief reboot.

Key Concept

Selecting VMware HCX migration methods based on application dependency, downtime tolerance, and size requirements.
Estimated Time:2m 0s
Rate this question

Topics

Hybrid and VMware Cloud on AWS Migrations

More questions from this topic