McAfee-Secured Website

Exam Bundle

Exam Code: AZ-800

Exam Name Administering Windows Server Hybrid Core Infrastructure

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Windows Server Hybrid Administrator Associate

Microsoft AZ-800 Bundle $44.99

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

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

  • Questions & Answers

    AZ-800 Questions & Answers

    311 Questions & Answers

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

  • AZ-800 Video Course

    AZ-800 Video Course

    150 Video Lectures

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

    Description

    This course will improve your knowledge and skills required to pass Administering Windows Server Hybrid Core Infrastructure exam.
  • Study Guide

    AZ-800 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-800 exam.

Administering Windows Server Hybrid Core Infrastructure (AZ-800) 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

    311 Questions

    $124.99
  • AZ-800 Video Course

    Video Course

    150 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    430 PDF Pages

    $29.99

Microsoft AZ-800 Practice Test 67

Question 660

A Windows Server administrator proposes this action: Create and link the appropriate Azure Private DNS zone to the required virtual network. Which situation most specifically calls for this action?

  1. A public service domain moves its DNS hosting to Azure without changing its registrar.
  2. A domain-joined workstation fails to locate a controller even though its gateway and ping work.
  3. A service should return a nearby approved IP endpoint based on the client subnet.
  4. Azure VMs in a linked virtual network need to resolve private names for a hybrid application.

Explanation

Correct Answer

D:

This scenario is the specific context for Azure Private DNS resolution. The appropriate action is to Create and link the appropriate Azure Private DNS zone to the required virtual network. Expected outcome: Azure DNS can resolve the private namespace in linked networks.

Incorrect Answers

A:

This situation concerns Azure public DNS delegation. It would call for: Create an Azure Public DNS zone and update parent NS delegation with its Azure name servers. Expected result: Public recursive resolvers reach the new authoritative Azure DNS hosts. It does not directly motivate the specified Azure Private DNS resolution action.

B:

This situation concerns DNS SRV controller discovery. It would call for: Verify the configured DNS server and AD DS SRV records rather than using arbitrary public resolvers. Expected result: Directory locator queries resolve the services of the intended AD domain. It does not directly motivate the specified Azure Private DNS resolution action.

C:

This situation concerns DNS policy geo response. It would call for: Apply a supported Windows DNS policy using client subnet scopes and zone scopes. Expected result: Different permitted client subnets receive configured location-specific resource records. It does not directly motivate the specified Azure Private DNS resolution action.

Question 661

In an archival Windows Server hybrid scenario, A public service domain moves its DNS hosting to Azure without changing its registrar. Which administrative action most directly addresses the stated requirement?

  1. Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it.
  2. Create an Azure Public DNS zone and update parent NS delegation with its Azure name servers.
  3. Configure a conditional forwarder for the partner DNS namespace to approved authoritative resolvers.
  4. Create and link the appropriate Azure Private DNS zone to the required virtual network.

Explanation

Correct Answer

B:

This directly addresses Azure public DNS delegation: Public recursive resolvers reach the new authoritative Azure DNS hosts.

Incorrect Answers

A:

This option would instead address Azure DNS Private Resolver inbound: Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it. In that situation, the expected outcome is: On-premises resolvers reach the linked Azure private DNS namespace. It does not resolve the primary Azure public DNS delegation requirement described here.

C:

This option would instead address DNS conditional forwarding partner: Configure a conditional forwarder for the partner DNS namespace to approved authoritative resolvers. In that situation, the expected outcome is: Requests for the partner suffix reach the specified partner DNS servers. It does not resolve the primary Azure public DNS delegation requirement described here.

D:

This option would instead address Azure Private DNS resolution: Create and link the appropriate Azure Private DNS zone to the required virtual network. In that situation, the expected outcome is: Azure DNS can resolve the private namespace in linked networks. It does not resolve the primary Azure public DNS delegation requirement described here.

Question 662

A Windows Server administrator takes this approved action: Create an Azure Public DNS zone and update parent NS delegation with its Azure name servers. Which operational result most directly confirms the intended outcome?

  1. On-premises resolvers reach the linked Azure private DNS namespace.
  2. Requests for the partner suffix reach the specified partner DNS servers.
  3. Public recursive resolvers reach the new authoritative Azure DNS hosts.
  4. Azure DNS can resolve the private namespace in linked networks.

