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 5

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.

Question 41

At Horizon Field Operations, a field workforce organization prioritizing resilient offsite access, administrators observe this 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. Which targeted engineering action most directly resolves the reported problem?

  1. Inspect RDP connection information and session host network logs, then verify the UDP reachability and Shortpath configuration for the actual path.
  2. Renumber the conflicting address space or redesign routed connectivity so session host and domain controller networks have nonoverlapping prefixes.
  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. Configure appropriate on-premises conditional forwarding or DNS resolver rules to resolve the AVD private link zones correctly.

Explanation

Correct Answer

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 directly addresses the Horizon Field Operations failure: 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. The necessary acceptance evidence is: Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

Incorrect Answers

A:

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 Horizon Field Operations problem: 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. The relevant proof here is: Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

B:

Renumber the conflicting address space or redesign routed connectivity so session host and domain controller networks have nonoverlapping prefixes. This could resolve a DIFFERENT AVD 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. It does not fix the reported Horizon Field Operations problem: 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. The relevant proof here is: Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

D:

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 Horizon Field Operations problem: 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. The relevant proof here is: Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

Question 42

The field workforce desktop team at Horizon Field Operations requires independent proof of remediation for: 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. What measurable result should the reviewer require before closing the incident?

  1. The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.
  2. Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.
  3. A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.
  4. A test session uses the expected UDP transport and logs show no remaining policy or NAT negotiation failures.

Explanation

Correct Answer

B:

Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency. This is an independently observable result of the targeted change: Review the required Azure Virtual Desktop Private Link subresources, endpoint approvals, network routes, and private DNS zones rather than opening general internet access. It closes the specific Horizon Field Operations failure: 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.

Incorrect Answers

A:

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 Horizon Field Operations problem: 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. The required outcome here is: Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

C:

A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably. This is evidence for a DIFFERENT remediation: Renumber the conflicting address space or redesign routed connectivity so session host and domain controller networks have nonoverlapping prefixes. That remediation addresses: 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. It does not establish resolution of the Horizon Field Operations problem: 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. The required outcome here is: Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

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 Horizon Field Operations problem: 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. The required outcome here is: Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

Question 43

For the document management workload at Harborline Legal IT, the host pool team reports: 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. What is the most appropriate first corrective action for this AVD scenario?

  1. Inspect RDP connection information and session host network logs, then verify the UDP reachability and Shortpath configuration for the actual path.
  2. Configure appropriate on-premises conditional forwarding or DNS resolver rules to resolve the AVD private link zones correctly.
  3. Implement supported Azure Virtual Desktop Private Link private endpoints and required private DNS resolution for the appropriate service connections.
  4. Review the required Azure Virtual Desktop Private Link subresources, endpoint approvals, network routes, and private DNS zones rather than opening general internet access.

Explanation

Correct Answer

D:

Review the required Azure Virtual Desktop Private Link subresources, endpoint approvals, network routes, and private DNS zones rather than opening general internet access. This directly addresses the Harborline Legal IT failure: 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. The necessary acceptance evidence is: Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

Incorrect Answers

A:

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 Harborline Legal IT problem: 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. The relevant proof here is: Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

B:

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 Harborline Legal IT problem: 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. The relevant proof here is: Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

C:

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 Harborline Legal IT problem: 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. The relevant proof here is: Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

Question 44

The Harborline Legal IT operations group needs acceptance evidence before signing off: 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. 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. Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.
  3. A test session uses the expected UDP transport and logs show no remaining policy or NAT negotiation failures.
  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

B:

Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency. This is an independently observable result of the targeted change: Review the required Azure Virtual Desktop Private Link subresources, endpoint approvals, network routes, and private DNS zones rather than opening general internet access. It closes the specific Harborline Legal IT failure: 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.

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 Harborline Legal IT problem: 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. The required outcome here is: Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

C:

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 Harborline Legal IT problem: 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. The required outcome here is: Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

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 Harborline Legal IT problem: 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. The required outcome here is: Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.

