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 3

Question 20

In the Beacon IT Solutions pilot environment, a controlled verification is required for: A deployment team gives session hosts public IPs for outbound AVD service traffic even though security policy forbids inbound internet exposure. What evidence best demonstrates that the reported AVD issue is resolved?

  1. New session hosts register and users connect while no session host VM has a directly reachable public IP address.
  2. A representative logon surge and video meeting run coexist without the VPN link reaching sustained utilization or unacceptable jitter.
  3. A session host resolves the correct private storage endpoint and mounts the profile share without using a public DNS answer.
  4. Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

Explanation

Correct Answer

A:

New session hosts register and users connect while no session host VM has a directly reachable public IP address. This is an independently observable result of the targeted change: Design session-host egress through controlled NAT or firewall routing and permit required Azure Virtual Desktop service endpoints without public host IPs. It closes the specific Beacon IT Solutions failure: A deployment team gives session hosts public IPs for outbound AVD service traffic even though security policy forbids inbound internet exposure.

Incorrect Answers

B:

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 Beacon IT Solutions problem: A deployment team gives session hosts public IPs for outbound AVD service traffic even though security policy forbids inbound internet exposure. The required outcome here is: New session hosts register and users connect while no session host VM has a directly reachable public IP address.

C:

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 Beacon IT Solutions problem: A deployment team gives session hosts public IPs for outbound AVD service traffic even though security policy forbids inbound internet exposure. The required outcome here is: New session hosts register and users connect while no session host VM has a directly reachable public IP address.

D:

Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect. This is evidence for a DIFFERENT remediation: Use supported Windows App versions and RDP Shortpath connectivity so built-in RDP Multipath can maintain and switch viable transport paths. That remediation addresses: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. It does not establish resolution of the Beacon IT Solutions problem: A deployment team gives session hosts public IPs for outbound AVD service traffic even though security policy forbids inbound internet exposure. The required outcome here is: New session hosts register and users connect while no session host VM has a directly reachable public IP address.

Question 21

At Cobalt Customer Care, a support desk applications organization prioritizing predictable session performance, administrators observe this issue: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. Which targeted engineering action most directly resolves the reported problem?

  1. Configure and test DNS resolution for the session host subnet with conditional forwarding or private DNS integration matching the storage endpoints.
  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. Compare each affected host's service FQDN resolution and outbound HTTPS access to required AVD endpoints and correct the inconsistent DNS policy.
  4. Renumber the conflicting address space or redesign routed connectivity so session host and domain controller networks have nonoverlapping prefixes.

Explanation

Correct Answer

D:

Renumber the conflicting address space or redesign routed connectivity so session host and domain controller networks have nonoverlapping prefixes. This directly addresses the Cobalt Customer Care failure: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. The necessary acceptance evidence is: A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

Incorrect Answers

A:

Configure and test DNS resolution for the session host subnet with conditional forwarding or private DNS integration matching the storage endpoints. This could resolve a DIFFERENT AVD issue: 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 fix the reported Cobalt Customer Care problem: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. The relevant proof here is: A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

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 Cobalt Customer Care problem: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. The relevant proof here is: A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

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 Cobalt Customer Care problem: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. The relevant proof here is: A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

Question 22

The support desk applications desktop team at Cobalt Customer Care requires independent proof of remediation for: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. What measurable result should the reviewer require before closing the incident?

  1. Previously unavailable hosts regain healthy registration and a monitored pilot connects through each repaired host.
  2. A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.
  3. A session host resolves the correct private storage endpoint and mounts the profile share without using a public DNS answer.
  4. Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

Explanation

Correct Answer

B:

A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably. This is an independently observable result of the targeted change: Renumber the conflicting address space or redesign routed connectivity so session host and domain controller networks have nonoverlapping prefixes. It closes the specific Cobalt Customer Care failure: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination.

Incorrect Answers

A:

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 Cobalt Customer Care problem: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. The required outcome here is: A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

