AZ-140 · Question #304
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. Adding a lock in Azure does not prevent new user sessions from being initiated on the session host. Locks in Azure are generally used to prevent resources from being deleted or modified, but they don't control session management.
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 an Azure Virtual Desktop host pool that runs Windows 10 Enterprise multi-session. User sessions are load-balanced between the session hosts. Idle session timeout is 30 minutes. You plan to shut down a session host named Host1 to perform routine maintenance. You need to prevent new user sessions to Host1 without disconnecting active user sessions. Solution: From the Azure portal, add lock on Host1. Does this meet the goal?
Options
- AYes
- BNo
How the community answered
(24 responses)- A25% (6)
- B75% (18)
Explanation
Adding a lock in Azure does not prevent new user sessions from being initiated on the session host. Locks in Azure are generally used to prevent resources from being deleted or modified, but they don't control session management.
Community Discussion
No community discussion yet for this question.