Question 290
After deploying Depth-first configuration via Azure CLI to switch a pooled host pool to density-first placement with an explicitly tested maximum session limit, what direct observation provides the strongest acceptance evidence?
Explanation
Correct Answer
This is the direct functional outcome for Depth-first configuration via Azure CLI: a hostpool show command reports DepthFirst and its target maxSessionLimit. CLI can configure the pooled load balancing and session limit. The observed behavior supports the specified acceptance requirement.
Incorrect Answers
That evidence concerns Personal desktop direct user assignment, used to assign a named user to a selected persistent Windows VM within the personal host pool. It does not establish whether Depth-first configuration via Azure CLI satisfies the current requirement to switch a pooled host pool to density-first placement with an explicitly tested maximum session limit.
That evidence concerns Pooled host drain mode before patching, used to protect existing sessions while stopping new session assignments to a host scheduled for reboot. It does not establish whether Depth-first configuration via Azure CLI satisfies the current requirement to switch a pooled host pool to density-first placement with an explicitly tested maximum session limit.
That evidence concerns Remove personal desktop assignment, used to return an assigned VM to an unassigned pool after the prior user leaves, while meeting data-retention procedures. It does not establish whether Depth-first configuration via Azure CLI satisfies the current requirement to switch a pooled host pool to density-first placement with an explicitly tested maximum session limit.






Configuring and Operating Microsoft Azure Virtual Desktop (AZ-140) Practice Tests