AVD Automatic Sign-Out on Disconnect GPO
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an Azure Virtual Desktop deployment. You need to ensure that users are signed out automatically when they disconnect from a session. Solution: From the Local Group Policy Editor, you configure the Remote Session Environment settings. Does this meet the goal?
Community Votes
73% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
This question tests knowledge of specific Group Policy nodes for AVD session timeouts; the common trap is confusing the Remote Session Environment node with the Session Time Limits node.
Configuring the Remote Session Environment settings in Local Group Policy does not set disconnected session time limits for Azure Virtual Desktop. This page establishes that the correct GPO node is Session Time Limits, making the proposed solution incorrect.
Choosing Yes because both nodes exist under Remote Desktop Session Host, but only Session Time Limits controls the disconnected session timeout.
Community Discussion (8 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct answer is No because the "Remote Session Environment" Group Policy node does not contain the setting to automatically sign out users upon disconnection. The policy that enforces this behavior, "Set time limit for disconnected sessions," is located exclusively under the "Session Time Limits" node. Thus, configuring Remote Session Environment fails to meet the stated goal.Why the Other Options Are Wrong
Choosing Yes is incorrect because it assumes the timeout setting is broadly grouped with environment configurations like RemoteFX or display rendering. While both nodes reside under the Remote Desktop Session Host parent container, their policy scopes are entirely distinct. Remote Session Environment handles visual and hardware policies, not session lifecycle management.Community Comment Notes
Commenters correctly identified the exact GPO path required, noting that "it's not under Remote Session Environment settings but under... Session Time Limits" as smartleb961 pointed out. Others concisely affirmed that "Remote Session Environment is wrong" as lusis987 stated. Those who argued for Yes likely confused the parent directory or relied on inaccurate AI responses.Official Reference
Exam Strategy
When tested on Group Policy paths for AVD, carefully distinguish between session lifecycle policies (Session Time Limits) and rendering/hardware policies (Remote Session Environment). Memorize the exact node names under the Remote Desktop Session Host container.
Related Analysis
Practice All AZ-140 Questions
Access 64 questions with complete answers and detailed explanations.
View Full AZ-140 Practice Test →