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

Question 250

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 published-session host applies each user's desktop settings instead of the consistent lockdown policy intended for the shared server. The evidence is: Group Policy result on the session host lacks the approved loopback processing mode and inherits ordinary user OU policies. 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 and test the intended loopback merge or replace policy on the server OU with documented exceptions. Evidence of success: A test user receives the session host's authorized lockdown controls without affecting the same user on ordinary desktops.
  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: Review the approved credential exposure risk, permit only designated branch principals and prepopulate their secrets using supported RODC controls. Evidence of success: An authorized test account signs in during a simulated WAN outage while privileged disallowed accounts remain uncached.
  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

A:

The case at Harborview Identity Federation requires both correction and evidence for the same fault. The proposed pair is Action: Configure and test the intended loopback merge or replace policy on the server OU with documented exceptions. Evidence of success: A test user receives the session host's authorized lockdown controls without affecting the same user on ordinary desktops. It addresses the finding that group Policy result on the session host lacks the approved loopback processing mode and inherits ordinary user OU policies and tests whether a test user receives the session host's authorized lockdown controls without affecting the same user on ordinary desktops.

Incorrect Answers

B:

The paired remediation states 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 does not test correction of the Harborview Identity Federation condition: Group Policy result on the session host lacks the approved loopback processing mode and inherits ordinary user OU policies. The outcome to verify is that a test user receives the session host's authorized lockdown controls without affecting the same user on ordinary desktops.

C:

That action and check pair is Action: Review the approved credential exposure risk, permit only designated branch principals and prepopulate their secrets using supported RODC controls. Evidence of success: An authorized test account signs in during a simulated WAN outage while privileged disallowed accounts remain uncached. It does not connect both parts to the actual Harborview Identity Federation clue: Group Policy result on the session host lacks the approved loopback processing mode and inherits ordinary user OU policies. The acceptance test needs to show that a test user receives the session host's authorized lockdown controls without affecting the same user on ordinary desktops.

D:

The paired proposal 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. For Harborview Identity Federation, it fails to establish an intervention and check for the documented issue, where a published-session host applies each user's desktop settings instead of the consistent lockdown policy intended for the shared server. Successful closure requires that a test user receives the session host's authorized lockdown controls without affecting the same user on ordinary desktops.

Question 251

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: Domain administrators see a revised GPO version number but branch clients still download an older script. Supporting diagnostic evidence: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. Repair the underlying DFSR SYSVOL replication health and verify both policy metadata and files before forcing clients to refresh.
  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. Create a narrowly scoped managed service identity when supported and assign only the needed local and network rights.

Explanation

Correct Answer

A:

The underlying problem at Harborview Identity Federation is that domain administrators see a revised GPO version number but branch clients still download an older script. Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The recommended response is to repair the underlying DFSR SYSVOL replication health and verify both policy metadata and files before forcing clients to refresh. Verify that branch clients apply the updated file content and replication reports synchronized SYSVOL state.

Incorrect Answers

B:

That alternative would configure approved domain DNS resolvers and verify domain SRV record registration before evaluating other promotion faults. It misses the condition observed at Harborview Identity Federation: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The recommended correction addresses the observed condition directly.

C:

The failure at Harborview Identity Federation is that domain administrators see a revised GPO version number but branch clients still download an older script. That does not call for restore the configured domain time hierarchy and approved external time source for the forest-root PDC emulator. The case evidence instead establishes that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated.

D:

At Harborview Identity Federation, proposing to create a narrowly scoped managed service identity when supported and assign only the needed local and network rights would not address the recorded evidence: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The case instead needs an intervention related to domain administrators see a revised GPO version number but branch clients still download an older script. Group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

Question 252

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: Domain administrators see a revised GPO version number but branch clients still download an older script. 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. Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated.
  2. The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain.
  3. The AD site-link schedule excludes the required update period and replication metadata shows queued changes waiting for an allowed interval.
  4. Synchronization logs show an immutable source anchor mismatch and two cloud objects share similar sign-in attributes.

Explanation

Correct Answer

A:

For Harborview Identity Federation, this is the discriminating finding: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. It accounts for the reported problem, where domain administrators see a revised GPO version number but branch clients still download an older script. Group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

Incorrect Answers

B:

An unrelated diagnosis would involve: The server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain. The incident at Harborview Identity Federation is that domain administrators see a revised GPO version number but branch clients still download an older script. The decisive finding instead is that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated.

C:

This observation, the AD site-link schedule excludes the required update period and replication metadata shows queued changes waiting for an allowed interval, does not match the evidence in the Harborview Identity Federation record. Instead, the record shows that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. Group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