C:

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 Cobalt Customer Care problem: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. The required outcome here is: A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

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 Cobalt Customer Care problem: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. The required outcome here is: A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

Question 23

For the business services workload at Valleyline Partners, the host pool team reports: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. What is the most appropriate first corrective action for this AVD scenario?

  1. Configure and test DNS resolution for the session host subnet with conditional forwarding or private DNS integration matching the storage endpoints.
  2. Implement supported Azure Virtual Desktop Private Link private endpoints and required private DNS resolution for the appropriate service connections.
  3. Renumber the conflicting address space or redesign routed connectivity so session host and domain controller networks have nonoverlapping prefixes.
  4. Measure endpoint-to-service latency, packet loss, and concurrent session throughput, then resize or prioritize the constrained network path.

Explanation

Correct Answer

C:

Renumber the conflicting address space or redesign routed connectivity so session host and domain controller networks have nonoverlapping prefixes. This directly addresses the Valleyline Partners failure: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. The necessary acceptance evidence is: A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

Incorrect Answers

A:

Configure and test DNS resolution for the session host subnet with conditional forwarding or private DNS integration matching the storage endpoints. This could resolve a DIFFERENT AVD issue: 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 fix the reported Valleyline Partners problem: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. The relevant proof here is: A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

B:

Implement supported Azure Virtual Desktop Private Link private endpoints and required private DNS resolution for the appropriate service connections. This could resolve a DIFFERENT AVD issue: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link. It does not fix the reported Valleyline Partners problem: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. The relevant proof here is: A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

D:

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 Valleyline Partners problem: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. The relevant proof here is: A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

Question 24

The Valleyline Partners operations group needs acceptance evidence before signing off: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. Which outcome validates this fix rather than an unrelated system improvement?

  1. From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.
  2. A session host resolves the correct private storage endpoint and mounts the profile share without using a public DNS answer.
  3. A simulated afternoon peak shows reduced packet loss and stable interactive response without changing healthy session host capacity.
  4. A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

Explanation

Correct Answer

D:

A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably. This is an independently observable result of the targeted change: Renumber the conflicting address space or redesign routed connectivity so session host and domain controller networks have nonoverlapping prefixes. It closes the specific Valleyline Partners failure: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination.

Incorrect Answers

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 evidence for a DIFFERENT remediation: Implement supported Azure Virtual Desktop Private Link private endpoints and required private DNS resolution for the appropriate service connections. That remediation addresses: A regulated AVD environment uses public service endpoints for feed discovery even though the compliance design requires Azure Private Link. It does not establish resolution of the Valleyline Partners problem: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. The required outcome here is: A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

B:

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 Valleyline Partners problem: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. The required outcome here is: A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

C:

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 Valleyline Partners problem: AVD session hosts join a domain across site-to-site VPN, but their subnets overlap the on-premises AD network and routing chooses the wrong destination. The required outcome here is: A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.

Question 25

The virtual desktop support team at Granite Network Team investigates the following failure during a change review: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. How should the Azure Virtual Desktop administrator correct this specific failure?

  1. Design session-host egress through controlled NAT or firewall routing and permit required Azure Virtual Desktop service endpoints without public host IPs.
  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. Use AVD diagnostics, effective routes, NSG flow observations, and path tests to isolate the failing transport or DNS dependency.

Explanation

Correct Answer

B:

Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls. This directly addresses the Granite Network Team failure: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. The necessary acceptance evidence is: Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

Incorrect Answers

A:

Design session-host egress through controlled NAT or firewall routing and permit required Azure Virtual Desktop service endpoints without public host IPs. This could resolve a DIFFERENT AVD issue: A deployment team gives session hosts public IPs for outbound AVD service traffic even though security policy forbids inbound internet exposure. It does not fix the reported Granite Network Team problem: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. The relevant proof here is: Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

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 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 Granite Network Team problem: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. The relevant proof here is: Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

D:

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 Granite Network Team problem: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. The relevant proof here is: Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

Question 26

