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 64

Question 630

A Windows Server administrator takes this approved action: Configure a conditional forwarder for the partner DNS namespace to approved authoritative resolvers. Which operational result most directly confirms the intended outcome?

  1. External queries use the designated upstream resolvers while internal zones stay authoritative.
  2. Public recursive resolvers reach the new authoritative Azure DNS hosts.
  3. Requests for the partner suffix reach the specified partner DNS servers.
  4. Directory locator queries resolve the services of the intended AD domain.

Explanation

Correct Answer

C:

This confirms the intended result for DNS conditional forwarding partner: Requests for the partner suffix reach the specified partner DNS servers.

Incorrect Answers

A:

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.

B:

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.

D:

This is the outcome associated with DNS SRV controller discovery, achieved instead by: Verify the configured DNS server and AD DS SRV records rather than using arbitrary public resolvers. It is not the direct confirmation of the proposed action.

Question 631

In a Windows Server hybrid environment, A child domain must resolve names in a trusted partner domain without hosting its full zone locally. A colleague instead proposes: Configure approved external DNS forwarders and validate iterative fallback policy. Which response is more directly applicable to the original requirement?

  1. Configure approved external DNS forwarders and validate iterative fallback policy.
  2. Create an Azure Public DNS zone and update parent NS delegation with its Azure name servers.
  3. Verify the configured DNS server and AD DS SRV records rather than using arbitrary public resolvers.
  4. Configure a conditional forwarder for the partner DNS namespace to approved authoritative resolvers.

Explanation

Correct Answer

D:

The action needed for DNS conditional forwarding partner is: Configure a conditional forwarder for the partner DNS namespace to approved authoritative resolvers. The expected result is: Requests for the partner suffix reach the specified partner DNS servers.

Incorrect Answers

A:

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 DNS conditional forwarding partner requirement described here.

B:

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 DNS conditional forwarding partner requirement described here.

C:

This option would instead address DNS SRV controller discovery: Verify the configured DNS server and AD DS SRV records rather than using arbitrary public resolvers. In that situation, the expected outcome is: Directory locator queries resolve the services of the intended AD domain. It does not resolve the primary DNS conditional forwarding partner requirement described here.

Question 632

A Windows Server administrator proposes this action: Configure a conditional forwarder for the partner DNS namespace to approved authoritative resolvers. Which situation most specifically calls for this action?

  1. A child domain must resolve names in a trusted partner domain without hosting its full zone locally.
  2. Internal DNS clients need Internet name resolution but the local domain controller is not authoritative for public zones.
  3. A public service domain moves its DNS hosting to Azure without changing its registrar.
  4. A domain-joined workstation fails to locate a controller even though its gateway and ping work.

Explanation

Correct Answer

A:

This scenario is the specific context for DNS conditional forwarding partner. The appropriate action is to Configure a conditional forwarder for the partner DNS namespace to approved authoritative resolvers. Expected outcome: Requests for the partner suffix reach the specified partner DNS servers.

Incorrect Answers

B:

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 DNS conditional forwarding partner action.

C:

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 DNS conditional forwarding partner action.

D:

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 DNS conditional forwarding partner action.

Question 633

In an archival Windows Server hybrid scenario, Internal DNS clients need Internet name resolution but the local domain controller is not authoritative for public zones. Which administrative action most directly addresses the stated requirement?

  1. Create appropriately scoped internal and public DNS views or policies for that namespace.
  2. Deploy an Azure DNS Private Resolver inbound endpoint and forward on-premises zone queries to it.
  3. Configure approved external DNS forwarders and validate iterative fallback policy.
  4. Configure a conditional forwarder for the partner DNS namespace to approved authoritative resolvers.

Explanation

Correct Answer

C:

This directly addresses DNS standard forwarder: External queries use the designated upstream resolvers while internal zones stay authoritative.

Incorrect Answers

A:

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 DNS standard forwarder requirement described here.

B:

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 DNS standard forwarder requirement described here.

D:

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 DNS standard forwarder requirement described here.

Question 634

A Windows Server administrator takes this approved action: Configure approved external DNS forwarders and validate iterative fallback policy. Which operational result most directly confirms the intended outcome?

  1. Each client population receives the intended address without leaking internal service mapping.
  2. On-premises resolvers reach the linked Azure private DNS namespace.
  3. Requests for the partner suffix reach the specified partner DNS servers.
  4. External queries use the designated upstream resolvers while internal zones stay authoritative.

Explanation

Correct Answer

D:

This confirms the intended result for DNS standard forwarder: External queries use the designated upstream resolvers while internal zones stay authoritative.

Incorrect Answers

A:

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.

B:

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.

C:

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.

Question 635

In a Windows Server hybrid environment, Internal DNS clients need Internet name resolution but the local domain controller is not authoritative for public zones. A colleague instead proposes: Create appropriately scoped internal and public DNS views or policies for that namespace. Which response is more directly applicable to the original requirement?

  1. Configure approved external DNS forwarders and validate iterative fallback policy.
  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 a conditional forwarder for the partner DNS namespace to approved authoritative resolvers.

Explanation

Correct Answer

A:

The action needed for DNS standard forwarder is: Configure approved external DNS forwarders and validate iterative fallback policy. The expected result is: External queries use the designated upstream resolvers while internal zones stay authoritative.

