You must patch several session hosts without disrupting active users and want each VM to deallocate after the last user signs out. What should you do? (Choose two.)

Setting "Allow new sessions" to "No" (drain mode) on each session host prevents new user connections while allowing existing users to finish their work. This ensures no disruption to active users. Once all active sessions on a host have ended, the session count will reach zero, making the host safe to patch. After the last session ends, stopping (deallocating) the VM from Azure releases its compute resources, which is crucial for cost optimization and ensures the VM is in a clean state before patching. Immediately removing a VM from the host pool would disconnect active users, causing disruption. Setting the host pool's Max sessions limit to 0 would drain all hosts simultaneously, which might not be desirable if you want to patch hosts individually or in smaller batches. Redeploying the VM OS from an image is an extreme measure and would erase user profiles and data, which is not the goal here.