An AVD incident at Granite Network Team can be closed only after proving that this issue is fixed: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. Which controlled test result independently verifies successful remediation?

  1. The failing VPN client path is identified and a corrected route or rule permits a full authenticated session without broad firewall exemptions.
  2. New session hosts register and users connect while no session host VM has a directly reachable public IP address.
  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

D:

Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect. This is an independently observable result of the targeted change: Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls. It closes the specific Granite Network Team failure: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts.

Incorrect Answers

A:

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 Granite Network Team problem: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. The required outcome here is: Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

B:

New session hosts register and users connect while no session host VM has a directly reachable public IP address. This is evidence for a DIFFERENT remediation: Design session-host egress through controlled NAT or firewall routing and permit required Azure Virtual Desktop service endpoints without public host IPs. That remediation addresses: A deployment team gives session hosts public IPs for outbound AVD service traffic even though security policy forbids inbound internet exposure. It does not establish resolution of the Granite Network Team problem: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. The required outcome here is: Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

C:

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 Granite Network Team problem: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. The required outcome here is: Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

Question 27

An AVD deployment review at Cobalt Customer Care must resolve this condition while preserving predictable session performance: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. Which proposed implementation change best meets the documented requirement?

  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. Compare each affected host's service FQDN resolution and outbound HTTPS access to required AVD endpoints and correct the inconsistent DNS policy.
  4. Use supported Windows App versions and RDP Shortpath connectivity so built-in RDP Multipath can maintain and switch viable transport paths.

Explanation

Correct Answer

B:

Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls. This directly addresses the Cobalt Customer Care failure: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. The necessary acceptance evidence is: Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

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 Cobalt Customer Care problem: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. The relevant proof here is: Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

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 Cobalt Customer Care problem: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. The relevant proof here is: Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

D:

Use supported Windows App versions and RDP Shortpath connectivity so built-in RDP Multipath can maintain and switch viable transport paths. This could resolve a DIFFERENT AVD issue: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. It does not fix the reported Cobalt Customer Care problem: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. The relevant proof here is: Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

Question 28

After corrective work at Cobalt Customer Care, the acceptance reviewer tests this original failure: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. Which observed outcome is the strongest evidence that the correction worked?

  1. A simulated afternoon peak shows reduced packet loss and stable interactive response without changing healthy session host capacity.
  2. Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.
  3. Previously unavailable hosts regain healthy registration and a monitored pilot connects through each repaired host.
  4. Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

Explanation

Correct Answer

B:

Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect. This is an independently observable result of the targeted change: Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls. It closes the specific Cobalt Customer Care failure: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts.

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 Cobalt Customer Care problem: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. The required outcome here is: Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

C:

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 Cobalt Customer Care problem: An AVD team expects direct low-latency UDP sessions over ExpressRoute, but managed-network RDP Shortpath listener traffic is blocked on session hosts. The required outcome here is: Connection diagnostics show the intended direct UDP path and the measured session latency improves relative to TCP reverse connect.

D:

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

Question 29

During an Azure Virtual Desktop rollout for Aspen Research Group, engineers document this operational problem: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. Which remediation addresses the root cause without making an unrelated configuration change?

  1. Use supported Windows App versions and RDP Shortpath connectivity so built-in RDP Multipath can maintain and switch viable transport paths.
  2. Enable the managed-network Shortpath listener on supported hosts and allow the required UDP listener path through Windows and network firewalls.
  3. Use AVD diagnostics, effective routes, NSG flow observations, and path tests to isolate the failing transport or DNS dependency.
  4. Configure and test DNS resolution for the session host subnet with conditional forwarding or private DNS integration matching the storage endpoints.

Explanation

Correct Answer

A:

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 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. 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

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 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 relevant proof here is: Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

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 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 relevant proof here is: Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

D:

Configure and test DNS resolution for the session host subnet with conditional forwarding or private DNS integration matching the storage endpoints. This could resolve a DIFFERENT AVD issue: 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 fix the reported 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 relevant proof here is: Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.

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.