Microsoft AZ-800 Practice Test 62 - Prepaway
Practice Exams:

Pass Microsoft AZ-800 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium Bundle
$29.98
$79.99 $109.97

AZ-800 Premium Bundle


  • Premium File 311 Questions & Answers. Last update: Nov 12, 2026
  • Training Course 150 Lectures
  • Study Guide 430 Pages

Microsoft AZ-800 Practice Test 62

Question 610

At Bayview Address Services, the team supports Windows DHCP failover and corporate IPAM and must maintain unique address allocations and resilient lease delivery. The original incident is: A static network appliance randomly disconnects after a DHCP server assigns the same address to a workstation. The evidence is: ARP conflict records and lease history show the appliance's static address lies inside an unrestricted dynamic allocation pool. A recovery is acceptable only with an appropriately scoped change and independently observable proof. Which paired action and verification most appropriately correct and confirm this Windows Server issue?

  1. Action: Set the intended AD-integrated zone replication scope and verify eligible DNS server partition memberships. Evidence of success: The target controller answers authoritative zone queries and disallowed DNS servers remain outside the replication scope.
  2. Action: Replace the stale resolver target with an authorized reachable DNS forwarder and validate forwarding scope. Evidence of success: Queries for partner names resolve through the intended DNS server while unrelated namespaces retain their normal resolver path.
  3. Action: Exclude the approved static address from the dynamic pool or assign a coordinated reservation as appropriate. Evidence of success: Address conflict monitoring remains clear and both appliance and workstation retain unique stable connectivity.
  4. Action: Resolve the conflicting lease and configure the correct client identifier reservation inside the approved addressing plan. Evidence of success: The intended printer receives its reserved address and no other client is given the same address.

Explanation

Correct Answer

C:

This proposed change-and-check pair is tied to the Bayview Address Services fault: Action: Exclude the approved static address from the dynamic pool or assign a coordinated reservation as appropriate. Evidence of success: Address conflict monitoring remains clear and both appliance and workstation retain unique stable connectivity. The diagnostic basis is that aRP conflict records and lease history show the appliance's static address lies inside an unrestricted dynamic allocation pool. The outcome must show that address conflict monitoring remains clear and both appliance and workstation retain unique stable connectivity.

Incorrect Answers

A:

The alternative combined step is Action: Set the intended AD-integrated zone replication scope and verify eligible DNS server partition memberships. Evidence of success: The target controller answers authoritative zone queries and disallowed DNS servers remain outside the replication scope. The relevant Bayview Address Services evidence is that aRP conflict records and lease history show the appliance's static address lies inside an unrestricted dynamic allocation pool. Closure must validate that address conflict monitoring remains clear and both appliance and workstation retain unique stable connectivity, rather than a different symptom.

B:

The paired remediation states Action: Replace the stale resolver target with an authorized reachable DNS forwarder and validate forwarding scope. Evidence of success: Queries for partner names resolve through the intended DNS server while unrelated namespaces retain their normal resolver path. It does not test correction of the Bayview Address Services condition: ARP conflict records and lease history show the appliance's static address lies inside an unrestricted dynamic allocation pool. The outcome to verify is that address conflict monitoring remains clear and both appliance and workstation retain unique stable connectivity.

D:

The paired proposal is Action: Resolve the conflicting lease and configure the correct client identifier reservation inside the approved addressing plan. Evidence of success: The intended printer receives its reserved address and no other client is given the same address. For Bayview Address Services, it fails to establish an intervention and check for the documented issue, where a static network appliance randomly disconnects after a DHCP server assigns the same address to a workstation. Successful closure requires that address conflict monitoring remains clear and both appliance and workstation retain unique stable connectivity.

Question 611

At Cedarbrook Hybrid DNS, the team supports on-premises Windows DNS integrated with Azure namespaces and must preserve name resolution security and correct zone authority. Confirmed original fault: An Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. Supporting diagnostic evidence: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. Set the intended AD-integrated zone replication scope and verify eligible DNS server partition memberships.
  2. Add approved consistent address-space and routing entries at both peers and validate any firewall restrictions.
  3. Add the authorized network prefix to IPAM discovery and management scope with verified ownership and classification.
  4. Exclude the approved static address from the dynamic pool or assign a coordinated reservation as appropriate.

