Microsoft AZ-800 Practice Test 1 - 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 1

Question 1

At Cedarline Directory Operations, the team supports Windows Server domain controller lifecycle and authentication and must protect AD DS availability and accountable privileged change. Confirmed original fault: A newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. Supporting diagnostic evidence: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. Review the approved credential exposure risk, permit only designated branch principals and prepopulate their secrets using supported RODC controls.
  2. Restore the configured domain time hierarchy and approved external time source for the forest-root PDC emulator.
  3. Configure approved domain DNS resolvers and verify domain SRV record registration before evaluating other promotion faults.
  4. Adjust the specific site-link schedule and interval under approved WAN and replication capacity constraints.

Explanation

Correct Answer

C:

The underlying problem at Cedarline Directory Operations is that a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. The recommended response is to configure approved domain DNS resolvers and verify domain SRV record registration before evaluating other promotion faults. Verify that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.

Incorrect Answers

A:

That alternative would review the approved credential exposure risk, permit only designated branch principals and prepopulate their secrets using supported RODC controls. For Cedarline Directory Operations, that does not follow the diagnostic finding that the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. The relevant principle is that aD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.

B:

Proposing to restore the configured domain time hierarchy and approved external time source for the forest-root PDC emulator does not fit the evidence at Cedarline Directory Operations: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. That would not resolve the original failure: a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service.

D:

That alternative would adjust the specific site-link schedule and interval under approved WAN and replication capacity constraints. It misses the condition observed at Cedarline Directory Operations: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. The recommended correction addresses the observed condition directly.

Question 2

At Cedarline Directory Operations, the team supports Windows Server domain controller lifecycle and authentication and must protect AD DS availability and accountable privileged change. A reported incident states: A newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. 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. The RODC password replication policy excludes the branch staff group and the prepopulation report shows no permitted accounts.
  2. The AD site-link schedule excludes the required update period and replication metadata shows queued changes waiting for an allowed interval.
  3. The trust uses broad forest-wide authentication and access tests succeed on resource servers lacking explicit permitted-to-authenticate policy.
  4. The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain.

Explanation

Correct Answer

D:

The reported issue at Cedarline Directory Operations is that a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. The offered observation of the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain identifies the relevant fault rather than an unrelated symptom. AD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.

Incorrect Answers

A:

The observation offered is that the RODC password replication policy excludes the branch staff group and the prepopulation report shows no permitted accounts. It does not substantiate the reported Cedarline Directory Operations failure, where a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. The directly relevant diagnostic record is that the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain.

B:

The suggested evidence is that the AD site-link schedule excludes the required update period and replication metadata shows queued changes waiting for an allowed interval. In the Cedarline Directory Operations case, the actual distinguishing finding is that the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. AD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.

C:

At Cedarline Directory Operations, The alternative observation about the trust uses broad forest-wide authentication and access tests succeed on resource servers lacking explicit permitted-to-authenticate policy would not isolate the relevant problem. The diagnostic clue is that the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. This is the clue that bears on a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service.

Question 3

At Cedarline Directory Operations, the team supports Windows Server domain controller lifecycle and authentication and must protect AD DS availability and accountable privileged change. Observed issue: A newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. Investigation found: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. The proposed repair is: Configure approved domain DNS resolvers and verify domain SRV record registration before evaluating other promotion faults. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. An authorized test account signs in during a simulated WAN outage while privileged disallowed accounts remain uncached.
  2. Domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.
  3. Only the designated external accounts authenticate to approved servers and negative tests fail on unrelated sensitive hosts.
  4. The policy applies to representative intended servers and remains excluded from unrelated clients.

Explanation

Correct Answer

B:

The relevant acceptance result for Cedarline Directory Operations is that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records. It tests the outcome of the change against the fault shown by the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. AD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.

Incorrect Answers

A:

The option would validate that an authorized test account signs in during a simulated WAN outage while privileged disallowed accounts remain uncached. That does not establish correction of the Cedarline Directory Operations issue, where a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. The meaningful proof is that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.

C:

