AZ-802 Deploy and Manage AD DS Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Wait for the Knowledge Consistency Checker (KCC) to automatically move the role.

  Why it's wrong here

  The KCC is responsible for managing the replication topology and generating connection objects between domain controllers, but it does not have the authority or functionality to move FSMO roles. FSMO roles are static assignments that require manual intervention by an administrator to transfer or seize when a failure occurs.

• ✗

  Perform a graceful transfer of the RID Master role using ADUC.

  Why it's wrong here

  A graceful transfer requires the original role holder to be online and functional so that it can synchronize its remaining data before relinquishing the role. Since the original RID Master has suffered a catastrophic hardware failure and is offline, a graceful transfer is impossible, and an administrative seizure is the only viable path.

• ✓

  Seize the RID Master role using the 'Move-ADDirectoryServerOperationMasterRole' cmdlet.

  Why this is correct

  Seizing the role is the correct action when the original holder is permanently unavailable. Using the -Force parameter with the PowerShell cmdlet allows a healthy domain controller to take ownership of the RID Master role immediately, enabling the allocation of new RID pools and restoring the ability to create user accounts.

• ✗

  Reinstall Active Directory on the failed server using the same name.

  Why it's wrong here

  Reinstalling a server with the same name does not automatically restore its FSMO roles and can lead to significant metadata cleanup issues if the old computer object is not properly handled. Seizing the role to an existing, healthy domain controller is a much faster and safer way to restore domain services.