Explanation

Correct Answer

B:

The available evidence is that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. Cedarbrook Hybrid DNS needs to add approved consistent address-space and routing entries at both peers and validate any firewall restrictions. VPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules. Confirmation would be that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied.

Incorrect Answers

A:

The issue at Cedarbrook Hybrid DNS is that an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. Acting to set the intended AD-integrated zone replication scope and verify eligible DNS server partition memberships would not correct the evidenced cause. The most relevant clue is that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix.

C:

The failure at Cedarbrook Hybrid DNS is that an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. That does not call for add the authorized network prefix to IPAM discovery and management scope with verified ownership and classification. The case evidence instead establishes that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix.

D:

At Cedarbrook Hybrid DNS, proposing to exclude the approved static address from the dynamic pool or assign a coordinated reservation as appropriate would not address the recorded evidence: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The case instead needs an intervention related to an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. VPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.

Question 612

At Cedarbrook Hybrid DNS, the team supports on-premises Windows DNS integrated with Azure namespaces and must preserve name resolution security and correct zone authority. A reported incident states: An Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. Before changing the environment, the team must distinguish among plausible technical causes. Which observation most decisively distinguishes this specific Windows Server failure from other problems?

  1. Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix.
  2. The Windows DNS conditional forwarder points to a decommissioned resolver and times out for the partner namespace.
  3. Failover configuration and replication inspection show the new scope has not been included or synchronized to its partner.
  4. The new routed prefix is absent from the discovered and managed IP address blocks and delegated management scope.

Explanation

Correct Answer

A:

For Cedarbrook Hybrid DNS, this is the discriminating finding: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. It accounts for the reported problem, where an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. VPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.

Incorrect Answers

B:

An unrelated diagnosis would involve: The Windows DNS conditional forwarder points to a decommissioned resolver and times out for the partner namespace. The incident at Cedarbrook Hybrid DNS is that an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. The decisive finding instead is that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix.

C:

This observation, failover configuration and replication inspection show the new scope has not been included or synchronized to its partner, does not match the evidence in the Cedarbrook Hybrid DNS record. Instead, the record shows that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. VPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.

D:

For Cedarbrook Hybrid DNS, the proposed observation is that the new routed prefix is absent from the discovered and managed IP address blocks and delegated management scope. It would not distinguish the identified failure, where an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. The meaningful clue is that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix.

Question 613

At Cedarbrook Hybrid DNS, the team supports on-premises Windows DNS integrated with Azure namespaces and must preserve name resolution security and correct zone authority. Observed issue: An Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. Investigation found: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The proposed repair is: Add approved consistent address-space and routing entries at both peers and validate any firewall restrictions. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. An on-premises test client resolves the private service address while public queries retain their authorized path.
  2. Clients obtain the intended lease when either partner is deliberately made unavailable under controlled testing.
  3. A designated external test identity accesses only the published application through the connector with expected access controls.
  4. A controlled internal application flow crosses the tunnel while unrelated private networks remain denied.

Explanation

Correct Answer

D:

The verification signal is that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied. It connects the proposed correction to the recorded diagnostic clue at Cedarbrook Hybrid DNS: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. VPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.

Incorrect Answers

A:

The alternative validation would show that an on-premises test client resolves the private service address while public queries retain their authorized path. For Cedarbrook Hybrid DNS, that is insufficient to establish that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied. The original diagnostic finding is that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix.

B:

At Cedarbrook Hybrid DNS, a test showing that clients obtain the intended lease when either partner is deliberately made unavailable under controlled testing would not confirm the needed outcome. The check must demonstrate that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied. It must address the failure, where an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet.

C:

That verification is that a designated external test identity accesses only the published application through the connector with expected access controls. The Cedarbrook Hybrid DNS acceptance criterion is instead that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied. The recorded causal clue is that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix.

Question 614

