During ramp-down, a host has no active users but has disconnected sessions. The policy requires no sessions before deallocation, and forced sign-out is disabled. Why might it stay running?

✓ Correct answer

• Disconnected sessions still exist, so the no-sessions condition has not been met.

Read the configured shutdown condition precisely. No active sessions and no sessions are different requirements, and disconnected sessions can keep the latter unmet. Option explanations: A. The host’s image version number dictates deallocation eligibility.: Image version metadata is not the session-state shutdown condition. B. Drain mode automatically forces sign-out but takes exactly one day.: Drain mode does not force sign-out or define such a delay. C. A disconnected session is already signed out and therefore cannot affect shutdown.: Session state persists after disconnect and can affect eligibility. D. Disconnected sessions still exist, so the no-sessions condition has not been met.: Disconnecting does not end a session; the stated policy waits until sessions are gone. Sources: Create a scaling plan — https://learn.microsoft.com/en-us/azure/virtual-desktop/autoscale-create-assign-scaling-plan; Drain mode — https://learn.microsoft.com/en-us/azure/virtual-desktop/drain-mode

Read the source reference