Migration & HA interview questions

1. A.A DRS rule that keeps specified VMs running on the same host (VM-VM affinity) or a defined host group (VM-host affinity)
2. B.a rule keeping specified VMs together on the same host
3. C.a saved-state VM move with a brief pause
4. D.live migration of a running VM between ESXi hosts with no downtime

Answer + AI explanation with Pro

1. A.vMotion
2. B.vSphere HA admission control
3. C.Proactive HA
4. D.Affinity rule

Answer + AI explanation with Pro

1. A.vMotion — live migration of a running VM between ESXi hosts with no downtime
2. B.vMotion — Recovery Time Objective: the maximum acceptable time to restore a service after an outage
3. C.vMotion — a saved-state VM move with a brief pause
4. D.vMotion — XenServer/XCP-ng live migration of a running VM

Answer + AI explanation with Pro

1. A.A migration that changes both compute host and datastore in one operation, working even between hosts with no shared storage
2. B.live migration of a VM's disk files between datastores
3. C.A vMotion variant that encrypts the migration traffic in transit, mandatory for encrypted VMs and optional otherwise
4. D.a rule keeping specified VMs apart on different hosts

Answer + AI explanation with Pro

1. A.Hyper-V Live Migration
2. B.Datastore heartbeating
3. C.Storage vMotion
4. D.XenMotion

Answer + AI explanation with Pro

1. A.Storage vMotion — The default migration model (vMotion, KVM) that iteratively copies dirty memory pages to the destination while the source runs, then briefly pauses to copy the last delta
2. B.Storage vMotion — XenServer/XCP-ng live migration of a running VM
3. C.Storage vMotion — a rule keeping specified VMs apart on different hosts
4. D.Storage vMotion — live migration of a VM's disk files between datastores

Answer + AI explanation with Pro

1. A.HA uses shared datastores as a secondary liveness channel to distinguish host isolation from host failure.
2. B.restarting VMs on surviving hosts after a host failure
3. C.Admission-control setting reserving enough capacity to restart all VMs after losing the specified number of hosts.
4. D.Enhanced vMotion Compatibility masks newer CPU features to a common baseline so mixed-generation hosts can vMotion.

Answer + AI explanation with Pro

1. A.vSphere HA
2. B.Host failures to tolerate
3. C.Enhanced vMotion (XvMotion)
4. D.EVC baselines

Answer + AI explanation with Pro

1. A.vSphere HA — XenServer/XCP-ng live migration of a running VM
2. B.vSphere HA — restarting VMs on surviving hosts after a host failure
3. C.vSphere HA — live migration of a VM's disk files between datastores
4. D.vSphere HA — Automatically migrating all running VMs off a host before patching so the host can reboot without downtime

Answer + AI explanation with Pro

1. A.A vMotion variant that encrypts the migration traffic in transit, mandatory for encrypted VMs and optional otherwise
2. B.restarting VMs on surviving hosts after a host failure
3. C.A DRS rule that keeps specified VMs running on the same host (VM-VM affinity) or a defined host group (VM-host affinity)
4. D.load-balancing VMs across hosts using vMotion

Answer + AI explanation with Pro

1. A.vMotion
2. B.Per-VM EVC
3. C.DRS VM-host affinity rules
4. D.DRS

Answer + AI explanation with Pro

1. A.DRS — All-Paths-Down is a transient loss of storage paths; Permanent Device Loss is a definitive SCSI sense indicating the device is gone.
2. B.DRS — Migrates VMs between hosts managed by different vCenters, even across SSO domains in vSphere 8.
3. C.DRS — load-balancing VMs across hosts using vMotion
4. D.DRS — XenServer/XCP-ng live migration of a running VM

Answer + AI explanation with Pro

1. A.restarting VMs on surviving hosts after a host failure
2. B.load-balancing VMs across hosts using vMotion
3. C.The configured action (leave powered on, power off, shut down) a host takes when it loses management network and cannot reach isolation addresses
4. D.a lockstep secondary VM giving zero-downtime, no-data-loss failover

Answer + AI explanation with Pro

1. A.Post-copy live migration
2. B.Fault Tolerance (FT)
3. C.Stretched cluster
4. D.Host failures to tolerate

Answer + AI explanation with Pro

1. A.Fault Tolerance (FT) — A third lightweight component in a two-site stretched cluster or vSAN that breaks quorum ties and decides which site survives a partition
2. B.Fault Tolerance (FT) — Admission-control setting reserving enough capacity to restart all VMs after losing the specified number of hosts.
3. C.Fault Tolerance (FT) — Recovery Time Objective: the maximum acceptable time to restore a service after an outage
4. D.Fault Tolerance (FT) — a lockstep secondary VM giving zero-downtime, no-data-loss failover

Answer + AI explanation with Pro

1. A.A vMotion variant that encrypts the migration traffic in transit, mandatory for encrypted VMs and optional otherwise
2. B.Admission-control setting reserving enough capacity to restart all VMs after losing the specified number of hosts.
3. C.zero-downtime migration of a running VM between hosts
4. D.a saved-state VM move with a brief pause