The alternative validation would show that only the designated external accounts authenticate to approved servers and negative tests fail on unrelated sensitive hosts. For Cedarline Directory Operations, that is insufficient to establish that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records. The original diagnostic finding is that the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain.

D:

At Cedarline Directory Operations, a test showing that the policy applies to representative intended servers and remains excluded from unrelated clients would not confirm the needed outcome. The check must demonstrate that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records. It must address the failure, where a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service.

Question 4

At Cedarline Directory Operations, the team supports Windows Server domain controller lifecycle and authentication and must protect AD DS availability and accountable privileged change. The administrator observes: A newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. The distinguishing clue is: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. 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. AD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.
  2. Read-only domain controller offline authentication requires specifically permitted credential caching with least privilege.
  3. Kerberos service identity selection depends on unambiguous SPN ownership.
  4. Group Policy WMI filtering gates whether a GPO applies, independent of its OU link.

Explanation

Correct Answer

A:

The mechanism is expressed by this principle: AD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution. It accounts for the case at Cedarline Directory Operations, where the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. It explains the problem, where a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service.

Incorrect Answers

B:

The case at Cedarline Directory Operations is that a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. The offered principle, read-only domain controller offline authentication requires specifically permitted credential caching with least privilege, would not explain this observed failure. The relevant mechanism is that aD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.

C:

The alternative rule states that kerberos service identity selection depends on unambiguous SPN ownership. It does not account for the Cedarline Directory Operations evidence: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. The case turns on the mechanism that aD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.

D:

The alternative principle is that group Policy WMI filtering gates whether a GPO applies, independent of its OU link. For Cedarline Directory Operations, it does not explain why the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. The applicable causal rule is that aD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.

Question 5

At Cedarline Directory Operations, the team supports Windows Server domain controller lifecycle and authentication and must protect AD DS availability and accountable privileged change. The original incident is: A newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. The evidence is: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. 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: After proving permanent loss and validating backups, follow documented seizure and metadata-cleanup procedures for the specific FSMO role. Evidence of success: A healthy domain controller owns the role, RID allocation resumes and the failed former owner cannot be reintroduced without remediation.
  2. Action: Configure approved domain DNS resolvers and verify domain SRV record registration before evaluating other promotion faults. Evidence of success: Domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.
  3. Action: Place the host in the authorized routed network and validate NSG, firewall, DNS and VPN paths for only required AD DS protocols. Evidence of success: Replication diagnostics complete between the relevant site partners and the VM remains reachable under restricted administration rules.
  4. Action: Determine the supported service owner, remove the conflicting stale SPN and register only the correct unique service identity. Evidence of success: Kerberos service tickets resolve to the intended account and representative clients authenticate without duplicate-SPN errors.

Explanation

Correct Answer

B:

The case at Cedarline Directory Operations requires both correction and evidence for the same fault. The proposed pair is Action: Configure approved domain DNS resolvers and verify domain SRV record registration before evaluating other promotion faults. Evidence of success: Domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records. It addresses the finding that the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain and tests whether domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.

Incorrect Answers

A:

This offered change and proof, action: After proving permanent loss and validating backups, follow documented seizure and metadata-cleanup procedures for the specific FSMO role. Evidence of success: A healthy domain controller owns the role, RID allocation resumes and the failed former owner cannot be reintroduced without remediation, would leave the Cedarline Directory Operations case unverified. The actual recorded fault is that a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. A meaningful check requires that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.

C:

The paired remediation states Action: Place the host in the authorized routed network and validate NSG, firewall, DNS and VPN paths for only required AD DS protocols. Evidence of success: Replication diagnostics complete between the relevant site partners and the VM remains reachable under restricted administration rules. It does not test correction of the Cedarline Directory Operations condition: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. The outcome to verify is that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.

D:

That action and check pair is Action: Determine the supported service owner, remove the conflicting stale SPN and register only the correct unique service identity. Evidence of success: Kerberos service tickets resolve to the intended account and representative clients authenticate without duplicate-SPN errors. It does not connect both parts to the actual Cedarline Directory Operations clue: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. The acceptance test needs to show that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.

