McAfee-Secured Website

Exam Bundle

Exam Code: AZ-140

Exam Name Configuring and Operating Microsoft Azure Virtual Desktop

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Virtual Desktop Specialty

Microsoft AZ-140 Bundle $44.99

100% Microsoft AZ-140 Guaranteed Success With Testking Training Materials

Get Real AZ-140 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    AZ-140 Questions & Answers

    372 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual AZ-140 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • AZ-140 Video Course

    AZ-140 Video Course

    79 Video Lectures

    AZ-140 Video Course is developed by Microsoft Professionals to help you pass the AZ-140 exam.

    Description

    This course will improve your knowledge and skills required to pass Configuring and Operating Microsoft Azure Virtual Desktop exam.
  • Study Guide

    AZ-140 Study Guide

    430 PDF Pages

    Developed by industry experts, this 430-page guide spells out in painstaking detail all of the information you need to ace AZ-140 exam.

Configuring and Operating Microsoft Azure Virtual Desktop (AZ-140) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    372 Questions

    $124.99
  • AZ-140 Video Course

    Video Course

    79 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    430 PDF Pages

    $29.99

Microsoft AZ-140 Practice Test 4

Question 30

In the Aspen Research Group pilot environment, a controlled verification is required for: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. What evidence best demonstrates that the reported AVD issue is resolved?

  1. A session host resolves the correct private storage endpoint and mounts the profile share without using a public DNS answer.
  2. Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.
  3. The failing VPN client path is identified and a corrected route or rule permits a full authenticated session without broad firewall exemptions.
  4. Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

Explanation

Correct Answer

B:

Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect. This is an independently observable result of the targeted change: Use supported Windows App versions and RDP Shortpath connectivity so built-in RDP Multipath can maintain and switch viable transport paths. It closes the specific Aspen Research Group failure: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent.

Incorrect Answers

A:

A session host resolves the correct private storage endpoint and mounts the profile share without using a public DNS answer. This is evidence for a DIFFERENT remediation: Configure and test DNS resolution for the session host subnet with conditional forwarding or private DNS integration matching the storage endpoints. That remediation addresses: Session hosts in a hub-and-spoke deployment cannot resolve private file share names because the spoke VNet uses a DNS server without the needed forwarders. It does not establish resolution of the Aspen Research Group problem: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. The required outcome here is: Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

C:

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 Aspen Research Group problem: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. The required outcome here is: Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

D:

Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect. This is evidence for a DIFFERENT remediation: Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls. That remediation addresses: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. It does not establish resolution of the Aspen Research Group problem: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. The required outcome here is: Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

Question 31

At Clearwater Apps, a line-of-business apps organization prioritizing reproducible RemoteApp rollout, administrators observe this issue: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. Which targeted engineering action most directly resolves the reported problem?

  1. Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls.
  2. Use supported Windows App versions and RDP Shortpath connectivity so built-in RDP Multipath can maintain and switch viable transport paths.
  3. Review the required Azure Virtual Desktop Private Link subresources, endpoint approvals, network routes, and private DNS zones rather than opening general internet access.
  4. Inspect RDP connection information and session host network logs, then verify the UDP reachability and Shortpath configuration for the actual path.

Explanation

Correct Answer

B:

Use supported Windows App versions and RDP Shortpath connectivity so built-in RDP Multipath can maintain and switch viable transport paths. This directly addresses the Clearwater Apps failure: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. The necessary acceptance evidence is: Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

Incorrect Answers

A:

Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls. This could resolve a DIFFERENT AVD issue: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. It does not fix the reported Clearwater Apps problem: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. The relevant proof here is: Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

C:

Review the required Azure Virtual Desktop Private Link subresources, endpoint approvals, network routes, and private DNS zones rather than opening general internet access. This could resolve a DIFFERENT AVD issue: 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 fix the reported Clearwater Apps problem: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. The relevant proof here is: Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

D:

Inspect RDP connection information and session host network logs, then verify the UDP reachability and Shortpath configuration for the actual path. This could resolve a DIFFERENT AVD issue: A session host reports Available yet RDP Shortpath remains inactive; engineers troubleshoot only Azure VM power state rather than the connection transport. It does not fix the reported Clearwater Apps problem: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. The relevant proof here is: Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

Question 32

The line-of-business apps desktop team at Clearwater Apps requires independent proof of remediation for: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. What measurable result should the reviewer require before closing the incident?

  1. Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.
  2. Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.
  3. Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.
  4. A test session uses the expected UDP transport and logs show no remaining policy or NAT negotiation failures.

