100% Latest & Updated Microsoft AZ-801 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 660
Disk Manager shows a Healthy volume but an application receives NTFS corruption errors in Event Viewer. Which implementation step directly corrects the underlying problem?
- Retrieve approved recovery credentials and reestablish trusted boot protectors after hardware repair.
- Run supported filesystem diagnostics and repair with an approved backup/maintenance plan.
- Initialize/partition/format the disk as appropriate and assign the intended mount path.
- Restore the expected mount path and clustered resource reference.
Explanation
Correct Answer
B:A Healthy disk partition status is not sufficient to rule out filesystem metadata errors. A suitable corrective action is to run supported filesystem diagnostics and repair with an approved backup/maintenance plan.
Incorrect Answers
A:TPM measurement change can trigger recovery independent of filesystem health. However, a Healthy disk partition status is not sufficient to rule out filesystem metadata errors.
C:Attaching block storage does not automatically create a usable Windows filesystem volume. In this situation, a Healthy disk partition status is not sufficient to rule out filesystem metadata errors.
D:Application file paths depend on mounted namespace, not only disk health state. However, a Healthy disk partition status is not sufficient to rule out filesystem metadata errors.
Question 661
A user created on DC1 does not appear on DC2 after the expected convergence window. Which configuration or recovery action best matches this evidence?
- Inspect naming context replication and GC participation/refresh before asserting all replicas match.
- Compare partition replication status, last successful sync and topology scheduling.
- Run repadmin /showrepl or /replsummary and inspect the failing naming context/source partner.
- Repair AD-integrated DNS registration/replication for that domain controller.
Explanation
Correct Answer
C:AD DS replication status identifies which directory partition and connection failed. The targeted remedy is to run repadmin /showrepl or /replsummary and inspect the failing naming context/source partner.
Incorrect Answers
A:Successful replication of one partition or host does not automatically prove every GC view is current. Here, AD DS replication status identifies which directory partition and connection failed.
B:Directory values converge through actual successful partition replication, not mere name lookup. In this situation, AD DS replication status identifies which directory partition and connection failed.
D:Replication partners must resolve the target DC locator records before opening RPC connections. Here, AD DS replication status identifies which directory partition and connection failed.
Question 662
A replication error reports DNS lookup failure for one DC's GUID-based CNAME record. What should the administrator change first to correct this specific issue?
- Refresh only client-facing DC service SRV records while leaving the reported replication GUID CNAME absent from the _msdcs zone.
- Restore the required AD DS RPC endpoint/connectivity path within approved network rules.
- Investigate and remove lingering objects through supported tools before normal replication.
- Repair AD-integrated DNS registration/replication for that domain controller.
Explanation
Correct Answer
D:Repair AD-integrated DNS registration/replication for that domain controller. This addresses the condition because replication partners must resolve the target DC locator records before opening RPC connections.
Incorrect Answers
A:Kerberos and LDAP SRV discovery does not replace the missing DSA GUID CNAME that replication partners need. Repair the missing alias and its AD-integrated DNS registration.
B:Name resolution does not prove that dynamic RPC replication transport is reachable. However, replication partners must resolve the target DC locator records before opening RPC connections.
C:An out-of-date DC may hold deleted objects whose tombstones no longer exist elsewhere. Here, replication partners must resolve the target DC locator records before opening RPC connections.
Question 663
A repadmin failure shows RPC Server Unavailable after a firewall change between two sites, although DNS succeeds. What would be the most defensible next action based on the observed symptoms?
- Restore the required AD DS RPC endpoint/connectivity path within approved network rules.
- Repair AD-integrated DNS registration/replication for that domain controller.
- Correct subnet-to-site and site-link topology mapping for the new network.
- Inspect naming context replication and GC participation/refresh before asserting all replicas match.
Explanation
Correct Answer
A:Name resolution does not prove that dynamic RPC replication transport is reachable. For that reason, restore the required AD DS RPC endpoint/connectivity path within approved network rules.
Incorrect Answers
B:Replication partners must resolve the target DC locator records before opening RPC connections. Here, name resolution does not prove that dynamic RPC replication transport is reachable.
C:AD replication and client DC selection depend on site/subnet relationships. In this situation, name resolution does not prove that dynamic RPC replication transport is reachable.
D:Successful replication of one partition or host does not automatically prove every GC view is current. However, name resolution does not prove that dynamic RPC replication transport is reachable.
Question 664
An AD replication issue appears only between branch sites after the site's IP subnet was moved but AD Sites and Services was never updated. Which administrative change most directly resolves the documented failure?
- Review site-link schedules/costs and required replication frequency for the new topology.
- Correct subnet-to-site and site-link topology mapping for the new network.
- Compare partition replication status, last successful sync and topology scheduling.
- Restore the required AD DS RPC endpoint/connectivity path within approved network rules.
Explanation
Correct Answer
B:Correct subnet-to-site and site-link topology mapping for the new network. The underlying technical reason is that aD replication and client DC selection depend on site/subnet relationships.
Incorrect Answers
A:Intersite replication behavior depends on site-link scheduling and topology design. Here, AD replication and client DC selection depend on site/subnet relationships.
C:Directory values converge through actual successful partition replication, not mere name lookup. However, AD replication and client DC selection depend on site/subnet relationships.
D:Name resolution does not prove that dynamic RPC replication transport is reachable. Here, AD replication and client DC selection depend on site/subnet relationships.
Question 665
One DC has been offline past tombstone lifetime and now reports lingering object protection events when it reconnects. Which implementation step directly corrects the underlying problem?
- Keep protection enabled and remove stale objects with controlled remediation.
- Repair AD-integrated DNS registration/replication for that domain controller.
- Investigate and remove lingering objects through supported tools before normal replication.
- Inspect naming context replication and GC participation/refresh before asserting all replicas match.
Explanation
Correct Answer
C:An out-of-date DC may hold deleted objects whose tombstones no longer exist elsewhere. A suitable corrective action is to investigate and remove lingering objects through supported tools before normal replication.
Incorrect Answers
A:Disabling the guard can reintroduce logically deleted objects into the healthy forest. In this situation, an out-of-date DC may hold deleted objects whose tombstones no longer exist elsewhere.
B:Replication partners must resolve the target DC locator records before opening RPC connections. However, an out-of-date DC may hold deleted objects whose tombstones no longer exist elsewhere.
D:Successful replication of one partition or host does not automatically prove every GC view is current. In this situation, an out-of-date DC may hold deleted objects whose tombstones no longer exist elsewhere.
Question 666
An administrator attempts to force replication by disabling strict replication consistency on a DC reporting lingering objects. Which response addresses the identified root cause without weakening other controls?
- Investigate and remove lingering objects through supported tools before normal replication.
- Repair AD-integrated DNS registration/replication for that domain controller.
- Correct subnet-to-site and site-link topology mapping for the new network.
- Keep protection enabled and remove stale objects with controlled remediation.
Explanation
Correct Answer
D:Disabling the guard can reintroduce logically deleted objects into the healthy forest. The targeted remedy is to keep protection enabled and remove stale objects with controlled remediation.
Incorrect Answers
A:An out-of-date DC may hold deleted objects whose tombstones no longer exist elsewhere. However, disabling the guard can reintroduce logically deleted objects into the healthy forest.
B:Replication partners must resolve the target DC locator records before opening RPC connections. Here, disabling the guard can reintroduce logically deleted objects into the healthy forest.
C:AD replication and client DC selection depend on site/subnet relationships. In this situation, disabling the guard can reintroduce logically deleted objects into the healthy forest.
Question 667
Two domain controllers disagree about a user's group membership despite apparently healthy DNS, and one has not replicated for days. Which supported action should be taken for this reported condition?
- Compare partition replication status, last successful sync and topology scheduling.
- Review site-link schedules/costs and required replication frequency for the new topology.
- Correct subnet-to-site and site-link topology mapping for the new network.
- Repair AD-integrated DNS registration/replication for that domain controller.
Explanation
Correct Answer
A:Compare partition replication status, last successful sync and topology scheduling. This addresses the condition because directory values converge through actual successful partition replication, not mere name lookup.
Incorrect Answers
B:Intersite replication behavior depends on site-link scheduling and topology design. In this situation, directory values converge through actual successful partition replication, not mere name lookup.
C:AD replication and client DC selection depend on site/subnet relationships. However, directory values converge through actual successful partition replication, not mere name lookup.
D:Replication partners must resolve the target DC locator records before opening RPC connections. Here, directory values converge through actual successful partition replication, not mere name lookup.
Question 668
A PDC emulator moves to another site, and replication failures increase because site links remain scheduled for rare overnight windows. Which supported action should be taken for this reported condition?
- Correct subnet-to-site and site-link topology mapping for the new network.
- Review site-link schedules/costs and required replication frequency for the new topology.
- Compare partition replication status, last successful sync and topology scheduling.
- Repair AD-integrated DNS registration/replication for that domain controller.
Explanation
Correct Answer
B:Intersite replication behavior depends on site-link scheduling and topology design. For that reason, review site-link schedules/costs and required replication frequency for the new topology.
Incorrect Answers
A:AD replication and client DC selection depend on site/subnet relationships. In this situation, intersite replication behavior depends on site-link scheduling and topology design.
C:Directory values converge through actual successful partition replication, not mere name lookup. Here, intersite replication behavior depends on site-link scheduling and topology design.
D:Replication partners must resolve the target DC locator records before opening RPC connections. In this situation, intersite replication behavior depends on site-link scheduling and topology design.
Question 669
A new DC registers its DNS A record but fails to publish the necessary LDAP/Kerberos SRV records for DC locator. Which Windows Server or Azure operation best addresses the reported fault?
- Repair AD-integrated DNS registration/replication for that domain controller.
- Investigate and remove lingering objects through supported tools before normal replication.
- Repair Netlogon DNS registrations and verify SRV discovery from clients.
- Keep protection enabled and remove stale objects with controlled remediation.
Explanation
Correct Answer
C:Repair Netlogon DNS registrations and verify SRV discovery from clients. The underlying technical reason is that domain discovery relies on DC service records, not only the host's ordinary A record.
Incorrect Answers
A:Replication partners must resolve the target DC locator records before opening RPC connections. However, domain discovery relies on DC service records, not only the host's ordinary A record.
B:An out-of-date DC may hold deleted objects whose tombstones no longer exist elsewhere. Here, domain discovery relies on DC service records, not only the host's ordinary A record.
D:Disabling the guard can reintroduce logically deleted objects into the healthy forest. However, domain discovery relies on DC service records, not only the host's ordinary A record.
Question 670
A directory admin reports that repadmin /syncall returns success but one application OU still shows unexpected differences due to stale Global Catalog results. Which response addresses the identified root cause without weakening other controls?
- Run repadmin /showrepl or /replsummary and inspect the failing naming context/source partner.
- Restore the required AD DS RPC endpoint/connectivity path within approved network rules.
- Repair AD-integrated DNS registration/replication for that domain controller.
- Inspect naming context replication and GC participation/refresh before asserting all replicas match.
Explanation
Correct Answer
D:Successful replication of one partition or host does not automatically prove every GC view is current. A suitable corrective action is to inspect naming context replication and GC participation/refresh before asserting all replicas match.
Incorrect Answers
A:AD DS replication status identifies which directory partition and connection failed. Here, successful replication of one partition or host does not automatically prove every GC view is current.
B:Name resolution does not prove that dynamic RPC replication transport is reachable. In this situation, successful replication of one partition or host does not automatically prove every GC view is current.
C:Replication partners must resolve the target DC locator records before opening RPC connections. However, successful replication of one partition or host does not automatically prove every GC view is current.
Configuring Windows Server Hybrid Advanced Services (AZ-801) Practice Tests