Does Session Time Limits Meet the AVD Auto Sign-Out Goal?
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 Session Time Limits settings. Does this meet the goal?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests whether an RD Session Host Group Policy set (Session Time Limits) is an accepted way to force sign-out on disconnect in AVD; the trap is assuming session limits only disconnect sessions or that local GPO is ignored on AVD hosts.
In an Azure Virtual Desktop deployment, the Session Time Limits policies in the Local Group Policy Editor can sign users out automatically when they disconnect, because the disconnected-session time limit terminates the session at expiry. This page confirms that the proposed solution meets the stated goal and explains why the answer is Yes.
Choosing 'No' by assuming Session Time Limits only tidies up disconnected sessions or that only AVD-specific host pool settings/FSLogix can end sessions; in fact the disconnected-session time limit terminates the session, which logs the user off.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Every AVD session host runs the Remote Desktop Session Host role, so the Session Time Limits policy set is honored and directly controls what happens to a session after a user disconnects. Under Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits, the setting "Set time limit for disconnected sessions" ends a disconnected session when the configured limit expires, and an ended session means the user is signed out, not left lingering in a disconnected state. Enabling "End session when time limits are reached" reinforces this by terminating the session rather than allowing it to be reconnected after the limit. Because the goal is exactly "users are signed out automatically when they disconnect from a session," configuring these policies meets the goal, and the source key's answer of Yes is correct.Why the Other Options Are Wrong
The only competing option is No, which would be defensible only if the configuration merely disconnected sessions or if AVD session hosts ignored RDS host policies. Neither is true: Session Time Limits is the documented RDS host mechanism for ending idle and disconnected sessions, and Local Group Policy Editor writes those settings straight into the session host's registry. A No answer would fit a different solution in this series, such as one that only set an active-session idle limit, which ends idle sessions but never addresses the disconnect scenario, or one that configured unrelated components like FSLogix containers or host pool RDP properties. Since the proposed setting targets disconnection specifically and terminates the session, No cannot be justified here.Community Comment Notes
Bonesurfer marks the answer correct and reproduces the exact Group Policy path under Computer Configuration > Administrative Templates, confirming the policies sit in the RD Session Host branch rather than somewhere unrelated. jeff1988 zeroes in on the decisive policy, describing it as "Set time limit for disconnected sessions," which ensures users are signed out after the specified disconnection period, which is precisely the behavior the goal requires. Roee1 simply states it is correct, and the 100% Yes vote matches that reading. No commenter argues for an alternative mechanism such as host pool RDP properties or Intune, so the community shows no real dispute here.Note that Local Group Policy is per-host, so in a real fleet you would replicate it with domain GPO or Intune, but that operational point does not change whether the solution meets the goal.
Official Reference
Exam Strategy
In AVD scenario-series questions, first identify whether the proposed mechanism actually terminates the session or only disconnects it, because that single distinction decides Yes versus No. Session Time Limits set through Group Policy is a legitimate termination method, so treat it as a valid solution unless the scenario shows it was pointed at the wrong type of limit.
Frequently Asked Questions
Which Session Time Limits setting actually logs the user off in AVD?
"Set time limit for disconnected sessions" ends the session once the limit expires, which signs the user out. Adding "End session when time limits are reached" ensures termination instead of a lingering disconnected session.
Is Local Group Policy the best place to set session time limits on AVD hosts?
It works and meets the goal, but local policy must be applied to each session host and is lost on reimage. Domain GPO or Intune is preferable for fleets, though that does not change the answer here.
Related Analysis
Practice All AZ-140 Questions
Access 64 questions with complete answers and detailed explanations.
View Full AZ-140 Practice Test →