D:

For Harborview Identity Federation, the proposed observation is that synchronization logs show an immutable source anchor mismatch and two cloud objects share similar sign-in attributes. It would not distinguish the identified failure, where domain administrators see a revised GPO version number but branch clients still download an older script. The meaningful clue is that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated.

Question 253

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: Domain administrators see a revised GPO version number but branch clients still download an older script. Investigation found: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The proposed repair is: Repair the underlying DFSR SYSVOL replication health and verify both policy metadata and files before forcing clients to refresh. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. Branch clients apply the updated file content and replication reports synchronized SYSVOL state.
  2. Domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records.
  3. The service starts with the new identity while a negative privileged action is denied and administrative memberships remain unchanged.
  4. Authorized pilot users use the expected method and nonpilot users continue through the documented existing flow.

Explanation

Correct Answer

A:

At Harborview Identity Federation, the selected verification result is that branch clients apply the updated file content and replication reports synchronized SYSVOL state. This checks recovery of the reported issue, where domain administrators see a revised GPO version number but branch clients still download an older script. Group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

Incorrect Answers

B:

At Harborview Identity Federation, a test showing that domain controller diagnostic tests locate writable peers and correctly resolve the domain controller locator service records would not confirm the needed outcome. The check must demonstrate that branch clients apply the updated file content and replication reports synchronized SYSVOL state. It must address the failure, where domain administrators see a revised GPO version number but branch clients still download an older script.

C:

That verification is that the service starts with the new identity while a negative privileged action is denied and administrative memberships remain unchanged. The Harborview Identity Federation acceptance criterion is instead that branch clients apply the updated file content and replication reports synchronized SYSVOL state. The recorded causal clue is that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated.

D:

This check suggests that authorized pilot users use the expected method and nonpilot users continue through the documented existing flow. It does not test the resolution criterion for Harborview Identity Federation, namely that branch clients apply the updated file content and replication reports synchronized SYSVOL state. Group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

Question 254

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: Domain administrators see a revised GPO version number but branch clients still download an older script. The distinguishing clue is: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. 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. Hybrid identities need a stable authoritative source anchor and careful collision resolution rather than indiscriminate object recreation.
  3. Group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.
  4. Group Policy WMI filtering gates whether a GPO applies, independent of its OU link.

Explanation

Correct Answer

C:

At Harborview Identity Federation, the key technical rule is that group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers. The evidence is that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. This links the observed failure to its underlying cause.

Incorrect Answers

A:

The alternative rule states that aD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution. It does not account for the Harborview Identity Federation evidence: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The case turns on the mechanism that group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

B:

The alternative principle is that hybrid identities need a stable authoritative source anchor and careful collision resolution rather than indiscriminate object recreation. For Harborview Identity Federation, it does not explain why domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The applicable causal rule is that group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

D:

At Harborview Identity Federation, the reported clue is that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The principle of group Policy WMI filtering gates whether a GPO applies, independent of its OU link does not explain that finding. The appropriate explanation is that group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

Question 255

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: Domain administrators see a revised GPO version number but branch clients still download an older script. The evidence is: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. 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: Review the approved credential exposure risk, permit only designated branch principals and prepopulate their secrets using supported RODC controls. Evidence of success: An authorized test account signs in during a simulated WAN outage while privileged disallowed accounts remain uncached.
  2. 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.
  3. Action: Restore approved proxy and outbound endpoint access for the provisioning agent while retaining minimum network access. Evidence of success: A controlled new test identity appears in the target scope and sync health reports successful agent communication.
  4. Action: Repair the underlying DFSR SYSVOL replication health and verify both policy metadata and files before forcing clients to refresh. Evidence of success: Branch clients apply the updated file content and replication reports synchronized SYSVOL state.

Explanation

Correct Answer

D:

The documented issue at Harborview Identity Federation is that domain administrators see a revised GPO version number but branch clients still download an older script. The selected combined action and test is Action: Repair the underlying DFSR SYSVOL replication health and verify both policy metadata and files before forcing clients to refresh. Evidence of success: Branch clients apply the updated file content and replication reports synchronized SYSVOL state. Its verification aligns with the required outcome: Branch clients apply the updated file content and replication reports synchronized SYSVOL state.

Incorrect Answers

A:

The paired remediation states Action: Review the approved credential exposure risk, permit only designated branch principals and prepopulate their secrets using supported RODC controls. Evidence of success: An authorized test account signs in during a simulated WAN outage while privileged disallowed accounts remain uncached. It does not test correction of the Harborview Identity Federation condition: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The outcome to verify is that branch clients apply the updated file content and replication reports synchronized SYSVOL state.