At Cedarbrook Hybrid DNS, the team supports on-premises Windows DNS integrated with Azure namespaces and must preserve name resolution security and correct zone authority. The administrator observes: An Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. The distinguishing clue is: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The team wants a causal explanation, not a generic remedy. Which Windows Server, identity, network, compute or storage principle best explains the identified failure?

  1. DNS change safety requires authoritative record governance and awareness of TTL-driven caching behavior.
  2. Windows hybrid network adapters rely on authenticated VPN endpoint identity and correctly scoped routing.
  3. VPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.
  4. Application Proxy requires an operational outbound connector path to internal resources, independent of public endpoint availability.

Explanation

Correct Answer

C:

At Cedarbrook Hybrid DNS, the key technical rule is that vPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules. The evidence is that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. This links the observed failure to its underlying cause.

Incorrect Answers

A:

The alternative rule states that dNS change safety requires authoritative record governance and awareness of TTL-driven caching behavior. It does not account for the Cedarbrook Hybrid DNS evidence: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The case turns on the mechanism that vPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.

B:

The alternative principle is that windows hybrid network adapters rely on authenticated VPN endpoint identity and correctly scoped routing. For Cedarbrook Hybrid DNS, it does not explain why tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The applicable causal rule is that vPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.

D:

At Cedarbrook Hybrid DNS, the reported clue is that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The principle of application Proxy requires an operational outbound connector path to internal resources, independent of public endpoint availability does not explain that finding. The appropriate explanation is that vPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.

Question 615

At Cedarbrook Hybrid DNS, the team supports on-premises Windows DNS integrated with Azure namespaces and must preserve name resolution security and correct zone authority. The original incident is: An Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. The evidence is: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. A recovery is acceptable only with an appropriately scoped change and independently observable proof. Which paired action and verification most appropriately correct and confirm this Windows Server issue?

  1. Action: Plan and expand or redistribute the DHCP scope based on approved IPAM allocations and actual lease demand. Evidence of success: A peak-volume client simulation receives unique addresses with correct gateway and DNS options.
  2. Action: Deploy the correct server certificate and approved trusted CA chain, preserving intended EAP policy constraints. Evidence of success: Representative domain clients authenticate with validated server identity while an untrusted server certificate is rejected.
  3. Action: Restore the approved gateway and endpoint configuration with current certificate and route authorization. Evidence of success: The server reaches the explicitly approved Azure private subnet while unapproved cloud networks remain inaccessible.
  4. Action: Add approved consistent address-space and routing entries at both peers and validate any firewall restrictions. Evidence of success: A controlled internal application flow crosses the tunnel while unrelated private networks remain denied.

Explanation

Correct Answer

D:

The documented issue at Cedarbrook Hybrid DNS is that an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. The selected combined action and test is Action: Add approved consistent address-space and routing entries at both peers and validate any firewall restrictions. Evidence of success: A controlled internal application flow crosses the tunnel while unrelated private networks remain denied. Its verification aligns with the required outcome: A controlled internal application flow crosses the tunnel while unrelated private networks remain denied.

Incorrect Answers

A:

The paired remediation states Action: Plan and expand or redistribute the DHCP scope based on approved IPAM allocations and actual lease demand. Evidence of success: A peak-volume client simulation receives unique addresses with correct gateway and DNS options. It does not test correction of the Cedarbrook Hybrid DNS condition: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The outcome to verify is that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied.

B:

That action and check pair is Action: Deploy the correct server certificate and approved trusted CA chain, preserving intended EAP policy constraints. Evidence of success: Representative domain clients authenticate with validated server identity while an untrusted server certificate is rejected. It does not connect both parts to the actual Cedarbrook Hybrid DNS clue: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The acceptance test needs to show that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied.

C:

The paired proposal is Action: Restore the approved gateway and endpoint configuration with current certificate and route authorization. Evidence of success: The server reaches the explicitly approved Azure private subnet while unapproved cloud networks remain inaccessible. For Cedarbrook Hybrid DNS, it fails to establish an intervention and check for the documented issue, where an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. Successful closure requires that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied.

Question 616