Explanation

Correct Answer

C:

Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect. This is an independently observable result of the targeted change: Use supported Windows App versions and RDP Shortpath connectivity so built-in RDP Multipath can maintain and switch viable transport paths. It closes the specific Clearwater Apps failure: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent.

Incorrect Answers

A:

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 Clearwater Apps problem: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. The required outcome here is: Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

B:

Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect. This is evidence for a DIFFERENT remediation: Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls. That remediation addresses: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. It does not establish resolution of the Clearwater Apps problem: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. The required outcome here is: Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

D:

A test session uses the expected UDP transport and logs show no remaining policy or NAT negotiation failures. This is evidence for a DIFFERENT remediation: Inspect RDP connection information and session host network logs, then verify the UDP reachability and Shortpath configuration for the actual path. That remediation addresses: A session host reports Available yet RDP Shortpath remains inactive; engineers troubleshoot only Azure VM power state rather than the connection transport. It does not establish resolution of the Clearwater Apps problem: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. The required outcome here is: Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

Question 33

For the hybrid desktops workload at Atlas Digital Systems, the host pool team reports: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. What is the most appropriate first corrective action for this AVD scenario?

  1. Define and deploy an appropriate end-to-end QoS marking and prioritization policy for AVD real-time traffic consistent with the network design.
  2. Plan capacity against observed high-percentile bandwidth and bursty sign-ins, incorporating headroom for concurrent Microsoft Teams meetings.
  3. Inspect RDP connection information and session host network logs, then verify the UDP reachability and Shortpath configuration for the actual path.
  4. Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls.

Explanation

Correct Answer

A:

Define and deploy an appropriate end-to-end QoS marking and prioritization policy for AVD real-time traffic consistent with the network design. This directly addresses the Atlas Digital Systems failure: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. The necessary acceptance evidence is: Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.

Incorrect Answers

B:

Plan capacity against observed high-percentile bandwidth and bursty sign-ins, incorporating headroom for concurrent Microsoft Teams meetings. This could resolve a DIFFERENT AVD issue: An acquired branch connects through an undersized VPN and the team projects total desktop bandwidth using only average traffic per connected user. It does not fix the reported Atlas Digital Systems problem: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. The relevant proof here is: Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.

C:

Inspect RDP connection information and session host network logs, then verify the UDP reachability and Shortpath configuration for the actual path. This could resolve a DIFFERENT AVD issue: A session host reports Available yet RDP Shortpath remains inactive; engineers troubleshoot only Azure VM power state rather than the connection transport. It does not fix the reported Atlas Digital Systems problem: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. The relevant proof here is: Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.

D:

Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls. This could resolve a DIFFERENT AVD issue: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. It does not fix the reported Atlas Digital Systems problem: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. The relevant proof here is: Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.

Question 34

The Atlas Digital Systems operations group needs acceptance evidence before signing off: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. Which outcome validates this fix rather than an unrelated system improvement?

  1. Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.
  2. A test session uses the expected UDP transport and logs show no remaining policy or NAT negotiation failures.
  3. A representative logon surge and video meeting run coexist without the VPN link reaching sustained utilization or unacceptable jitter.
  4. Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

Explanation

Correct Answer

A:

Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads. This is an independently observable result of the targeted change: Define and deploy an appropriate end-to-end QoS marking and prioritization policy for AVD real-time traffic consistent with the network design. It closes the specific Atlas Digital Systems failure: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment.

Incorrect Answers

B:

A test session uses the expected UDP transport and logs show no remaining policy or NAT negotiation failures. This is evidence for a DIFFERENT remediation: Inspect RDP connection information and session host network logs, then verify the UDP reachability and Shortpath configuration for the actual path. That remediation addresses: A session host reports Available yet RDP Shortpath remains inactive; engineers troubleshoot only Azure VM power state rather than the connection transport. It does not establish resolution of the Atlas Digital Systems problem: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. The required outcome here is: Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.

C:

A representative logon surge and video meeting run coexist without the VPN link reaching sustained utilization or unacceptable jitter. This is evidence for a DIFFERENT remediation: Plan capacity against observed high-percentile bandwidth and bursty sign-ins, incorporating headroom for concurrent Microsoft Teams meetings. That remediation addresses: An acquired branch connects through an undersized VPN and the team projects total desktop bandwidth using only average traffic per connected user. It does not establish resolution of the Atlas Digital Systems problem: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. The required outcome here is: Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.