Question 6

At Harborview Identity Federation, the team supports on-premises identities synchronized to Microsoft Entra and must preserve approved authoritative identity scope and sign-in controls. Confirmed original fault: A newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. Supporting diagnostic evidence: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. After proving permanent loss and validating backups, follow documented seizure and metadata-cleanup procedures for the specific FSMO role.
  2. Configure approved domain DNS resolvers and verify domain SRV record registration before evaluating other promotion faults.
  3. Restore the configured domain time hierarchy and approved external time source for the forest-root PDC emulator.
  4. Configure approved conditional forwarders or equivalent trusted DNS resolution and validate the precise trust direction and authentication rules.

Explanation

Correct Answer

B:

The underlying problem at Harborview Identity Federation is that a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. The recommended response is to configure approved domain DNS resolvers and verify domain SRV record registration before evaluating other promotion faults. Verify that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.

Incorrect Answers

A:

Proposing to after proving permanent loss and validating backups, follow documented seizure and metadata-cleanup procedures for the specific FSMO role does not fit the evidence at Harborview Identity Federation: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. That would not resolve the original failure: a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service.

C:

That alternative would restore the configured domain time hierarchy and approved external time source for the forest-root PDC emulator. It misses the condition observed at Harborview Identity Federation: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. The recommended correction addresses the observed condition directly.

D:

The failure at Harborview Identity Federation is that a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. That does not call for configure approved conditional forwarders or equivalent trusted DNS resolution and validate the precise trust direction and authentication rules. The case evidence instead establishes that the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain.

Question 7

At Harborview Identity Federation, the team supports on-premises identities synchronized to Microsoft Entra and must preserve approved authoritative identity scope and sign-in controls. A reported incident states: A newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. 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. Operations master queries still name the decommissioned RID Master and domain controllers log exhausted or unavailable RID allocation requests.
  2. The AD site-link schedule excludes the required update period and replication metadata shows queued changes waiting for an allowed interval.
  3. The service logon identity belongs to the privileged administrators group and the service starts with a stored long-lived password.
  4. The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain.

Explanation

Correct Answer

D:

At Harborview Identity Federation, the distinguishing evidence is: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. It is directly connected to a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. AD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.

Incorrect Answers

A:

The suggested evidence is that operations master queries still name the decommissioned RID Master and domain controllers log exhausted or unavailable RID allocation requests. In the Harborview Identity Federation case, the actual distinguishing finding is that the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. AD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.

B:

At Harborview Identity Federation, The alternative observation about the AD site-link schedule excludes the required update period and replication metadata shows queued changes waiting for an allowed interval would not isolate the relevant problem. The diagnostic clue is that the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. This is the clue that bears on a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service.

C:

An unrelated diagnosis would involve: The service logon identity belongs to the privileged administrators group and the service starts with a stored long-lived password. The incident at Harborview Identity Federation is that a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. The decisive finding instead is that the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain.

Question 8

At Harborview Identity Federation, the team supports on-premises identities synchronized to Microsoft Entra and must preserve approved authoritative identity scope and sign-in controls. Observed issue: A newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. Investigation found: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. The proposed repair is: Configure approved domain DNS resolvers and verify domain SRV record registration before evaluating other promotion faults. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. Domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.
  2. A healthy domain controller owns the role, RID allocation resumes and the failed former owner cannot be reintroduced without remediation.
  3. Only the designated external accounts authenticate to approved servers and negative tests fail on unrelated sensitive hosts.
  4. The mapped drive appears for an authorized test user and stays absent for an unrelated user.

Explanation

Correct Answer

A:

The relevant acceptance result for Harborview Identity Federation is that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records. It tests the outcome of the change against the fault shown by the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. AD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.

Incorrect Answers

B:

The alternative validation would show that a healthy domain controller owns the role, RID allocation resumes and the failed former owner cannot be reintroduced without remediation. For Harborview Identity Federation, that is insufficient to establish that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records. The original diagnostic finding is that the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain.

C:

