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

Question 160

At Orion Secure Service Identities, the team supports Windows service accounts and Kerberos principals and must maintain auditable least privilege for services and computer accounts. The original incident is: An internal SQL endpoint fails integrated authentication after an administrator registers the same service principal name on two accounts. The evidence is: Forest-wide SPN duplicate queries identify the endpoint identifier on both a legacy service account and the active service identity. 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: Create a narrowly scoped managed service identity when supported and assign only the needed local and network rights. Evidence of success: The service starts with the new identity while a negative privileged action is denied and administrative memberships remain unchanged.
  2. Action: Authorize the exact host computer in the designated gMSA retrieval group and refresh its group token or Kerberos context appropriately. Evidence of success: The designated server retrieves the managed password and starts the service while unauthorized hosts remain denied.
  3. Action: Implement the approved cross-domain group nesting and verify both share and NTFS ACLs without granting rights directly to individual users. Evidence of success: An intended user gains only the documented share access while a nonmember in another domain remains blocked.
  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

D:

At Orion Secure Service Identities, the offered pair combines a relevant intervention with proof: 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 responds to the evidence that forest-wide SPN duplicate queries identify the endpoint identifier on both a legacy service account and the active service identity. A successful result should establish that kerberos service tickets resolve to the intended account and representative clients authenticate without duplicate-SPN errors.

Incorrect Answers

A:

The alternative combined step is Action: Create a narrowly scoped managed service identity when supported and assign only the needed local and network rights. Evidence of success: The service starts with the new identity while a negative privileged action is denied and administrative memberships remain unchanged. The relevant Orion Secure Service Identities evidence is that forest-wide SPN duplicate queries identify the endpoint identifier on both a legacy service account and the active service identity. Closure must validate that kerberos service tickets resolve to the intended account and representative clients authenticate without duplicate-SPN errors, rather than a different symptom.

B:

The paired remediation states Action: Authorize the exact host computer in the designated gMSA retrieval group and refresh its group token or Kerberos context appropriately. Evidence of success: The designated server retrieves the managed password and starts the service while unauthorized hosts remain denied. It does not test correction of the Orion Secure Service Identities condition: Forest-wide SPN duplicate queries identify the endpoint identifier on both a legacy service account and the active service identity. The outcome to verify is that kerberos service tickets resolve to the intended account and representative clients authenticate without duplicate-SPN errors.

C:

That action and check pair is Action: Implement the approved cross-domain group nesting and verify both share and NTFS ACLs without granting rights directly to individual users. Evidence of success: An intended user gains only the documented share access while a nonmember in another domain remains blocked. It does not connect both parts to the actual Orion Secure Service Identities clue: Forest-wide SPN duplicate queries identify the endpoint identifier on both a legacy service account and the active service identity. The acceptance test needs to show that kerberos service tickets resolve to the intended account and representative clients authenticate without duplicate-SPN errors.

Question 161

At Summit Group Policy Engineering, the team supports server and user policy deployment through domain GPOs and must maintain predictable resultant policy and authorized scoped changes. Confirmed original fault: Newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. Supporting diagnostic evidence: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. Create a narrowly scoped managed service identity when supported and assign only the needed local and network rights.
  2. Assign the intended pilot group to the selected staged method and validate fallback and rollback conditions.
  3. Review authorized identity synchronization scope, add the required OU to filtering and run a supported synchronization cycle.
  4. Correct the specific WMI targeting filter after checking supported Windows Server versions and the authorized policy audience.

Explanation

Correct Answer

C:

For Summit Group Policy Engineering, the decisive clue is that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The matching control change is to review authorized identity synchronization scope, add the required OU to filtering and run a supported synchronization cycle. Hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory. The correct result is that that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope.

Incorrect Answers

A:

The issue at Summit Group Policy Engineering is that newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. Acting to create a narrowly scoped managed service identity when supported and assign only the needed local and network rights would not correct the evidenced cause. The most relevant clue is that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy.

B:

That alternative would assign the intended pilot group to the selected staged method and validate fallback and rollback conditions. It misses the condition observed at Summit Group Policy Engineering: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The recommended correction addresses the observed condition directly.

D:

At Summit Group Policy Engineering, proposing to correct the specific WMI targeting filter after checking supported Windows Server versions and the authorized policy audience would not address the recorded evidence: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The case instead needs an intervention related to newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. Hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.

Question 162

At Summit Group Policy Engineering, the team supports server and user policy deployment through domain GPOs and must maintain predictable resultant policy and authorized scoped changes. A reported incident states: Newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. 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 host computer is absent from the gMSA retrieval permission group and the password retrieval test returns access denied.
  2. Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy.
  3. Agent diagnostic logs identify blocked outbound HTTPS to required Microsoft provisioning endpoints from the agent host.
  4. A WMI filter queries a client-operating-system product type and returns false on the servers.

Explanation

Correct Answer

B:

The reported issue at Summit Group Policy Engineering is that newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. The offered observation of entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy identifies the relevant fault rather than an unrelated symptom. Hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.

Incorrect Answers

A:

At Summit Group Policy Engineering, The alternative observation about the host computer is absent from the gMSA retrieval permission group and the password retrieval test returns access denied would not isolate the relevant problem. The diagnostic clue is that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. This is the clue that bears on newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync.

C:

This observation, agent diagnostic logs identify blocked outbound HTTPS to required Microsoft provisioning endpoints from the agent host, does not match the evidence in the Summit Group Policy Engineering record. Instead, the record shows that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. Hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.

D:

For Summit Group Policy Engineering, the proposed observation is that a WMI filter queries a client-operating-system product type and returns false on the servers. It would not distinguish the identified failure, where newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. The meaningful clue is that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy.

Question 163

At Summit Group Policy Engineering, the team supports server and user policy deployment through domain GPOs and must maintain predictable resultant policy and authorized scoped changes. Observed issue: Newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. Investigation found: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The proposed repair is: Review authorized identity synchronization scope, add the required OU to filtering and run a supported synchronization cycle. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. An intended user gains only the documented share access while a nonmember in another domain remains blocked.
  2. The intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope.
  3. Authorized pilot users use the expected method and nonpilot users continue through the documented existing flow.
  4. Resultant Set of Policy displays the documented approved setting on a test computer without weakening other baselines.

Explanation

Correct Answer

B:

The proof must establish that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope. That directly tests the observed condition at Summit Group Policy Engineering: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. Hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.

Incorrect Answers

A:

The alternative validation would show that an intended user gains only the documented share access while a nonmember in another domain remains blocked. For Summit Group Policy Engineering, that is insufficient to establish that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope. The original diagnostic finding is that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy.

C:

That verification is that authorized pilot users use the expected method and nonpilot users continue through the documented existing flow. The Summit Group Policy Engineering acceptance criterion is instead that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope. The recorded causal clue is that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy.

D:

This check suggests that resultant Set of Policy displays the documented approved setting on a test computer without weakening other baselines. It does not test the resolution criterion for Summit Group Policy Engineering, namely that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope. Hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.

Question 164

At Summit Group Policy Engineering, the team supports server and user policy deployment through domain GPOs and must maintain predictable resultant policy and authorized scoped changes. The administrator observes: Newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. The distinguishing clue is: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. 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. Hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.
  2. Machine accounts use changing shared secrets and restoring older system state can invalidate domain trust.
  3. Group Policy WMI filtering gates whether a GPO applies, independent of its OU link.
  4. Group Policy loopback processing changes how user configuration is selected for shared computer scenarios.

Explanation

Correct Answer

A:

The appropriate mechanism for Summit Group Policy Engineering is that hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory. This explains the recorded clue: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. It accounts for the reported failure, where newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync.

Incorrect Answers

B:

The alternative principle is that machine accounts use changing shared secrets and restoring older system state can invalidate domain trust. For Summit Group Policy Engineering, it does not explain why entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The applicable causal rule is that hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.

C:

This offered mechanism, group Policy WMI filtering gates whether a GPO applies, independent of its OU link, does not match the specific recorded failure at Summit Group Policy Engineering, where newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. The relevant principle is that hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.

D:

At Summit Group Policy Engineering, the reported clue is that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The principle of group Policy loopback processing changes how user configuration is selected for shared computer scenarios does not explain that finding. The appropriate explanation is that hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.