D:

Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect. This is evidence for a DIFFERENT remediation: Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls. That remediation addresses: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. It does not establish resolution of the Atlas Digital Systems problem: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. The required outcome here is: Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.

Question 35

The virtual desktop support team at Cedarview Engineering investigates the following failure during a change review: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. How should the Azure Virtual Desktop administrator correct this specific failure?

  1. Measure endpoint-to-service latency, packet loss, and concurrent session throughput, then resize or prioritize the constrained network path.
  2. Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls.
  3. Define and deploy an appropriate end-to-end QoS marking and prioritization policy for AVD real-time traffic consistent with the network design.
  4. Inspect RDP connection information and session host network logs, then verify the UDP reachability and Shortpath configuration for the actual path.

Explanation

Correct Answer

C:

Define and deploy an appropriate end-to-end QoS marking and prioritization policy for AVD real-time traffic consistent with the network design. This directly addresses the Cedarview Engineering failure: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. The necessary acceptance evidence is: Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.

Incorrect Answers

A:

Measure endpoint-to-service latency, packet loss, and concurrent session throughput, then resize or prioritize the constrained network path. This could resolve a DIFFERENT AVD issue: A remote call center's AVD sessions become unresponsive each afternoon even though session host CPU is healthy and the WAN link is saturated. It does not fix the reported Cedarview Engineering problem: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. The relevant proof here is: Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.

B:

Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls. This could resolve a DIFFERENT AVD issue: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. It does not fix the reported Cedarview Engineering problem: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. The relevant proof here is: Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.

D:

Inspect RDP connection information and session host network logs, then verify the UDP reachability and Shortpath configuration for the actual path. This could resolve a DIFFERENT AVD issue: A session host reports Available yet RDP Shortpath remains inactive; engineers troubleshoot only Azure VM power state rather than the connection transport. It does not fix the reported Cedarview Engineering problem: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. The relevant proof here is: Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.

Question 36

An AVD incident at Cedarview Engineering can be closed only after proving that this issue is fixed: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. Which controlled test result independently verifies successful remediation?

  1. A simulated afternoon peak shows reduced packet loss and stable interactive response without changing healthy session host capacity.
  2. A test session uses the expected UDP transport and logs show no remaining policy or NAT negotiation failures.
  3. Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.
  4. Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

Explanation

Correct Answer

C:

Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads. This is an independently observable result of the targeted change: Define and deploy an appropriate end-to-end QoS marking and prioritization policy for AVD real-time traffic consistent with the network design. It closes the specific Cedarview Engineering failure: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment.

Incorrect Answers

A:

A simulated afternoon peak shows reduced packet loss and stable interactive response without changing healthy session host capacity. This is evidence for a DIFFERENT remediation: Measure endpoint-to-service latency, packet loss, and concurrent session throughput, then resize or prioritize the constrained network path. That remediation addresses: A remote call center's AVD sessions become unresponsive each afternoon even though session host CPU is healthy and the WAN link is saturated. It does not establish resolution of the Cedarview Engineering problem: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. The required outcome here is: Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.

B:

A test session uses the expected UDP transport and logs show no remaining policy or NAT negotiation failures. This is evidence for a DIFFERENT remediation: Inspect RDP connection information and session host network logs, then verify the UDP reachability and Shortpath configuration for the actual path. That remediation addresses: A session host reports Available yet RDP Shortpath remains inactive; engineers troubleshoot only Azure VM power state rather than the connection transport. It does not establish resolution of the Cedarview Engineering problem: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. The required outcome here is: Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.

D:

Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect. This is evidence for a DIFFERENT remediation: Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls. That remediation addresses: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. It does not establish resolution of the Cedarview Engineering problem: A shared uplink carries Teams video and AVD interactive traffic with severe jitter, but the QoS policy gives every packet the same treatment. The required outcome here is: Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.

Question 37

An AVD deployment review at Pinecrest Services must resolve this condition while preserving traceable desktop incidents: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link. Which proposed implementation change best meets the documented requirement?

  1. Configure appropriate on-premises conditional forwarding or DNS resolver rules to resolve the AVD private link zones correctly.
  2. Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls.
  3. Compare each affected host's service FQDN resolution and outbound HTTPS access to required AVD endpoints and correct the inconsistent DNS policy.
  4. Implement supported Azure Virtual Desktop Private Link private endpoints and required private DNS resolution for the appropriate service connections.

Explanation

