Pass Microsoft AZ-800 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
Microsoft AZ-800 Practice Test 10
Question 90
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: Users from a trusted forest cannot authenticate to a resource forest even though the administrators created a trust relationship. The evidence is: Conditional name-resolution tests cannot resolve the other forest's domain controller locator records and the trust validation reports name discovery errors. 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?
Explanation
Correct Answer
The case at Northgate Enterprise Directory requires both correction and evidence for the same fault. The proposed pair is Action: Configure approved conditional forwarders or equivalent trusted DNS resolution and validate the precise trust direction and authentication rules. Evidence of success: A selected cross-forest user accesses an authorized resource and unrelated external names remain subject to normal DNS policy. It addresses the finding that conditional name-resolution tests cannot resolve the other forest's domain controller locator records and the trust validation reports name discovery errors and tests whether a selected cross-forest user accesses an authorized resource and unrelated external names remain subject to normal DNS policy.
Incorrect Answers
At Northgate Enterprise Directory, the option couples 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. Its test does not independently demonstrate that a selected cross-forest user accesses an authorized resource and unrelated external names remain subject to normal DNS policy. The deciding case evidence is that conditional name-resolution tests cannot resolve the other forest's domain controller locator records and the trust validation reports name discovery errors.
This offered change and proof, action: Assign the correct network prefix to the approved AD site and validate site topology and DNS locator results. Evidence of success: New client site discovery selects the local site and authentication latency decreases without altering unrelated sites, would leave the Northgate Enterprise Directory case unverified. The actual recorded fault is that users from a trusted forest cannot authenticate to a resource forest even though the administrators created a trust relationship. A meaningful check requires that a selected cross-forest user accesses an authorized resource and unrelated external names remain subject to normal DNS policy.
The paired remediation states 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 test correction of the Northgate Enterprise Directory condition: Conditional name-resolution tests cannot resolve the other forest's domain controller locator records and the trust validation reports name discovery errors. The outcome to verify is that a selected cross-forest user accesses an authorized resource and unrelated external names remain subject to normal DNS policy.
Question 91
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: A domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. Supporting diagnostic evidence: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?
Explanation
Correct Answer
The available evidence is that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. Northgate Enterprise Directory needs to restore the narrowly required RPC and related AD replication paths between the designated controllers and reassess replication health. Ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication. Confirmation would be that a newly created test object and group membership change replicate without unresolved failure events.
Incorrect Answers
That alternative would review the approved credential exposure risk, permit only designated branch principals and prepopulate their secrets using supported RODC controls. For Northgate Enterprise Directory, that does not follow the diagnostic finding that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. The relevant principle is that ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication.
Proposing to create a narrowly scoped managed service identity when supported and assign only the needed local and network rights does not fit the evidence at Northgate Enterprise Directory: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. That would not resolve the original failure: a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change.
The issue at Northgate Enterprise Directory is that a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. Acting to authorize the exact host computer in the designated gMSA retrieval group and refresh its group token or Kerberos context appropriately would not correct the evidenced cause. The most relevant clue is that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass.
Question 92
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: A domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. 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?
Explanation
Correct Answer
The relevant observation is that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. It is directly relevant to Northgate Enterprise Directory because a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. Ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication.
Incorrect Answers
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 Northgate Enterprise Directory failure, where a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. The directly relevant diagnostic record is that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass.
At Northgate Enterprise Directory, The alternative observation about entra Connect synchronization scope excludes the newly created organizational unit, although the synchronization scheduler is healthy would not isolate the relevant problem. The diagnostic clue is that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. This is the clue that bears on a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change.
An unrelated diagnosis would involve: Synchronization logs show an immutable source anchor mismatch and two cloud objects share similar sign-in attributes. The incident at Northgate Enterprise Directory is that a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. The decisive finding instead is that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass.
Question 93
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: A domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. Investigation found: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. The proposed repair is: Restore the narrowly required RPC and related AD replication paths between the designated controllers and reassess replication health. Which independently observable result best verifies resolution of the stated Windows Server problem?
Explanation
Correct Answer
The relevant acceptance result for Northgate Enterprise Directory is that a newly created test object and group membership change replicate without unresolved failure events. It tests the outcome of the change against the fault shown by repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. Ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication.
Incorrect Answers
The option would validate that a healthy domain controller owns the role, RID allocation resumes and the failed former owner cannot be reintroduced without remediation. That does not establish correction of the Northgate Enterprise Directory issue, where a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. The meaningful proof is that a newly created test object and group membership change replicate without unresolved failure events.
The alternative validation would show that replication diagnostics complete between the relevant site partners and the VM remains reachable under restricted administration rules. For Northgate Enterprise Directory, that is insufficient to establish that a newly created test object and group membership change replicate without unresolved failure events. The original diagnostic finding is that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass.
At Northgate Enterprise Directory, a test showing that the application uses a supported directory design without attempts to seize managed-domain controller privileges would not confirm the needed outcome. The check must demonstrate that a newly created test object and group membership change replicate without unresolved failure events. It must address the failure, where a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change.
Question 94
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: A domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. The distinguishing clue is: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. The team wants a causal explanation, not a generic remedy. Which Windows Server, identity, network, compute or storage principle best explains the identified failure?
Explanation
Correct Answer
The appropriate mechanism for Northgate Enterprise Directory is that ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication. This explains the recorded clue: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. It accounts for the reported failure, where a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change.
Incorrect Answers
The alternate technical explanation says that role seizure is an exceptional recovery action that requires confirming permanent owner loss and avoiding simultaneous role owners. It is not the mechanism identified by the Northgate Enterprise Directory record: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. Ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication.
The case at Northgate Enterprise Directory is that a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. The offered principle, active Directory site selection depends on maintained subnet-to-site mappings as well as domain controller availability, would not explain this observed failure. The relevant mechanism is that ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication.
The alternative principle is that gPP item-level targeting can block individual preference actions even when the enclosing GPO is applied. For Northgate Enterprise Directory, it does not explain why repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. The applicable causal rule is that ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication.
Question 95
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: A domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. The evidence is: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. 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?
Explanation
Correct Answer
This proposed change-and-check pair is tied to the Northgate Enterprise Directory fault: Action: Restore the narrowly required RPC and related AD replication paths between the designated controllers and reassess replication health. Evidence of success: A newly created test object and group membership change replicate without unresolved failure events. The diagnostic basis is that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. The outcome must show that a newly created test object and group membership change replicate without unresolved failure events.
Incorrect Answers
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 Northgate Enterprise Directory case unverified. The actual recorded fault is that a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. A meaningful check requires that a newly created test object and group membership change replicate without unresolved failure events.
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 Northgate Enterprise Directory evidence is that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. Closure must validate that a newly created test object and group membership change replicate without unresolved failure events, rather than a different symptom.
The paired remediation states 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 test correction of the Northgate Enterprise Directory condition: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. The outcome to verify is that a newly created test object and group membership change replicate without unresolved failure events.
Question 96
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: A domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. Supporting diagnostic evidence: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?
Explanation
Correct Answer
The underlying problem at Orion Secure Service Identities is that a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. The recommended response is to restore the narrowly required RPC and related AD replication paths between the designated controllers and reassess replication health. Verify that a newly created test object and group membership change replicate without unresolved failure events.
Incorrect Answers
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 Orion Secure Service Identities: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. That would not resolve the original failure: a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change.
That alternative would authorize the exact host computer in the designated gMSA retrieval group and refresh its group token or Kerberos context appropriately. It misses the condition observed at Orion Secure Service Identities: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. The recommended correction addresses the observed condition directly.
The failure at Orion Secure Service Identities is that a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. That does not call for correct the specific WMI targeting filter after checking supported Windows Server versions and the authorized policy audience. The case evidence instead establishes that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass.
Question 97
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: A domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. 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?
Explanation
Correct Answer
The reported issue at Orion Secure Service Identities is that a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. The offered observation of repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass identifies the relevant fault rather than an unrelated symptom. Ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication.
Incorrect Answers
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 Orion Secure Service Identities case, the actual distinguishing finding is that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. Ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication.
At Orion Secure Service Identities, The alternative observation about agent diagnostic logs identify blocked outbound HTTPS to required Microsoft provisioning endpoints from the agent host would not isolate the relevant problem. The diagnostic clue is that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. This is the clue that bears on a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change.
This observation, domain controller SYSVOL file versions differ between sites while directory GPO metadata has replicated, does not match the evidence in the Orion Secure Service Identities record. Instead, the record shows that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. Ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication.
Question 98
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: A domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. Investigation found: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. The proposed repair is: Restore the narrowly required RPC and related AD replication paths between the designated controllers and reassess replication health. Which independently observable result best verifies resolution of the stated Windows Server problem?
Explanation
Correct Answer
The relevant acceptance result for Orion Secure Service Identities is that a newly created test object and group membership change replicate without unresolved failure events. It tests the outcome of the change against the fault shown by repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. Ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication.
Incorrect Answers
The alternative validation would show that replication diagnostics complete between the relevant site partners and the VM remains reachable under restricted administration rules. For Orion Secure Service Identities, that is insufficient to establish that a newly created test object and group membership change replicate without unresolved failure events. The original diagnostic finding is that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass.
At Orion Secure Service Identities, a test showing that sYSVOL and NETLOGON shares become available and Group Policy assets match an independently checked healthy controller would not confirm the needed outcome. The check must demonstrate that a newly created test object and group membership change replicate without unresolved failure events. It must address the failure, where a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change.
That verification is that branch clients apply the updated file content and replication reports synchronized SYSVOL state. The Orion Secure Service Identities acceptance criterion is instead that a newly created test object and group membership change replicate without unresolved failure events. The recorded causal clue is that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass.
Question 99
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: A domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. The distinguishing clue is: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. The team wants a causal explanation, not a generic remedy. Which Windows Server, identity, network, compute or storage principle best explains the identified failure?
Explanation
Correct Answer
The selected principle is that ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication. It fits the Orion Secure Service Identities case because repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. The reported failure is that a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change.
Incorrect Answers
The case at Orion Secure Service Identities is that a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. The offered principle, hybrid domain controllers need explicit reliable routed identity traffic in addition to basic VM administrator access, would not explain this observed failure. The relevant mechanism is that ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication.
The alternative rule states that cross-forest trust scope and per-resource authorization must be designed together to prevent unintended reachability. It does not account for the Orion Secure Service Identities evidence: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. The case turns on the mechanism that ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication.
This offered mechanism, hybrid authentication rollout must be explicitly scoped and checked by observed sign-in method, not by enabling a global setting alone, does not match the specific recorded failure at Orion Secure Service Identities, where a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. The relevant principle is that ping success is insufficient to prove the dynamic protocol connectivity required by Active Directory replication.
Question 100
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: A domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. The evidence is: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. 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?
Explanation
Correct Answer
The case at Orion Secure Service Identities requires both correction and evidence for the same fault. The proposed pair is Action: Restore the narrowly required RPC and related AD replication paths between the designated controllers and reassess replication health. Evidence of success: A newly created test object and group membership change replicate without unresolved failure events. It addresses the finding that repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass and tests whether a newly created test object and group membership change replicate without unresolved failure events.
Incorrect Answers
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 Orion Secure Service Identities condition: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. The outcome to verify is that a newly created test object and group membership change replicate without unresolved failure events.
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 Orion Secure Service Identities clue: Repadmin shows a persistent replication partner failure with a specific RPC or dynamic port error while ordinary ICMP checks pass. The acceptance test needs to show that a newly created test object and group membership change replicate without unresolved failure events.
The paired proposal is Action: Assign the intended pilot group to the selected staged method and validate fallback and rollback conditions. Evidence of success: Authorized pilot users use the expected method and nonpilot users continue through the documented existing flow. For Orion Secure Service Identities, it fails to establish an intervention and check for the documented issue, where a domain appears reachable yet group changes stop arriving on one remote domain controller after a firewall change. Successful closure requires that a newly created test object and group membership change replicate without unresolved failure events.
Administering Windows Server Hybrid Core Infrastructure (AZ-800) Practice Tests
- Microsoft AZ-800 Practice Test 8 - 10 Questions (Last Reviewed 10-Nov-2026)
- Microsoft AZ-800 Practice Test 9 - 10 Questions (Last Reviewed 09-Nov-2026)
- Microsoft AZ-800 Practice Test 10 - 10 Questions (Last Reviewed 08-Nov-2026)
- Microsoft AZ-800 Practice Test 11 - 10 Questions (Last Reviewed 07-Nov-2026)
- Microsoft AZ-800 Practice Test 12 - 10 Questions (Last Reviewed 06-Nov-2026)
