Private AVD records resolve correctly in Azure, but an on-premises VPN client still gets public AVD addresses from its corporate resolver. Private routing is available. What should be fixed first?

Choose the single best answer.

A.Grant a user broader file-share ACLs
B.Increase the session-host VM size
C.Remove all private endpoints
D.Corporate DNS resolution/forwarding to the appropriate linked private zones

Show the answer and explanation

✓ Correct answer

Corporate DNS resolution/forwarding to the appropriate linked private zones

The failure is in the client's name-resolution path. Configure forwarding/resolution for the private AVD zones and retest from that network. Option explanations: A. Grant a user broader file-share ACLs: File ACLs cannot change AVD service DNS resolution. B. Increase the session-host VM size: VM compute capacity does not correct DNS answers. C. Remove all private endpoints: Removing the private design does not meet the private-access requirement. D. Corporate DNS resolution/forwarding to the appropriate linked private zones: The client must resolve the relevant AVD names to the private addresses for the intended workflow. Sources: Azure Private Link with Azure Virtual Desktop — https://learn.microsoft.com/en-us/azure/virtual-desktop/private-link-overview; Set up Private Link with Azure Virtual Desktop — https://learn.microsoft.com/en-us/azure/virtual-desktop/private-link-setup

Read the source reference

Read and review here, or open the app to practise and save your results on this device.

Practise in the app

Unofficial study aid, not affiliated with or endorsed by Microsoft. Original educational practice questions, not official exam questions or a prediction of an exam result. Use Microsoft Learn and hands-on labs alongside this course.