Correct Answer

D:

Implement supported Azure Virtual Desktop Private Link private endpoints and required private DNS resolution for the appropriate service connections. This directly addresses the Pinecrest Services failure: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link. The necessary acceptance evidence is: From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.

Incorrect Answers

A:

Configure appropriate on-premises conditional forwarding or DNS resolver rules to resolve the AVD private link zones correctly. This could resolve a DIFFERENT AVD issue: A hybrid desktop client receives a public AVD service address despite a private endpoint deployment because its on-premises DNS never sees the linked private zone. It does not fix the reported Pinecrest Services problem: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link. The relevant proof here is: From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.

B:

Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls. This could resolve a DIFFERENT AVD issue: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. It does not fix the reported Pinecrest Services problem: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link. The relevant proof here is: From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.

C:

Compare each affected host's service FQDN resolution and outbound HTTPS access to required AVD endpoints and correct the inconsistent DNS policy. This could resolve a DIFFERENT AVD issue: Some session hosts disappear from connection pools after a DNS server change, while other hosts in the same host pool remain registered. It does not fix the reported Pinecrest Services problem: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link. The relevant proof here is: From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.

Question 38

After corrective work at Pinecrest Services, the acceptance reviewer tests this original failure: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link. Which observed outcome is the strongest evidence that the correction worked?

  1. From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.
  2. Previously unavailable hosts regain healthy registration and a monitored pilot connects through each repaired host.
  3. Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.
  4. The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

Explanation

Correct Answer

A:

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 Pinecrest Services failure: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link.

Incorrect Answers

B:

Previously unavailable hosts regain healthy registration and a monitored pilot connects through each repaired host. This is evidence for a DIFFERENT remediation: Compare each affected host's service FQDN resolution and outbound HTTPS access to required AVD endpoints and correct the inconsistent DNS policy. That remediation addresses: Some session hosts disappear from connection pools after a DNS server change, while other hosts in the same host pool remain registered. It does not establish resolution of the Pinecrest Services 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.

C:

Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect. This is evidence for a DIFFERENT remediation: Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls. That remediation addresses: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. It does not establish resolution of the Pinecrest Services 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.

D:

The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy. This is evidence for a DIFFERENT remediation: Configure appropriate on-premises conditional forwarding or DNS resolver rules to resolve the AVD private link zones correctly. That remediation addresses: A hybrid desktop client receives a public AVD service address despite a private endpoint deployment because its on-premises DNS never sees the linked private zone. It does not establish resolution of the Pinecrest Services 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.

Question 39

During an Azure Virtual Desktop rollout for Horizon Field Operations, engineers document this operational problem: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link. Which remediation addresses the root cause without making an unrelated configuration change?

  1. Implement supported Azure Virtual Desktop Private Link private endpoints and required private DNS resolution for the appropriate service connections.
  2. Review the required Azure Virtual Desktop Private Link subresources, endpoint approvals, network routes, and private DNS zones rather than opening general internet access.
  3. Use AVD diagnostics, effective routes, NSG flow observations, and path tests to isolate the failing transport or DNS dependency.
  4. Define and deploy an appropriate end-to-end QoS marking and prioritization policy for AVD real-time traffic consistent with the network design.

Explanation

Correct Answer

A:

Implement supported Azure Virtual Desktop Private Link private endpoints and required private DNS resolution for the appropriate service connections. This directly addresses the Horizon Field Operations failure: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link. The necessary acceptance evidence is: From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.

Incorrect Answers

B:

Review the required Azure Virtual Desktop Private Link subresources, endpoint approvals, network routes, and private DNS zones rather than opening general internet access. This could resolve a DIFFERENT AVD issue: 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 fix the reported 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 relevant proof here is: From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.

C:

Use AVD diagnostics, effective routes, NSG flow observations, and path tests to isolate the failing transport or DNS dependency. This could resolve a DIFFERENT AVD issue: 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 fix the reported 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 relevant proof here is: From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.

D:

Define and deploy an appropriate end-to-end QoS marking and prioritization policy for AVD real-time traffic consistent with the network design. This could resolve a DIFFERENT AVD issue: 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 fix the reported 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 relevant proof here is: From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.

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?

  1. Under a controlled congestion test the prioritized traffic retains acceptable jitter and packet loss without starving other required workloads.
  2. The failing VPN client path is identified and a corrected route or rule permits a full authenticated session without broad firewall exemptions.
  3. From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.
  4. Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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.