At Harborview Identity Federation, a test showing that only the designated external accounts authenticate to approved servers and negative tests fail on unrelated sensitive hosts would not confirm the needed outcome. The check must demonstrate that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records. It must address the failure, where a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service.

D:

That verification is that the mapped drive appears for an authorized test user and stays absent for an unrelated user. The Harborview Identity Federation acceptance criterion is instead that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records. The recorded causal clue is that the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain.

Question 9

At Harborview Identity Federation, the team supports on-premises identities synchronized to Microsoft Entra and must preserve approved authoritative identity scope and sign-in controls. The administrator observes: A newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. The distinguishing clue is: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. 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. Role seizure is an exceptional recovery action that requires confirming permanent owner loss and avoiding simultaneous role owners.
  2. AD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.
  3. Kerberos service identity selection depends on unambiguous SPN ownership.
  4. GPP item-level targeting can block individual preference actions even when the enclosing GPO is applied.

Explanation

Correct Answer

B:

The appropriate mechanism for Harborview Identity Federation is that aD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution. This explains the recorded clue: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. It accounts for the reported failure, where a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service.

Incorrect Answers

A:

The case at Harborview Identity Federation is that a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. The offered principle, role seizure is an exceptional recovery action that requires confirming permanent owner loss and avoiding simultaneous role owners, would not explain this observed failure. The relevant mechanism is that aD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.

C:

The alternative principle is that kerberos service identity selection depends on unambiguous SPN ownership. For Harborview Identity Federation, it does not explain why the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. The applicable causal rule is that aD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.

D:

This offered mechanism, gPP item-level targeting can block individual preference actions even when the enclosing GPO is applied, does not match the specific recorded failure at Harborview Identity Federation, where a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. The relevant principle is that aD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.

Question 10

At Harborview Identity Federation, the team supports on-premises identities synchronized to Microsoft Entra and must preserve approved authoritative identity scope and sign-in controls. The original incident is: A newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. The evidence is: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. 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: Place the host in the authorized routed network and validate NSG, firewall, DNS and VPN paths for only required AD DS protocols. Evidence of success: Replication diagnostics complete between the relevant site partners and the VM remains reachable under restricted administration rules.
  2. Action: Configure approved domain DNS resolvers and verify domain SRV record registration before evaluating other promotion faults. Evidence of success: Domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.
  3. Action: Restore the configured domain time hierarchy and approved external time source for the forest-root PDC emulator. Evidence of success: The drift returns within the expected Kerberos tolerance and representative domain logons succeed without time skew errors.
  4. Action: Resolve the identity matching conflict according to documented immutable anchor and supported soft/hard match practices after preserving account data. Evidence of success: The supported authoritative identity relationship is established and licensed application access remains intact.

Explanation

Correct Answer

B:

That intervention and proof go together at Harborview Identity Federation: Action: Configure approved domain DNS resolvers and verify domain SRV record registration before evaluating other promotion faults. Evidence of success: Domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records. The relevant root finding is that the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. It is closed only when domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.

Incorrect Answers

A:

The alternative combined step is Action: Place the host in the authorized routed network and validate NSG, firewall, DNS and VPN paths for only required AD DS protocols. Evidence of success: Replication diagnostics complete between the relevant site partners and the VM remains reachable under restricted administration rules. The relevant Harborview Identity Federation evidence is that the server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. Closure must validate that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records, rather than a different symptom.

C:

That action and check pair is Action: Restore the configured domain time hierarchy and approved external time source for the forest-root PDC emulator. Evidence of success: The drift returns within the expected Kerberos tolerance and representative domain logons succeed without time skew errors. It does not connect both parts to the actual Harborview Identity Federation clue: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. The acceptance test needs to show that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.

D:

The paired proposal is Action: Resolve the identity matching conflict according to documented immutable anchor and supported soft/hard match practices after preserving account data. Evidence of success: The supported authoritative identity relationship is established and licensed application access remains intact. For Harborview Identity Federation, it fails to establish an intervention and check for the documented issue, where a newly promoted branch domain controller cannot complete normal domain operations because its network interface points to a public resolver instead of the AD-integrated DNS service. Successful closure requires that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.

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