AZ-140 · Question #318
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 h
The correct answer is B. No. This is another variant in the same series. The proposed solution here also fails to fully satisfy the private connectivity requirement. A common reason for 'No' in this variant is that the solution configures a private DNS zone or network rule without deploying the private endpo
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 configure network peering for Vnet1. Does this meet the goal?
Options
- AYes
- BNo
How the community answered
(30 responses)- A17% (5)
- B83% (25)
Explanation
This is another variant in the same series. The proposed solution here also fails to fully satisfy the private connectivity requirement. A common reason for 'No' in this variant is that the solution configures a private DNS zone or network rule without deploying the private endpoint itself, or it modifies firewall rules on storage1 without disabling public network access - meaning traffic could still route publicly. To correctly ensure session hosts connect to share1 over private connectivity only, you must: (1) create a private endpoint for storage1 in VNet1, (2) link a private DNS zone (privatelink.file.core.windows.net) to VNet1, and (3) optionally restrict public access on the storage account. This proposed solution omits a critical step, so the answer is No.
Community Discussion
No community discussion yet for this question.