Explanation

Correct Answer

C:

This confirms the intended result for Azure public DNS delegation: Public recursive resolvers reach the new authoritative Azure DNS hosts.

Incorrect Answers

A:

This is the outcome associated with Azure DNS Private Resolver inbound, achieved instead by: Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it. It is not the direct confirmation of the proposed action.

B:

This is the outcome associated with DNS conditional forwarding partner, achieved instead by: Configure a conditional forwarder for the partner DNS namespace to approved authoritative resolvers. It is not the direct confirmation of the proposed action.

D:

This is the outcome associated with Azure Private DNS resolution, achieved instead by: Create and link the appropriate Azure Private DNS zone to the required virtual network. It is not the direct confirmation of the proposed action.

Question 663

In a Windows Server hybrid environment, A public service domain moves its DNS hosting to Azure without changing its registrar. A colleague instead proposes: Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it. Which response is more directly applicable to the original requirement?

  1. Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it.
  2. Configure a conditional forwarder for the partner DNS namespace to approved authoritative resolvers.
  3. Create and link the appropriate Azure Private DNS zone to the required virtual network.
  4. Create an Azure Public DNS zone and update parent NS delegation with its Azure name servers.

Explanation

Correct Answer

D:

The action needed for Azure public DNS delegation is: Create an Azure Public DNS zone and update parent NS delegation with its Azure name servers. The expected result is: Public recursive resolvers reach the new authoritative Azure DNS hosts.

Incorrect Answers

A:

This option would instead address Azure DNS Private Resolver inbound: Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it. In that situation, the expected outcome is: On-premises resolvers reach the linked Azure private DNS namespace. It does not resolve the primary Azure public DNS delegation requirement described here.

B:

This option would instead address DNS conditional forwarding partner: Configure a conditional forwarder for the partner DNS namespace to approved authoritative resolvers. In that situation, the expected outcome is: Requests for the partner suffix reach the specified partner DNS servers. It does not resolve the primary Azure public DNS delegation requirement described here.

C:

This option would instead address Azure Private DNS resolution: Create and link the appropriate Azure Private DNS zone to the required virtual network. In that situation, the expected outcome is: Azure DNS can resolve the private namespace in linked networks. It does not resolve the primary Azure public DNS delegation requirement described here.

Question 664

A Windows Server administrator proposes this action: Create an Azure Public DNS zone and update parent NS delegation with its Azure name servers. Which situation most specifically calls for this action?

  1. A public service domain moves its DNS hosting to Azure without changing its registrar.
  2. On-premises clients cannot query Azure Private DNS zones directly through a hybrid network connection.
  3. A child domain must resolve names in a trusted partner domain without hosting its full zone locally.
  4. Azure VMs in a linked virtual network need to resolve private names for a hybrid application.

Explanation

Correct Answer

A:

This scenario is the specific context for Azure public DNS delegation. The appropriate action is to Create an Azure Public DNS zone and update parent NS delegation with its Azure name servers. Expected outcome: Public recursive resolvers reach the new authoritative Azure DNS hosts.

Incorrect Answers

B:

This situation concerns Azure DNS Private Resolver inbound. It would call for: Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it. Expected result: On-premises resolvers reach the linked Azure private DNS namespace. It does not directly motivate the specified Azure public DNS delegation action.

C:

This situation concerns DNS conditional forwarding partner. It would call for: Configure a conditional forwarder for the partner DNS namespace to approved authoritative resolvers. Expected result: Requests for the partner suffix reach the specified partner DNS servers. It does not directly motivate the specified Azure public DNS delegation action.

D:

This situation concerns Azure Private DNS resolution. It would call for: Create and link the appropriate Azure Private DNS zone to the required virtual network. Expected result: Azure DNS can resolve the private namespace in linked networks. It does not directly motivate the specified Azure public DNS delegation action.

Question 665

In an archival Windows Server hybrid scenario, On-premises clients cannot query Azure Private DNS zones directly through a hybrid network connection. Which administrative action most directly addresses the stated requirement?

  1. Configure outbound resolver endpoint rules forwarding the on-premises suffix to its DNS servers.
  2. Configure approved external DNS forwarders and validate iterative fallback policy.
  3. Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it.
  4. Create an Azure Public DNS zone and update parent NS delegation with its Azure name servers.