At Bayview Address Services, the team supports Windows DHCP failover and corporate IPAM and must maintain unique address allocations and resilient lease delivery. Confirmed original fault: An Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. Supporting diagnostic evidence: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. Resolve the conflicting lease and configure the correct client identifier reservation inside the approved addressing plan.
  2. Add the authorized network prefix to IPAM discovery and management scope with verified ownership and classification.
  3. Add approved consistent address-space and routing entries at both peers and validate any firewall restrictions.
  4. Restore the approved gateway and endpoint configuration with current certificate and route authorization.

Explanation

Correct Answer

C:

At Bayview Address Services, the relevant observation is that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The direct correction is to add approved consistent address-space and routing entries at both peers and validate any firewall restrictions. VPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules. Verify that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied.

Incorrect Answers

A:

That alternative would resolve the conflicting lease and configure the correct client identifier reservation inside the approved addressing plan. It misses the condition observed at Bayview Address Services: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The recommended correction addresses the observed condition directly.

B:

The failure at Bayview Address Services is that an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. That does not call for add the authorized network prefix to IPAM discovery and management scope with verified ownership and classification. The case evidence instead establishes that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix.

D:

That alternative would restore the approved gateway and endpoint configuration with current certificate and route authorization. For Bayview Address Services, that does not follow the diagnostic finding that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The relevant principle is that vPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.

Question 617

At Bayview Address Services, the team supports Windows DHCP failover and corporate IPAM and must maintain unique address allocations and resilient lease delivery. A reported incident states: An Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. Before changing the environment, the team must distinguish among plausible technical causes. Which observation most decisively distinguishes this specific Windows Server failure from other problems?

  1. Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix.
  2. The zone replication scope is configured for a partition that does not include the target DNS server.
  3. The hybrid DNS flow has no configured route through an Azure DNS Private Resolver inbound endpoint for the private zone.
  4. Validation logs identify an outdated trust anchor or uncoordinated DS/DNSKEY signature chain.

Explanation

Correct Answer

A:

The reported issue at Bayview Address Services is that an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. The offered observation of tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix identifies the relevant fault rather than an unrelated symptom. VPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.

Incorrect Answers

B:

This observation, the zone replication scope is configured for a partition that does not include the target DNS server, does not match the evidence in the Bayview Address Services record. Instead, the record shows that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. VPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.

C:

For Bayview Address Services, the proposed observation is that the hybrid DNS flow has no configured route through an Azure DNS Private Resolver inbound endpoint for the private zone. It would not distinguish the identified failure, where an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. The meaningful clue is that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix.

D:

The observation offered is that validation logs identify an outdated trust anchor or uncoordinated DS/DNSKEY signature chain. It does not substantiate the reported Bayview Address Services failure, where an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. The directly relevant diagnostic record is that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix.

Question 618

At Bayview Address Services, the team supports Windows DHCP failover and corporate IPAM and must maintain unique address allocations and resilient lease delivery. Observed issue: An Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. Investigation found: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The proposed repair is: Add approved consistent address-space and routing entries at both peers and validate any firewall restrictions. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. The target controller answers authoritative zone queries and disallowed DNS servers remain outside the replication scope.
  2. Representative domain clients authenticate with validated server identity while an untrusted server certificate is rejected.
  3. A controlled internal application flow crosses the tunnel while unrelated private networks remain denied.
  4. The server reaches the explicitly approved Azure private subnet while unapproved cloud networks remain inaccessible.

Explanation

Correct Answer

C:

The verification signal is that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied. It connects the proposed correction to the recorded diagnostic clue at Bayview Address Services: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. VPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.

Incorrect Answers

A:

At Bayview Address Services, a test showing that the target controller answers authoritative zone queries and disallowed DNS servers remain outside the replication scope would not confirm the needed outcome. The check must demonstrate that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied. It must address the failure, where an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet.

B:

That verification is that representative domain clients authenticate with validated server identity while an untrusted server certificate is rejected. The Bayview Address Services acceptance criterion is instead that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied. The recorded causal clue is that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix.

D:

The option would validate that the server reaches the explicitly approved Azure private subnet while unapproved cloud networks remain inaccessible. That does not establish correction of the Bayview Address Services issue, where an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. The meaningful proof is that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied.

Question 619