Incorrect Answers

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 DNS standard forwarder 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 DNS standard forwarder requirement described here.

D:

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 DNS standard forwarder requirement described here.

Question 636

A Windows Server administrator proposes this action: Configure approved external DNS forwarders and validate iterative fallback policy. Which situation most specifically calls for this action?

  1. An application name must resolve to a private endpoint for on-premises clients and a public endpoint for Internet users.
  2. Internal DNS clients need Internet name resolution but the local domain controller is not authoritative for public zones.
  3. On-premises clients cannot query Azure Private DNS zones directly through a hybrid network connection.
  4. A child domain must resolve names in a trusted partner domain without hosting its full zone locally.

Explanation

Correct Answer

B:

This scenario is the specific context for DNS standard forwarder. The appropriate action is to Configure approved external DNS forwarders and validate iterative fallback policy. Expected outcome: External queries use the designated upstream resolvers while internal zones stay authoritative.

Incorrect Answers

A:

This situation concerns DNS split-brain requirement. It would call for: Create appropriately scoped internal and public DNS views or policies for that namespace. Expected result: Each client population receives the intended address without leaking internal service mapping. It does not directly motivate the specified DNS standard forwarder action.

C:

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 DNS standard forwarder action.

D:

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 DNS standard forwarder action.

Question 637

In an archival Windows Server hybrid scenario, An application name must resolve to a private endpoint for on-premises clients and a public endpoint for Internet users. Which administrative action most directly addresses the stated requirement?

  1. Create and maintain the appropriate DNS reverse lookup zone and PTR records.
  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 appropriately scoped internal and public DNS views or policies for that namespace.

Explanation

Correct Answer

D:

This directly addresses DNS split-brain requirement: Each client population receives the intended address without leaking internal service mapping.

Incorrect Answers

A:

This option would instead address DNS reverse lookup: Create and maintain the appropriate DNS reverse lookup zone and PTR records. In that situation, the expected outcome is: Reverse queries resolve the authorized addresses to their intended hostnames. It does not resolve the primary DNS split-brain requirement requirement described here.

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 DNS split-brain requirement 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 DNS split-brain requirement requirement described here.

Question 638

A Windows Server administrator takes this approved action: Create appropriately scoped internal and public DNS views or policies for that namespace. Which operational result most directly confirms the intended outcome?

  1. Each client population receives the intended address without leaking internal service mapping.
  2. Reverse queries resolve the authorized addresses to their intended hostnames.
  3. Azure virtual network DNS queries for the corporate suffix reach on-premises authoritative servers.
  4. External queries use the designated upstream resolvers while internal zones stay authoritative.

Explanation

Correct Answer

A:

This confirms the intended result for DNS split-brain requirement: Each client population receives the intended address without leaking internal service mapping.

Incorrect Answers

B:

This is the outcome associated with DNS reverse lookup, achieved instead by: Create and maintain the appropriate DNS reverse lookup zone and PTR records. It is not the direct confirmation of the proposed action.

C:

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.

D:

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.

Question 639

In a Windows Server hybrid environment, An application name must resolve to a private endpoint for on-premises clients and a public endpoint for Internet users. A colleague instead proposes: Create and maintain the appropriate DNS reverse lookup zone and PTR records. Which response is more directly applicable to the original requirement?

  1. Create and maintain the appropriate DNS reverse lookup zone and PTR records.
  2. Create appropriately scoped internal and public DNS views or policies for that namespace.
  3. Configure outbound resolver endpoint rules forwarding the on-premises suffix to its DNS servers.
  4. Configure approved external DNS forwarders and validate iterative fallback policy.

Explanation

Correct Answer

B:

The action needed for DNS split-brain requirement is: Create appropriately scoped internal and public DNS views or policies for that namespace. The expected result is: Each client population receives the intended address without leaking internal service mapping.

Incorrect Answers

A:

This option would instead address DNS reverse lookup: Create and maintain the appropriate DNS reverse lookup zone and PTR records. In that situation, the expected outcome is: Reverse queries resolve the authorized addresses to their intended hostnames. It does not resolve the primary DNS split-brain requirement requirement described here.

C:

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 DNS split-brain requirement requirement described here.

D:

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 DNS split-brain requirement requirement described here.

Question 640

A Windows Server administrator proposes this action: Create appropriately scoped internal and public DNS views or policies for that namespace. Which situation most specifically calls for this action?

  1. A security log records only IP addresses and analysts require name mapping for local workloads.
  2. Azure workloads need conditional resolution of on-premises corp.example records through private connectivity.
  3. An application name must resolve to a private endpoint for on-premises clients and a public endpoint for Internet users.
  4. Internal DNS clients need Internet name resolution but the local domain controller is not authoritative for public zones.

Explanation

Correct Answer

C:

This scenario is the specific context for DNS split-brain requirement. The appropriate action is to Create appropriately scoped internal and public DNS views or policies for that namespace. Expected outcome: Each client population receives the intended address without leaking internal service mapping.

Incorrect Answers

A:

This situation concerns DNS reverse lookup. It would call for: Create and maintain the appropriate DNS reverse lookup zone and PTR records. Expected result: Reverse queries resolve the authorized addresses to their intended hostnames. It does not directly motivate the specified DNS split-brain requirement action.

B:

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 DNS split-brain requirement action.

D:

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 DNS split-brain requirement action.