Explanation

Correct Answer

C:

This directly addresses Azure DNS Private Resolver inbound: On-premises resolvers reach the linked Azure private DNS namespace.

Incorrect Answers

A:

This option would instead address Azure DNS Private Resolver outbound: Configure outbound resolver endpoint rules forwarding the on-premises suffix to its DNS servers. In that situation, the expected outcome is: Azure virtual network DNS queries for the corporate suffix reach on-premises authoritative servers. It does not resolve the primary Azure DNS Private Resolver inbound requirement described here.

B:

This option would instead address DNS standard forwarder: Configure approved external DNS forwarders and validate iterative fallback policy. In that situation, the expected outcome is: External queries use the designated upstream resolvers while internal zones stay authoritative. It does not resolve the primary Azure DNS Private Resolver inbound requirement described here.

D:

This option would instead address Azure public DNS delegation: Create an Azure Public DNS zone and update parent NS delegation with its Azure name servers. In that situation, the expected outcome is: Public recursive resolvers reach the new authoritative Azure DNS hosts. It does not resolve the primary Azure DNS Private Resolver inbound requirement described here.

Question 666

A Windows Server administrator takes this approved action: Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it. Which operational result most directly confirms the intended outcome?

  1. Azure virtual network DNS queries for the corporate suffix reach on-premises authoritative servers.
  2. External queries use the designated upstream resolvers while internal zones stay authoritative.
  3. Public recursive resolvers reach the new authoritative Azure DNS hosts.
  4. On-premises resolvers reach the linked Azure private DNS namespace.

Explanation

Correct Answer

D:

This confirms the intended result for Azure DNS Private Resolver inbound: On-premises resolvers reach the linked Azure private DNS namespace.

Incorrect Answers

A:

This is the outcome associated with Azure DNS Private Resolver outbound, achieved instead by: Configure outbound resolver endpoint rules forwarding the on-premises suffix to its DNS servers. It is not the direct confirmation of the proposed action.

B:

This is the outcome associated with DNS standard forwarder, achieved instead by: Configure approved external DNS forwarders and validate iterative fallback policy. It is not the direct confirmation of the proposed action.

C:

This is the outcome associated with Azure public DNS delegation, achieved instead by: Create an Azure Public DNS zone and update parent NS delegation with its Azure name servers. It is not the direct confirmation of the proposed action.

Question 667

In a Windows Server hybrid environment, On-premises clients cannot query Azure Private DNS zones directly through a hybrid network connection. A colleague instead proposes: Configure outbound resolver endpoint rules forwarding the on-premises suffix to its DNS servers. Which response is more directly applicable to the original requirement?

  1. Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it.
  2. Configure outbound resolver endpoint rules forwarding the on-premises suffix to its DNS servers.
  3. Configure approved external DNS forwarders and validate iterative fallback policy.
  4. Create an Azure Public DNS zone and update parent NS delegation with its Azure name servers.

Explanation

Correct Answer

A:

The action needed for Azure DNS Private Resolver inbound is: Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it. The expected result is: On-premises resolvers reach the linked Azure private DNS namespace.

Incorrect Answers

B:

This option would instead address Azure DNS Private Resolver outbound: Configure outbound resolver endpoint rules forwarding the on-premises suffix to its DNS servers. In that situation, the expected outcome is: Azure virtual network DNS queries for the corporate suffix reach on-premises authoritative servers. It does not resolve the primary Azure DNS Private Resolver inbound requirement described here.

C:

This option would instead address DNS standard forwarder: Configure approved external DNS forwarders and validate iterative fallback policy. In that situation, the expected outcome is: External queries use the designated upstream resolvers while internal zones stay authoritative. It does not resolve the primary Azure DNS Private Resolver inbound requirement described here.

D:

This option would instead address Azure public DNS delegation: Create an Azure Public DNS zone and update parent NS delegation with its Azure name servers. In that situation, the expected outcome is: Public recursive resolvers reach the new authoritative Azure DNS hosts. It does not resolve the primary Azure DNS Private Resolver inbound requirement described here.

Question 668

