You operate a pooled host pool and want to spread user sessions evenly across all available session hosts to minimize memory pressure on any single VM. Which load-balancing algorithm should you configure?

Breadth-first is the correct load-balancing algorithm because it distributes new user sessions evenly across all available session hosts in a pooled host pool. This approach ensures that no single VM becomes overloaded, minimizing memory pressure and improving overall performance and user experience. Depth-first, conversely, fills one session host to its maximum session limit before moving to the next. While this can reduce the number of active VMs, it concentrates load and increases memory pressure on fewer hosts. Round-robin is not a standard load-balancing option in Azure Virtual Desktop. Least sessions is also not a standard load-balancing option; while it sounds like it would distribute load, Azure Virtual Desktop's built-in options are Breadth-first and Depth-first.