How does live VM migration support DR testing and ongoing availability?

How does live VM migration support DR testing and ongoing availability?

• A. It guarantees zero downtime under all circumstances.
• B. It creates new VMs automatically after failover.
• C. It enables moving VMs between hosts with minimal downtime.
• D. It prevents any maintenance actions.

Answer: (C)

Live VM migration keeps services available by moving a running virtual machine from one physical host to another without powering it off. This ability is exactly what DR testing and ongoing availability rely on: you can relocate workloads during a failover test or during maintenance, and the VM continues running with only a brief interruption as memory and state are transferred and the final switch is made. In DR testing, you validate recovery procedures by shifting VMs to a standby host or site while users stay online, which shows how failover would work in a real outage without a full outage itself. This also supports ongoing availability by letting you balance load or perform maintenance on hosts or storage without taking the VM offline. It’s not about guaranteeing zero downtime in all cases, nor about automatically creating new VMs after failover, and it doesn’t prevent maintenance actions—it enables them with minimal disruption.

Live VM migration keeps services available by moving a running virtual machine from one physical host to another without powering it off. This ability is exactly what DR testing and ongoing availability rely on: you can relocate workloads during a failover test or during maintenance, and the VM continues running with only a brief interruption as memory and state are transferred and the final switch is made. In DR testing, you validate recovery procedures by shifting VMs to a standby host or site while users stay online, which shows how failover would work in a real outage without a full outage itself. This also supports ongoing availability by letting you balance load or perform maintenance on hosts or storage without taking the VM offline. It’s not about guaranteeing zero downtime in all cases, nor about automatically creating new VMs after failover, and it doesn’t prevent maintenance actions—it enables them with minimal disruption.