A technician says the cluster will vMotion a clerk desktop if the city puts an ESXi host in maintenance. Which associate-level idea is that?
Select an answer to reveal the explanation.
Short Explanation
Maintenance mode is like closing one teller window while the clerk keeps talking. vMotion walks the running desktop VM to another host so the session does not die. That is vSphere terminology, not an NSX lab.
Full Explanation
vMotion live migration lets the city put an ESXi host into maintenance while a clerk desktop VM moves without killing the VDI session. In municipal EUC terms, treat the endpoint as a window into city systems when the architecture says so, not as the system of record for the files or apps in the stem. Distractor concept: NSX overlay failover is not what live-migrates the guest VM for host maintenance. Distractor concept: App Volumes detach is not the prerequisite that defines maintenance-mode migration. Distractor concept: Horizon Cloud Control Plane is not required for on-prem vMotion of a running desktop VM. Exam caveat: Maintenance mode + running desktop survives = vMotion; not NSX, App Volumes, or cloud-plane exclusivity. Operational check: Enter maintenance on a host with a test VDI VM, confirm vMotion completes, and verify the Horizon session stays up. Record the chosen control and the rejected failure modes in the civic change ticket or runbook so on-call staff and auditors share the same rationale after the next maintenance window. Re-validate after personnel or image changes that the same control still meets the city's continuity, security, and support expectations for this service.