B:

That action and check pair 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. It does not connect both parts to the actual Harborview Identity Federation clue: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The acceptance test needs to show that branch clients apply the updated file content and replication reports synchronized SYSVOL state.

C:

The paired proposal is Action: Restore approved proxy and outbound endpoint access for the provisioning agent while retaining minimum network access. Evidence of success: A controlled new test identity appears in the target scope and sync health reports successful agent communication. For Harborview Identity Federation, it fails to establish an intervention and check for the documented issue, where domain administrators see a revised GPO version number but branch clients still download an older script. Successful closure requires that branch clients apply the updated file content and replication reports synchronized SYSVOL state.

Question 256

At Northgate Enterprise Directory, the team supports multi-domain policy and cross-forest resource access and must validate trusts, replication and permissions without broadening privilege. Confirmed original fault: Domain administrators see a revised GPO version number but branch clients still download an older script. Supporting diagnostic evidence: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. 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. Repair the underlying DFSR SYSVOL replication health and verify both policy metadata and files before forcing clients to refresh.
  4. Authorize the exact host computer in the designated gMSA retrieval group and refresh its group token or Kerberos context appropriately.

Explanation

Correct Answer

C:

At Northgate Enterprise Directory, the relevant observation is that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The direct correction is to repair the underlying DFSR SYSVOL replication health and verify both policy metadata and files before forcing clients to refresh. Group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers. Verify that branch clients apply the updated file content and replication reports synchronized SYSVOL state.

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. It misses the condition observed at Northgate Enterprise Directory: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The recommended correction addresses the observed condition directly.

B:

The failure at Northgate Enterprise Directory is that domain administrators see a revised GPO version number but branch clients still download an older script. That does not call for restore the configured domain time hierarchy and approved external time source for the forest-root PDC emulator. The case evidence instead establishes that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated.

D:

That alternative would authorize the exact host computer in the designated gMSA retrieval group and refresh its group token or Kerberos context appropriately. For Northgate Enterprise Directory, that does not follow the diagnostic finding that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The relevant principle is that group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

Question 257

At Northgate Enterprise Directory, the team supports multi-domain policy and cross-forest resource access and must validate trusts, replication and permissions without broadening privilege. A reported incident states: Domain administrators see a revised GPO version number but branch clients still download an older script. 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. Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated.
  4. Agent diagnostic logs identify blocked outbound HTTPS to required Microsoft provisioning endpoints from the agent host.

Explanation

Correct Answer

C:

This observation is the appropriate evidence for Northgate Enterprise Directory: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. It explains the problem, where domain administrators see a revised GPO version number but branch clients still download an older script. Group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

Incorrect Answers

A:

An unrelated diagnosis would involve: The RODC password replication policy excludes the branch staff group and the prepopulation report shows no permitted accounts. The incident at Northgate Enterprise Directory is that domain administrators see a revised GPO version number but branch clients still download an older script. The decisive finding instead is that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated.

B:

This observation, the AD site-link schedule excludes the required update period and replication metadata shows queued changes waiting for an allowed interval, does not match the evidence in the Northgate Enterprise Directory record. Instead, the record shows that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. Group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

D:

The observation offered is that agent diagnostic logs identify blocked outbound HTTPS to required Microsoft provisioning endpoints from the agent host. It does not substantiate the reported Northgate Enterprise Directory failure, where domain administrators see a revised GPO version number but branch clients still download an older script. The directly relevant diagnostic record is that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated.

Question 258

At Northgate Enterprise Directory, the team supports multi-domain policy and cross-forest resource access and must validate trusts, replication and permissions without broadening privilege. Observed issue: Domain administrators see a revised GPO version number but branch clients still download an older script. Investigation found: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The proposed repair is: Repair the underlying DFSR SYSVOL replication health and verify both policy metadata and files before forcing clients to refresh. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. Branch clients apply the updated file content and replication reports synchronized SYSVOL state.
  2. An authorized test account signs in during a simulated WAN outage while privileged disallowed accounts remain uncached.
  3. The service starts with the new identity while a negative privileged action is denied and administrative memberships remain unchanged.
  4. The application uses a supported directory design without attempts to seize managed-domain controller privileges.

Explanation

Correct Answer

A:

The proof must establish that branch clients apply the updated file content and replication reports synchronized SYSVOL state. That directly tests the observed condition at Northgate Enterprise Directory: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. Group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

Incorrect Answers

B:

