AZ-140 · Question #28
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…
The correct answer is B. No. Modifying the RDP Properties of a host pool (Session behavior settings) controls RDP connection parameters such as display resolution, audio redirection, and device redirection - it does NOT configure idle session timeout limits. Idle and disconnected session timeouts for Azure…
Question
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 a Azure Virtual Desktop host pool named Pool1 that is integrated with an Azure Active Directory Domain Services (Azure AD DS) managed domain. You need to configure idle session timeout settings for users that connect to the session hosts in Pool1. Solution: From the Azure portal, you modify the Session behavior settings in the RDP Properties of Pool1. Does that meet the goal?
Options
- AYes
- BNo
How the community answered
(23 responses)- A22% (5)
- B78% (18)
Explanation
Modifying the RDP Properties of a host pool (Session behavior settings) controls RDP connection parameters such as display resolution, audio redirection, and device redirection - it does NOT configure idle session timeout limits. Idle and disconnected session timeouts for Azure Virtual Desktop session hosts are managed through Group Policy Objects (GPOs), specifically under: Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits. Since the host pool is integrated with Azure AD DS, the correct approach is to configure a GPO in Azure AD DS and link it to the OU containing the session hosts. The proposed portal-based solution does not meet the goal.
Topics
Community Discussion
No community discussion yet for this question.