Question 45

The virtual desktop support team at Mariner Finance investigates the following failure during a change review: 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. How should the Azure Virtual Desktop administrator correct this specific failure?

  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. Configure appropriate on-premises conditional forwarding or DNS resolver rules to resolve the AVD private link zones correctly.
  4. Implement supported Azure Virtual Desktop Private Link private endpoints and required private DNS resolution for the appropriate service connections.

Explanation

Correct Answer

C:

Configure appropriate on-premises conditional forwarding or DNS resolver rules to resolve the AVD private link zones correctly. This directly addresses the Mariner Finance failure: 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. The necessary acceptance evidence is: The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

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 Mariner Finance problem: 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. The relevant proof here is: The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

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 Mariner Finance problem: 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. The relevant proof here is: The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

D:

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 Mariner Finance problem: 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. The relevant proof here is: The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

Question 46

An AVD incident at Mariner Finance can be closed only after proving that this issue is fixed: 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. Which controlled test result independently verifies successful remediation?

  1. Registration and connection diagnostics succeed through the approved private endpoints with no unexpected public transport dependency.
  2. From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.
  3. The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.
  4. A session host resolves the correct private storage endpoint and mounts the profile share without using a public DNS answer.

Explanation

Correct Answer

C:

The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy. This is an independently observable result of the targeted change: Configure appropriate on-premises conditional forwarding or DNS resolver rules to resolve the AVD private link zones correctly. It closes the specific Mariner Finance failure: 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.

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 Mariner Finance problem: 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. The required outcome here is: The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

B:

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 Mariner Finance problem: 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. The required outcome here is: The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

D:

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 Mariner Finance problem: 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. The required outcome here is: The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

Question 47

An AVD deployment review at Oakridge Administration must resolve this condition while preserving documented change control: 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. Which proposed implementation change best meets the documented requirement?

  1. Implement supported Azure Virtual Desktop Private Link private endpoints and required private DNS resolution for the appropriate service connections.
  2. Configure appropriate on-premises conditional forwarding or DNS resolver rules to resolve the AVD private link zones correctly.
  3. Renumber the conflicting address space or redesign routed connectivity so session host and domain controller networks have nonoverlapping prefixes.
  4. Estimate concurrent session bandwidth by workload, multimedia usage, latency tolerance, and peak concurrency before choosing network capacity.

Explanation

Correct Answer

B:

Configure appropriate on-premises conditional forwarding or DNS resolver rules to resolve the AVD private link zones correctly. This directly addresses the Oakridge Administration failure: 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. The necessary acceptance evidence is: The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

Incorrect Answers

A:

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 Oakridge Administration problem: 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. The relevant proof here is: The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

C:

Renumber the conflicting address space or redesign routed connectivity so session host and domain controller networks have nonoverlapping prefixes. This could resolve a DIFFERENT AVD 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. It does not fix the reported Oakridge Administration problem: 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. The relevant proof here is: The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

D:

Estimate concurrent session bandwidth by workload, multimedia usage, latency tolerance, and peak concurrency before choosing network capacity. This could resolve a DIFFERENT AVD issue: A new Azure Virtual Desktop office supports 480 concurrent users, but network sizing was estimated from the number of physical desks and omits session bandwidth. It does not fix the reported Oakridge Administration problem: 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. The relevant proof here is: The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

Question 48

After corrective work at Oakridge Administration, the acceptance reviewer tests this original failure: 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. Which observed outcome is the strongest evidence that the correction worked?

  1. A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably.
  2. From an approved private client, workspace feed and desktop connections succeed over the intended private paths and DNS resolves private endpoint addresses.
  3. The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.
  4. A busy-hour pilot with representative display and media workloads stays within the measured link headroom and user latency objectives.

Explanation

Correct Answer

C:

