AZ-140 · Question #316
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 A. Yes. You add a private endpoint to storage1. You can use Azure Private Link with Azure Virtual Desktop to privately connect to your remote resources. By creating a private endpoint, traffic between your virtual network and the service remains on the Microsoft network, so you no…
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 subscription that contains a virtual network named VNet1, a storage account named storage1, and five Azure Virtual Desktop session hosts. VNet1 and storage1 are in the East US Azure region. The session hosts are connected to VNet1. In storage1, you create an Azure Files share named share1. You need to ensure that the session hosts connect to share1 by using the Microsoft backbone network. Solution: You add a private endpoint to storage1. Does this meet the goal?
Options
- AYes
- BNo
How the community answered
(50 responses)- A82% (41)
- B18% (9)
Explanation
- You add a private endpoint to storage1. You can use Azure Private Link with Azure Virtual Desktop to privately connect to your remote resources. By creating a private endpoint, traffic between your virtual network and the service remains on the Microsoft network, so you no longer need to expose your service to the public https://learn.microsoft.com/en-us/azure/virtual-desktop/private-link-overview
Community Discussion
No community discussion yet for this question.