Configuring Automatic Scaling for Azure Virtual Desktop Host Pool
Question
Your company has an AVD host pool that runs Windows 10 Enterprise multi-session.
You have been asked to configure the automatic scaling for the host pool in such a way that the following 2 requirements are met: New user sessions should be distributed across all running session hosts.
A new session host should be started automatically when concurrent user sessions surpass 30 users per host.
What would you consider in the solution?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: C
Depth-first load balancing allows the users to saturate a session host with user sessions in a host pool.
Once the 1st session host touches its session limit threshold, any new user connections are directed by the load balancer to the next session host in the host pool until its limit is reached and so on.
Option A is incorrect.
To meet the goal, there is a need for an Azure Automation account and depth-first load balancing algorithm, not breadth-first.
Option B is incorrect.
There is a need for the Azure automation account to meet the goal.
Option C is correct.
An Azure Automation account and the depth-first load-balancing algorithm is required to meet the given requirements.
Option D is incorrect.
There is a need for an Azure automation account to meet the goal, Azure load balance won't help.
References:
To know more about load balancing algorithms, please visit the below-given link:
To meet the requirements mentioned in the question, you would need to configure automatic scaling for the host pool using an Azure Automation account and the breadth-first load balancing algorithm.
Breadth-first load balancing ensures that new user sessions are distributed across all running session hosts, and the Azure Automation account will allow you to automatically start a new session host when concurrent user sessions surpass 30 users per host.
Option B, which suggests using an Azure load balancer and the breadth-first load balancing algorithm, does not meet the second requirement of automatically starting a new session host when concurrent user sessions surpass 30 users per host.
Option C, which suggests using an Azure Automation account and the depth-first load balancing algorithm, is not appropriate as the depth-first algorithm is designed to prioritize filling up one session host before moving on to the next, which does not meet the requirement of distributing new user sessions across all running session hosts.
Option D, which suggests using an Azure load balancer and the depth-first load balancing algorithm, is also not appropriate for the same reasons as Option C.
In summary, Option A - using an Azure Automation account and the breadth-first load balancing algorithm - is the best solution for meeting the requirements stated in the question.
