Question 180
A post-change operational risk review considers: A team changes maximum sessions per host without testing peak-hour user placement. Which risk MOST DIRECTLY explains the need for the proposed AVD control?
Explanation
Correct Answer
The condition is: A team changes maximum sessions per host without testing peak-hour user placement. The directly related risk is: A host pool with incompatible properties or unmanaged session behavior can create repeated reconnect failures and capacity problems. The corrective control is: Configure supported host-pool session settings, connection limits and validation according to pooled or personal desktop requirements. Its test of effectiveness is: Controlled logon and reconnection tests show users land on the correct hosts and policies take effect. This issue is specific to the observed AVD behavior, not to a separate administration concern.
Incorrect Answers
This option relates to Portal host pool and workspace provisioning under AZ-140 objective group 1.4. It addresses a different failure risk: Creating a session host without an accessible application group and registered workspace will not publish a usable desktop feed. But the observed requirement is: A team changes maximum sessions per host without testing peak-hour user placement. For the targeted topic (Host pool session settings and reconnection behavior), the directly relevant risk is: A host pool with incompatible properties or unmanaged session behavior can create repeated reconnect failures and capacity problems. That other measure may be useful in a separate environment, but does not by itself establish the specific requested outcome. An independent qualified Azure Virtual Desktop expert must adjudicate any plausible overlapping alternatives before release.
This option relates to Host pool drain mode and safe maintenance under AZ-140 objective group 1.4. It addresses a different failure risk: Patching an active pooled host without draining can interrupt current users and trigger new sessions during repair. But the observed requirement is: A team changes maximum sessions per host without testing peak-hour user placement. For the targeted topic (Host pool session settings and reconnection behavior), the directly relevant risk is: A host pool with incompatible properties or unmanaged session behavior can create repeated reconnect failures and capacity problems. That other measure may be useful in a separate environment, but does not by itself establish the specific requested outcome. An independent qualified Azure Virtual Desktop expert must adjudicate any plausible overlapping alternatives before release.
This option relates to Host agent health and troubleshooting registration under AZ-140 objective group 1.4. It addresses a different failure risk: A running virtual machine is not necessarily a healthy AVD session host when the agent, registration or domain trust fails. But the observed requirement is: A team changes maximum sessions per host without testing peak-hour user placement. For the targeted topic (Host pool session settings and reconnection behavior), the directly relevant risk is: A host pool with incompatible properties or unmanaged session behavior can create repeated reconnect failures and capacity problems. That other measure may be useful in a separate environment, but does not by itself establish the specific requested outcome. An independent qualified Azure Virtual Desktop expert must adjudicate any plausible overlapping alternatives before release.