Question 165

At Summit Group Policy Engineering, the team supports server and user policy deployment through domain GPOs and must maintain predictable resultant policy and authorized scoped changes. The original incident is: Newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. The evidence is: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. 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: 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.
  2. 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.
  3. Action: Review authorized identity synchronization scope, add the required OU to filtering and run a supported synchronization cycle. Evidence of success: The intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope.
  4. Action: Update the preference item-level targeting condition to the approved group and independently verify share permissions. Evidence of success: The mapped drive appears for an authorized test user and stays absent for an unrelated user.

Explanation

Correct Answer

C:

At Summit Group Policy Engineering, the offered pair combines a relevant intervention with proof: Action: Review authorized identity synchronization scope, add the required OU to filtering and run a supported synchronization cycle. Evidence of success: The intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope. It responds to the evidence that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. A successful result should establish that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope.

Incorrect Answers

A:

The paired remediation states 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. It does not test correction of the Summit Group Policy Engineering condition: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The outcome to verify is that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope.

B:

That action and check pair is 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. It does not connect both parts to the actual Summit Group Policy Engineering clue: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The acceptance test needs to show that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope.

D:

At Summit Group Policy Engineering, the option couples action: Update the preference item-level targeting condition to the approved group and independently verify share permissions. Evidence of success: The mapped drive appears for an authorized test user and stays absent for an unrelated user. Its test does not independently demonstrate that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope. The deciding case evidence is that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy.

Question 166

At Orion Secure Service Identities, the team supports Windows service accounts and Kerberos principals and must maintain auditable least privilege for services and computer accounts. Confirmed original fault: Newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. Supporting diagnostic evidence: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. Restore approved proxy and outbound endpoint access for the provisioning agent while retaining minimum network access.
  2. Assign the intended pilot group to the selected staged method and validate fallback and rollback conditions.
  3. Repair the underlying DFSR SYSVOL replication health and verify both policy metadata and files before forcing clients to refresh.
  4. Review authorized identity synchronization scope, add the required OU to filtering and run a supported synchronization cycle.

Explanation

Correct Answer

D:

At Orion Secure Service Identities, entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The fitting correction is to review authorized identity synchronization scope, add the required OU to filtering and run a supported synchronization cycle. Hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory. The acceptance check is that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope.

Incorrect Answers

A:

That alternative would restore approved proxy and outbound endpoint access for the provisioning agent while retaining minimum network access. It misses the condition observed at Orion Secure Service Identities: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The recommended correction addresses the observed condition directly.

B:

The failure at Orion Secure Service Identities is that newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. That does not call for assign the intended pilot group to the selected staged method and validate fallback and rollback conditions. The case evidence instead establishes that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy.

C:

At Orion Secure Service Identities, proposing to repair the underlying DFSR SYSVOL replication health and verify both policy metadata and files before forcing clients to refresh would not address the recorded evidence: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The case instead needs an intervention related to newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. Hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.

Question 167

At Orion Secure Service Identities, the team supports Windows service accounts and Kerberos principals and must maintain auditable least privilege for services and computer accounts. A reported incident states: Newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. 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 server resolves external names but cannot locate LDAP and Kerberos SRV records for its own Active Directory domain.
  2. Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy.
  3. The RODC password replication policy excludes the branch staff group and the prepopulation report shows no permitted accounts.
  4. The service logon identity belongs to the privileged administrators group and the service starts with a stored long-lived password.

Explanation

Correct Answer

B:

At Orion Secure Service Identities, the distinguishing evidence is: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. It is directly connected to newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. Hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.

Incorrect Answers

A:

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 Orion Secure Service Identities is that newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. The decisive finding instead is that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy.

C:

For Orion Secure Service Identities, the proposed observation is that the RODC password replication policy excludes the branch staff group and the prepopulation report shows no permitted accounts. It would not distinguish the identified failure, where newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. The meaningful clue is that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy.

D:

The observation offered is that the service logon identity belongs to the privileged administrators group and the service starts with a stored long-lived password. It does not substantiate the reported Orion Secure Service Identities failure, where newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. The directly relevant diagnostic record is that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy.

Question 168