At Bayview Address Services, the team supports Windows DHCP failover and corporate IPAM and must maintain unique address allocations and resilient lease delivery. The administrator observes: An Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. The distinguishing clue is: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The team wants a causal explanation, not a generic remedy. Which Windows Server, identity, network, compute or storage principle best explains the identified failure?

  1. VPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.
  2. Conditional forwarding directs specific namespaces and depends on the health of designated upstream DNS endpoints.
  3. IP address management requires actively maintained inventory scope to detect allocation conflicts.
  4. Application Proxy requires an operational outbound connector path to internal resources, independent of public endpoint availability.

Explanation

Correct Answer

A:

The selected principle is that vPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules. It fits the Bayview Address Services case because tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The reported failure is that an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet.

Incorrect Answers

B:

This offered mechanism, conditional forwarding directs specific namespaces and depends on the health of designated upstream DNS endpoints, does not match the specific recorded failure at Bayview Address Services, where an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. The relevant principle is that vPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.

C:

At Bayview Address Services, the reported clue is that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The principle of iP address management requires actively maintained inventory scope to detect allocation conflicts does not explain that finding. The appropriate explanation is that vPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.

D:

The alternate technical explanation says that application Proxy requires an operational outbound connector path to internal resources, independent of public endpoint availability. It is not the mechanism identified by the Bayview Address Services record: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. VPN control-plane establishment does not automatically guarantee the correct data-plane routes and access rules.

Question 620

At Bayview Address Services, the team supports Windows DHCP failover and corporate IPAM and must maintain unique address allocations and resilient lease delivery. The original incident is: An Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. The evidence is: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. A recovery is acceptable only with an appropriately scoped change and independently observable proof. Which paired action and verification most appropriately correct and confirm this Windows Server issue?

  1. Action: Configure the supported DNS forwarding path to the approved private resolver endpoint and verify required connectivity. Evidence of success: An on-premises test client resolves the private service address while public queries retain their authorized path.
  2. Action: Deploy the correct server certificate and approved trusted CA chain, preserving intended EAP policy constraints. Evidence of success: Representative domain clients authenticate with validated server identity while an untrusted server certificate is rejected.
  3. Action: Correct the approved backend service SPN and constrained delegation binding after validating the service identity. Evidence of success: An external authorized user completes sign-in to the published app without granting unrelated backend access.
  4. Action: Add approved consistent address-space and routing entries at both peers and validate any firewall restrictions. Evidence of success: A controlled internal application flow crosses the tunnel while unrelated private networks remain denied.

Explanation

Correct Answer

D:

Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The paired remediation and acceptance test for Bayview Address Services is Action: Add approved consistent address-space and routing entries at both peers and validate any firewall restrictions. Evidence of success: A controlled internal application flow crosses the tunnel while unrelated private networks remain denied. The check is meaningful because success requires that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied.

Incorrect Answers

A:

That action and check pair is Action: Configure the supported DNS forwarding path to the approved private resolver endpoint and verify required connectivity. Evidence of success: An on-premises test client resolves the private service address while public queries retain their authorized path. It does not connect both parts to the actual Bayview Address Services clue: Tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix. The acceptance test needs to show that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied.

B:

The paired proposal is Action: Deploy the correct server certificate and approved trusted CA chain, preserving intended EAP policy constraints. Evidence of success: Representative domain clients authenticate with validated server identity while an untrusted server certificate is rejected. For Bayview Address Services, it fails to establish an intervention and check for the documented issue, where an Azure-linked Windows remote-access gateway reports a connected VPN tunnel but no internal workloads can reach the remote subnet. Successful closure requires that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied.

C:

At Bayview Address Services, the option couples action: Correct the approved backend service SPN and constrained delegation binding after validating the service identity. Evidence of success: An external authorized user completes sign-in to the published app without granting unrelated backend access. Its test does not independently demonstrate that a controlled internal application flow crosses the tunnel while unrelated private networks remain denied. The deciding case evidence is that tunnel negotiation succeeds while effective route tables and remote address spaces omit the destination network prefix.

Administering Windows Server Hybrid Core Infrastructure (AZ-800) Practice Tests