An administrator is configuring vSphere Lifecycle Manager to install patches to a vSphere cluster. The cluster runs workload virtual machines (VMs) that are incompatible with vSphere vMotion, and therefore cannot be live migrated between hosts during the installation of the patches.
Which configuration in vSphere Lifecycle Manager will allow the administrator to reduce the downtime associated with the patching operation without migrating the VMs?
To minimize downtime associated with patching operations when VMs cannot be live-migrated, the best option is to use Quick Boot along with the 'suspend to memory' state. Quick Boot allows the ESXi host to reboot without requiring a full hardware initialization, significantly reducing the time required for reboot. Suspending VMs to memory ensures that they can resume their state quickly once the host is back online. This combination reduces downtime as compared to other methods, making it the most efficient solution for this scenario.
Together with Quick Boot, the Suspend to memory option provides faster host upgrades. vSphere Lifecycle Managersuspends to the host memory and not to the disk the powered on virtual machines on the host. After the Quick Boot, the suspended virtual machines are resumed from memory. https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-lifecycle-manager/GUID-06A5D316-9452-4A5D-A5BB-3AEEFE0483B4.html#:~:text=memory%20option%20is%20dimmed.-,Together%20with%20Quick%20Boot%2C%20the%20Suspend%20to%20memory%20option%20provides%20faster%20host%20upgrades.,-vSphere%20Lifecycle%20Managersuspends
https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-lifecycle-manager/GUID-06A5D316-9452-4A5D-A5BB-3AEEFE0483B4.html
The answer looks to be correct. Quick boot + suspend memory allows you to more quickly patch a host when vMotion cannot be used with VMs. https://kb.vmware.com/s/article/81555
This was my answer, passed with 452