That verification is that an authorized test account signs in during a simulated WAN outage while privileged disallowed accounts remain uncached. The Northgate Enterprise Directory acceptance criterion is instead that branch clients apply the updated file content and replication reports synchronized SYSVOL state. The recorded causal clue is that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated.

C:

This check suggests that the service starts with the new identity while a negative privileged action is denied and administrative memberships remain unchanged. It does not test the resolution criterion for Northgate Enterprise Directory, namely that branch clients apply the updated file content and replication reports synchronized SYSVOL state. Group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

D:

The option would validate that the application uses a supported directory design without attempts to seize managed-domain controller privileges. That does not establish correction of the Northgate Enterprise Directory issue, where domain administrators see a revised GPO version number but branch clients still download an older script. The meaningful proof is that branch clients apply the updated file content and replication reports synchronized SYSVOL state.

Question 259

At Northgate Enterprise Directory, the team supports multi-domain policy and cross-forest resource access and must validate trusts, replication and permissions without broadening privilege. The administrator observes: Domain administrators see a revised GPO version number but branch clients still download an older script. The distinguishing clue is: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. 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. Group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.
  2. Read-only domain controller offline authentication requires specifically permitted credential caching with least privilege.
  3. Hybrid identities need a stable authoritative source anchor and careful collision resolution rather than indiscriminate object recreation.
  4. GPP item-level targeting can block individual preference actions even when the enclosing GPO is applied.

Explanation

Correct Answer

A:

The selected principle is that group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers. It fits the Northgate Enterprise Directory case because domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The reported failure is that domain administrators see a revised GPO version number but branch clients still download an older script.

Incorrect Answers

B:

This offered mechanism, read-only domain controller offline authentication requires specifically permitted credential caching with least privilege, does not match the specific recorded failure at Northgate Enterprise Directory, where domain administrators see a revised GPO version number but branch clients still download an older script. The relevant principle is that group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

C:

At Northgate Enterprise Directory, the reported clue is that domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The principle of hybrid identities need a stable authoritative source anchor and careful collision resolution rather than indiscriminate object recreation does not explain that finding. The appropriate explanation is that group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

D:

The alternate technical explanation says that gPP item-level targeting can block individual preference actions even when the enclosing GPO is applied. It is not the mechanism identified by the Northgate Enterprise Directory record: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. Group Policy correctness depends on both directory metadata and SYSVOL content being consistent across controllers.

Question 260

At Northgate Enterprise Directory, the team supports multi-domain policy and cross-forest resource access and must validate trusts, replication and permissions without broadening privilege. The original incident is: Domain administrators see a revised GPO version number but branch clients still download an older script. The evidence is: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. 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: 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.
  3. Action: Repair the underlying DFSR SYSVOL replication health and verify both policy metadata and files before forcing clients to refresh. Evidence of success: Branch clients apply the updated file content and replication reports synchronized SYSVOL state.
  4. Action: Review inheritance and enforcement requirements, then coordinate the appropriately scoped policy adjustment with the owner. Evidence of success: Resultant Set of Policy displays the documented approved setting on a test computer without weakening other baselines.

Explanation

Correct Answer

C:

The documented issue at Northgate Enterprise Directory is that domain administrators see a revised GPO version number but branch clients still download an older script. The selected combined action and test is Action: Repair the underlying DFSR SYSVOL replication health and verify both policy metadata and files before forcing clients to refresh. Evidence of success: Branch clients apply the updated file content and replication reports synchronized SYSVOL state. Its verification aligns with the required outcome: Branch clients apply the updated file content and replication reports synchronized SYSVOL state.

Incorrect Answers

A:

That action and check pair is 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. It does not connect both parts to the actual Northgate Enterprise Directory clue: Domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated. The acceptance test needs to show that branch clients apply the updated file content and replication reports synchronized SYSVOL state.

B:

The paired proposal 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. For Northgate Enterprise Directory, it fails to establish an intervention and check for the documented issue, where domain administrators see a revised GPO version number but branch clients still download an older script. Successful closure requires that branch clients apply the updated file content and replication reports synchronized SYSVOL state.

D:

This offered change and proof, action: Review inheritance and enforcement requirements, then coordinate the appropriately scoped policy adjustment with the owner. Evidence of success: Resultant Set of Policy displays the documented approved setting on a test computer without weakening other baselines, would leave the Northgate Enterprise Directory case unverified. The actual recorded fault is that domain administrators see a revised GPO version number but branch clients still download an older script. A meaningful check requires that branch clients apply the updated file content and replication reports synchronized SYSVOL state.

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