Question 550
In the Bayview Compliance pilot environment, a controlled verification is required for: A desktop policy logs off every active user at a short timeout even when they are running a lengthy approved batch job. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
A long-running authorized job completes while genuinely idle sessions still release capacity after the intended duration. This is an independently observable result of the targeted change: Differentiate idle, active, and disconnected session timeout requirements and configure compatible limits for the pool. It closes the specific Bayview Compliance failure: A desktop policy logs off every active user at a short timeout even when they are running a lengthy approved batch job.
Incorrect Answers
After the correct tenant sign-in the user sees the expected workspace resources and launches a desktop. This is evidence for a DIFFERENT remediation: Validate client account context, workspace subscription, and application group assignment before rebuilding session hosts. That remediation addresses: Users receive an empty workspace feed after a Windows App update because the desktop client is signed into a different Entra tenant. It does not establish resolution of the Bayview Compliance problem: A desktop policy logs off every active user at a short timeout even when they are running a lengthy approved batch job. The required outcome here is: A long-running authorized job completes while genuinely idle sessions still release capacity after the intended duration.
The replacement user receives the intended machine and the former user's sign-in is denied without deleting retained data unlawfully. This is evidence for a DIFFERENT remediation: Unassign the former user and reassign the personal desktop through the supported host pool assignment process with data retention checks. That remediation addresses: An employee leaves and their assigned personal desktop remains inaccessible to a replacement because the assignment was never removed. It does not establish resolution of the Bayview Compliance problem: A desktop policy logs off every active user at a short timeout even when they are running a lengthy approved batch job. The required outcome here is: A long-running authorized job completes while genuinely idle sessions still release capacity after the intended duration.
A controlled idle session follows the configured warning and disconnect or logoff sequence within the approved timeout. This is evidence for a DIFFERENT remediation: Apply appropriate session idle, active, and disconnected time-limit policies with user communication and save-work protection. That remediation addresses: Disconnected pooled sessions consume capacity indefinitely because no idle or disconnected session limits are defined. It does not establish resolution of the Bayview Compliance problem: A desktop policy logs off every active user at a short timeout even when they are running a lengthy approved batch job. The required outcome here is: A long-running authorized job completes while genuinely idle sessions still release capacity after the intended duration.