Answer + AI explanation with Pro

1. A.Datastore heartbeating
2. B.Stretched cluster
3. C.Hyper-V Live Migration
4. D.Fault Tolerance (FT)

Answer + AI explanation with Pro

1. A.Hyper-V Live Migration — The default migration model (vMotion, KVM) that iteratively copies dirty memory pages to the destination while the source runs, then briefly pauses to copy the last delta
2. B.Hyper-V Live Migration — Evacuates VMs from a host flagged as degraded by a hardware health provider before it fully fails.
3. C.Hyper-V Live Migration — zero-downtime migration of a running VM between hosts
4. D.Hyper-V Live Migration — A KVM/QEMU migration mode that switches execution to the destination immediately and pulls remaining pages on demand, bounding downtime but risking failure if the network drops mid-migration

Answer + AI explanation with Pro

1. A.load-balancing VMs across hosts using vMotion
2. B.a saved-state VM move with a brief pause
3. C.Shared visibility of the VM, compatible CPUs (or EVC), a vMotion-enabled VMkernel, and sufficient bandwidth.
4. D.A feature that evacuates VMs off a host flagged as degraded by a hardware health provider before an actual failure occurs

Answer + AI explanation with Pro

1. A.Cross vCenter vMotion
2. B.DRS
3. C.Hyper-V Live Migration
4. D.Quick Migration

Answer + AI explanation with Pro

1. A.Quick Migration — live migration of a running VM between ESXi hosts with no downtime
2. B.Quick Migration — A feature that evacuates VMs off a host flagged as degraded by a hardware health provider before an actual failure occurs
3. C.Quick Migration — a saved-state VM move with a brief pause
4. D.Quick Migration — Shared visibility of the VM, compatible CPUs (or EVC), a vMotion-enabled VMkernel, and sufficient bandwidth.

Answer + AI explanation with Pro

1. A.a rule keeping specified VMs together on the same host
2. B.A migration that changes both compute host and datastore in one operation, working even between hosts with no shared storage
3. C.Migrates VMs between hosts managed by different vCenters, even across SSO domains in vSphere 8.
4. D.live migration of a VM's disk files between datastores

Answer + AI explanation with Pro

1. A.Stretched cluster
2. B.Maintenance mode evacuation
3. C.affinity rule
4. D.Witness node

Answer + AI explanation with Pro

1. A.affinity rule — a rule keeping specified VMs together on the same host
2. B.affinity rule — live migration of a running VM between ESXi hosts with no downtime
3. C.affinity rule — A DRS rule that keeps specified VMs on separate hosts so a single host failure cannot take down all members of a clustered application
4. D.affinity rule — HA uses shared datastores as a secondary liveness channel to distinguish host isolation from host failure.

Answer + AI explanation with Pro

1. A.The configured action (leave powered on, power off, shut down) a host takes when it loses management network and cannot reach isolation addresses
2. B.The default migration model (vMotion, KVM) that iteratively copies dirty memory pages to the destination while the source runs, then briefly pauses to copy the last delta
3. C.HA uses shared datastores as a secondary liveness channel to distinguish host isolation from host failure.
4. D.a rule keeping specified VMs apart on different hosts

Answer + AI explanation with Pro

1. A.vSphere HA admission control
2. B.Pre-copy live migration
3. C.XenMotion
4. D.anti-affinity rule

Answer + AI explanation with Pro

1. A.anti-affinity rule — A vMotion variant that encrypts the migration traffic in transit, mandatory for encrypted VMs and optional otherwise
2. B.anti-affinity rule — a rule keeping specified VMs apart on different hosts
3. C.anti-affinity rule — a saved-state VM move with a brief pause
4. D.anti-affinity rule — Migrates VMs between hosts managed by different vCenters, even across SSO domains in vSphere 8.

Answer + AI explanation with Pro

1. A.A migration that changes both compute host and datastore in one operation, working even between hosts with no shared storage
2. B.XenServer/XCP-ng live migration of a running VM
3. C.Recovery Point Objective: the maximum acceptable amount of data loss measured as time since the last recoverable copy
4. D.zero-downtime migration of a running VM between hosts

Answer + AI explanation with Pro

1. A.Replication-based DR
2. B.Pre-copy live migration
3. C.anti-affinity rule
4. D.XenMotion

Answer + AI explanation with Pro

1. A.XenMotion — XenServer/XCP-ng live migration of a running VM
2. B.XenMotion — A DRS rule that keeps specified VMs running on the same host (VM-VM affinity) or a defined host group (VM-host affinity)
3. C.XenMotion — a lockstep secondary VM giving zero-downtime, no-data-loss failover
4. D.XenMotion — Asynchronously copying VM data to a recovery site so workloads can be restarted there within the RPO after a primary-site loss

Answer + AI explanation with Pro