The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy. This is an independently observable result of the targeted change: Configure appropriate on-premises conditional forwarding or DNS resolver rules to resolve the AVD private link zones correctly. It closes the specific Oakridge Administration failure: 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.

Incorrect Answers

A:

A session host reaches the intended AD DS domain controllers through the documented next hop and completes domain join reliably. This is evidence for a DIFFERENT remediation: Renumber the conflicting address space or redesign routed connectivity so session host and domain controller networks have nonoverlapping prefixes. That remediation addresses: 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. It does not establish resolution of the Oakridge Administration problem: 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. The required outcome here is: The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

B:

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 Oakridge Administration problem: 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. The required outcome here is: The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

D:

A busy-hour pilot with representative display and media workloads stays within the measured link headroom and user latency objectives. This is evidence for a DIFFERENT remediation: Estimate concurrent session bandwidth by workload, multimedia usage, latency tolerance, and peak concurrency before choosing network capacity. That remediation addresses: A new Azure Virtual Desktop office supports 480 concurrent users, but network sizing was estimated from the number of physical desks and omits session bandwidth. It does not establish resolution of the Oakridge Administration problem: 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. The required outcome here is: The same workspace FQDN resolves to the approved private endpoint from the hybrid network and connections succeed under the intended access policy.

Question 49

During an Azure Virtual Desktop rollout for Redwood Media Group, engineers document this operational problem: 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. Which remediation addresses the root cause without making an unrelated configuration change?

  1. Compare each affected host's service FQDN resolution and outbound HTTPS access to required AVD endpoints and correct the inconsistent DNS policy.
  2. Plan capacity against observed high-percentile bandwidth and bursty sign-ins, incorporating headroom for concurrent Microsoft Teams meetings.
  3. Use AVD diagnostics, effective routes, NSG flow observations, and path tests to isolate the failing transport or DNS dependency.
  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

C:

Use AVD diagnostics, effective routes, NSG flow observations, and path tests to isolate the failing transport or DNS dependency. This directly addresses the Redwood Media Group failure: 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. The necessary acceptance evidence is: The failing VPN client path is identified and a corrected route or rule permits a full authenticated session without broad firewall exemptions.

Incorrect Answers

A:

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 Redwood Media Group problem: 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. The relevant proof here is: The failing VPN client path is identified and a corrected route or rule permits a full authenticated session without broad firewall exemptions.

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 Redwood Media Group problem: 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. The relevant proof here is: The failing VPN client path is identified and a corrected route or rule permits a full authenticated session without broad firewall exemptions.

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 Redwood Media Group problem: 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. The relevant proof here is: The failing VPN client path is identified and a corrected route or rule permits a full authenticated session without broad firewall exemptions.

Question 50

In the Redwood Media Group pilot environment, a controlled verification is required for: 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. What evidence best demonstrates that the reported AVD issue is resolved?

  1. The failing VPN client path is identified and a corrected route or rule permits a full authenticated session without broad firewall exemptions.
  2. Previously unavailable hosts regain healthy registration and a monitored pilot connects through each repaired host.
  3. Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect.
  4. A representative logon surge and video meeting run coexist without the VPN link reaching sustained utilization or unacceptable jitter.

Explanation

Correct Answer

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 an independently observable result of the targeted change: Use AVD diagnostics, effective routes, NSG flow observations, and path tests to isolate the failing transport or DNS dependency. It closes the specific Redwood Media Group failure: 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.

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 Redwood Media Group problem: 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. The required outcome here is: The failing VPN client path is identified and a corrected route or rule permits a full authenticated session without broad firewall exemptions.

C:

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 Redwood Media Group problem: 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. The required outcome here is: The failing VPN client path is identified and a corrected route or rule permits a full authenticated session without broad firewall exemptions.

D:

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 Redwood Media Group problem: 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. The required outcome here is: The failing VPN client path is identified and a corrected route or rule permits a full authenticated session without broad firewall exemptions.