Question 40
In the Horizon Field Operations pilot environment, a controlled verification is required for: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses. This is an independently observable result of the targeted change: Implement supported Azure Virtual Desktop Private Link private endpoints and required private DNS resolution for the appropriate service connections. It closes the specific Horizon Field Operations failure: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link.
Incorrect Answers
Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads. This is evidence for a DIFFERENT remediation: Define and deploy an appropriate end-to-end QoS marking and prioritization policy for AVD real-time traffic consistent with the network design. That remediation addresses: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. It does not establish resolution of the Horizon Field Operations problem: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link. The required outcome here is: From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.
The failing VPN client path is identified and a corrected route or rule permits a full authenticated session without broad firewall exemptions. This is evidence for a DIFFERENT remediation: Use AVD diagnostics, effective routes, NSG flow observations, and path tests to isolate the failing transport or DNS dependency. That remediation addresses: AVD sign-in works from the corporate LAN but fails over a regional VPN; the support team assumes successful host health rules out network problems. It does not establish resolution of the Horizon Field Operations problem: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link. The required outcome here is: From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.
Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency. This is evidence for a DIFFERENT remediation: Review the required Azure Virtual Desktop Private Link subresources, endpoint approvals, network routes, and private DNS zones rather than opening general internet access. That remediation addresses: Session hosts can resolve an AVD private endpoint IP but cannot finish registration after a new private endpoint was added without correct service subresource coverage. It does not establish resolution of the Horizon Field Operations problem: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link. The required outcome here is: From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.