Knowledge Check

1.

Repadmin reports an inbound failure for DC=contoso,DC=com on Brisbane\BNE-DC-01 from Seattle\SEA-DC-01. Which interpretation is correct?

SEA-DC-01 is the destination and pulls the domain partition from BNE-DC-01.

BNE-DC-01 and SEA-DC-01 both originate the same inbound replication attempt.

BNE-DC-01 is the destination and pulls the domain partition from SEA-DC-01.

2.

Repadmin reports error 1722 for the Configuration and Schema naming contexts, then error 1256 for the Domain, DomainDnsZones, and ForestDnsZones naming contexts from the same source. Which status should drive the first investigation?

Error 1722, because the Configuration and Schema remote procedure call bind failures caused cancellation of the remaining three naming contexts.

Error 1256, because each of the three canceled naming contexts requires a separate repair.

Status 8477, because posted replication requests replace remote procedure call failures.

3.

Name resolution for SEA-DC-01.contoso.com returns a retired address. TCP 135 fails through the name but succeeds to the current address. Which response best fits the evidence?

Open every dynamic remote procedure call port on each firewall, then force forest-wide synchronization.

Create a manual connection object from the destination to the source, then recalculate the topology.

Correct only the demonstrated stale A record on the authoritative server serving BNE-DC-01, verify the intended registration settings, then repeat the same tests.

4.

Error 8452 appears immediately after a site-link change. The destination DSA's current view no longer lists the named source as valid, while the DSA/DC that initiated the request still has stale topology or partition knowledge. Which action is safest?

Create permanent manual connection objects that reproduce the stale DSA/DC view.

Allow topology knowledge to converge and test a valid source, destination, and directory partition directly.

Run broad synchronization until every reported relationship succeeds.

5.

Directory Service event 2095 appears and the domain controller is marked nonwritable, although Repadmin reports no failures. Which response is appropriate?

Clear the writable-state flag and force synchronization from every partner before collecting logs.

Preserve evidence, isolate the affected domain controller when guidance requires it, and escalate supported recovery.

Manually attach and boot an old copied virtual hard disk, or revert on a platform that doesn't expose virtual machine Generation ID.

6.

Which event artifact best corroborates the Repadmin evidence for the failed inbound replication relationship?

A Directory Service Event ID 1925, task category Active Directory Domain Services / Knowledge Consistency Checker, logged on BNE-DC-01 at 2026-07-20 07:11:32 +10:00, for DC=contoso,DC=com, whose Source directory service is CN=NTDS Settings,CN=SEA-DC-01,CN=Servers,CN=Seattle,CN=Sites,CN=Configuration,DC=contoso,DC=com, whose Source domain controller address is the SEA DSA GUID CNAME, and whose additional status is 1256.

A DNS client event from an administrative workstation that contains only the retired IP address.

A source-logged event on SEA-DC-01 that doesn't identify a destination, directory partition, or timestamp.

Check your knowledge

Feedback