At Orion Secure Service Identities, the team supports Windows service accounts and Kerberos principals and must maintain auditable least privilege for services and computer accounts. Observed issue: Newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. Investigation found: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The proposed repair is: Review authorized identity synchronization scope, add the required OU to filtering and run a supported synchronization cycle. 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. The drift returns within the expected Kerberos tolerance and representative domain logons succeed without time skew errors.
  3. The intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope.
  4. A selected cross-forest user accesses an authorized resource and unrelated external names remain subject to normal DNS policy.

Explanation

Correct Answer

C:

The verification signal is that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope. It connects the proposed correction to the recorded diagnostic clue at Orion Secure Service Identities: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. Hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.

Incorrect Answers

A:

At Orion Secure Service Identities, 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 the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope. It must address the failure, where newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync.

B:

That verification is that the drift returns within the expected Kerberos tolerance and representative domain logons succeed without time skew errors. The Orion Secure Service Identities acceptance criterion is instead that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope. The recorded causal clue is that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy.

D:

The option would validate that a selected cross-forest user accesses an authorized resource and unrelated external names remain subject to normal DNS policy. That does not establish correction of the Orion Secure Service Identities issue, where newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. The meaningful proof is that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope.

Question 169

At Orion Secure Service Identities, the team supports Windows service accounts and Kerberos principals and must maintain auditable least privilege for services and computer accounts. The administrator observes: Newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. The distinguishing clue is: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. 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. Hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.
  2. AD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution.
  3. Inter-site replication latency follows topology, schedule and link policy rather than simply the health of individual domain controllers.
  4. Machine accounts use changing shared secrets and restoring older system state can invalidate domain trust.

Explanation

Correct Answer

A:

The selected principle is that hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory. It fits the Orion Secure Service Identities case because entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The reported failure is that newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync.

Incorrect Answers

B:

This offered mechanism, aD DS discovery depends on domain-aware DNS and appropriate service records rather than general internet name resolution, does not match the specific recorded failure at Orion Secure Service Identities, where newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. The relevant principle is that hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.

C:

At Orion Secure Service Identities, the reported clue is that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The principle of inter-site replication latency follows topology, schedule and link policy rather than simply the health of individual domain controllers does not explain that finding. The appropriate explanation is that hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.

D:

The alternate technical explanation says that machine accounts use changing shared secrets and restoring older system state can invalidate domain trust. It is not the mechanism identified by the Orion Secure Service Identities record: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. Hybrid identity synchronization intentionally applies scope and filtering before data flows to the cloud directory.

Question 170

At Orion Secure Service Identities, the team supports Windows service accounts and Kerberos principals and must maintain auditable least privilege for services and computer accounts. The original incident is: Newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. The evidence is: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. 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 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.
  2. Action: Review authorized identity synchronization scope, add the required OU to filtering and run a supported synchronization cycle. Evidence of success: The intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope.
  3. Action: Create a narrowly scoped managed service identity when supported and assign only the needed local and network rights. Evidence of success: The service starts with the new identity while a negative privileged action is denied and administrative memberships remain unchanged.
  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:

At Orion Secure Service Identities, the offered pair combines a relevant intervention with proof: Action: Review authorized identity synchronization scope, add the required OU to filtering and run a supported synchronization cycle. Evidence of success: The intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope. It responds to the evidence that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. A successful result should establish that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope.

Incorrect Answers

A:

That action and check 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 does not connect both parts to the actual Orion Secure Service Identities clue: Entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy. The acceptance test needs to show that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope.

C:

At Orion Secure Service Identities, the option couples action: Create a narrowly scoped managed service identity when supported and assign only the needed local and network rights. Evidence of success: The service starts with the new identity while a negative privileged action is denied and administrative memberships remain unchanged. Its test does not independently demonstrate that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope. The deciding case evidence is that entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy.

D:

This offered change and proof, 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, would leave the Orion Secure Service Identities case unverified. The actual recorded fault is that newly approved staff accounts exist in on-premises AD DS but never appear in Microsoft Entra ID after a directory sync. A meaningful check requires that the intended users appear with expected source-anchored identities and excluded privileged OUs stay out of scope.

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