A Windows Server administrator proposes this action: Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it. Which situation most specifically calls for this action?

  1. Azure workloads need conditional resolution of on-premises corp.example records through private connectivity.
  2. On-premises clients cannot query Azure Private DNS zones directly through a hybrid network connection.
  3. Internal DNS clients need Internet name resolution but the local domain controller is not authoritative for public zones.
  4. A public service domain moves its DNS hosting to Azure without changing its registrar.

Explanation

Correct Answer

B:

This scenario is the specific context for Azure DNS Private Resolver inbound. The appropriate action is to Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it. Expected outcome: On-premises resolvers reach the linked Azure private DNS namespace.

Incorrect Answers

A:

This situation concerns Azure DNS Private Resolver outbound. It would call for: Configure outbound resolver endpoint rules forwarding the on-premises suffix to its DNS servers. Expected result: Azure virtual network DNS queries for the corporate suffix reach on-premises authoritative servers. It does not directly motivate the specified Azure DNS Private Resolver inbound action.

C:

This situation concerns DNS standard forwarder. It would call for: Configure approved external DNS forwarders and validate iterative fallback policy. Expected result: External queries use the designated upstream resolvers while internal zones stay authoritative. It does not directly motivate the specified Azure DNS Private Resolver inbound action.

D:

This situation concerns Azure public DNS delegation. It would call for: Create an Azure Public DNS zone and update parent NS delegation with its Azure name servers. Expected result: Public recursive resolvers reach the new authoritative Azure DNS hosts. It does not directly motivate the specified Azure DNS Private Resolver inbound action.

Question 669

In an archival Windows Server hybrid scenario, Azure workloads need conditional resolution of on-premises corp.example records through private connectivity. Which administrative action most directly addresses the stated requirement?

  1. Create the appropriate CNAME where alias semantics are supported instead of duplicating unrelated A records.
  2. Create appropriately scoped internal and public DNS views or policies for that namespace.
  3. Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it.
  4. Configure outbound resolver endpoint rules forwarding the on-premises suffix to its DNS servers.

Explanation

Correct Answer

D:

This directly addresses Azure DNS Private Resolver outbound: Azure virtual network DNS queries for the corporate suffix reach on-premises authoritative servers.

Incorrect Answers

A:

This option would instead address DNS zone record type selection: Create the appropriate CNAME where alias semantics are supported instead of duplicating unrelated A records. In that situation, the expected outcome is: DNS clients resolve the application alias through the target canonical hostname. It does not resolve the primary Azure DNS Private Resolver outbound requirement described here.

B:

This option would instead address DNS split-brain requirement: Create appropriately scoped internal and public DNS views or policies for that namespace. In that situation, the expected outcome is: Each client population receives the intended address without leaking internal service mapping. It does not resolve the primary Azure DNS Private Resolver outbound requirement described here.

C:

This option would instead address Azure DNS Private Resolver inbound: Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it. In that situation, the expected outcome is: On-premises resolvers reach the linked Azure private DNS namespace. It does not resolve the primary Azure DNS Private Resolver outbound requirement described here.

Question 670

A Windows Server administrator takes this approved action: Configure outbound resolver endpoint rules forwarding the on-premises suffix to its DNS servers. Which operational result most directly confirms the intended outcome?

  1. Azure virtual network DNS queries for the corporate suffix reach on-premises authoritative servers.
  2. DNS clients resolve the application alias through the target canonical hostname.
  3. Each client population receives the intended address without leaking internal service mapping.
  4. On-premises resolvers reach the linked Azure private DNS namespace.

Explanation

Correct Answer

A:

This confirms the intended result for Azure DNS Private Resolver outbound: Azure virtual network DNS queries for the corporate suffix reach on-premises authoritative servers.

Incorrect Answers

B:

This is the outcome associated with DNS zone record type selection, achieved instead by: Create the appropriate CNAME where alias semantics are supported instead of duplicating unrelated A records. It is not the direct confirmation of the proposed action.

C:

This is the outcome associated with DNS split-brain requirement, achieved instead by: Create appropriately scoped internal and public DNS views or policies for that namespace. It is not the direct confirmation of the proposed action.

D:

This is the outcome associated with Azure DNS Private Resolver inbound, achieved instead by: Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it. It is not the direct confirmation of the proposed action.