In Windows NT domain administration, which action is Server Manager specifically used for among the following choices?

Introduction / Context:
Windows NT networks predate Active Directory and used Primary/Backup Domain Controllers (PDC/BDCs) with SAM database replication. Server Manager was the central MMC-style tool of its era for managing servers, shares, services, and certain domain operations. Knowing what Server Manager could and could not do is a common certification topic.

Given Data / Assumptions:

• Environment: Windows NT 4.0-era domains.
• Server Manager provided management of domain controllers and could trigger replication.
• Some tasks listed belong to other tools or later technologies.

Concept / Approach:
Server Manager could force synchronization of the SAM database between the PDC and BDCs. It did not directly control OS shutdown/restart (that was done locally or via different utilities), and it did not “demote” a PDC in the AD sense—rather, you could promote a BDC to PDC, which implicitly made the old PDC a BDC. Auditing configuration was handled in User Manager for Domains and Local Security Policy. Active Directory forests did not exist in NT 4.0.

Step-by-Step Solution:

Verification / Alternative check:
Contemporary documentation shows Server Manager’s ability to manage trusts, shares, and domain controller roles, including triggering replication, aligning with the selected option.

Why Other Options Are Wrong:

• PDC demotion: not an explicit “demote” action; role change occurred via promoting a BDC.
• Shutdown/restart: not Server Manager’s primary function.
• Enable auditing: done via User Manager for Domains/Policies.
• Active Directory forests: not applicable to NT domains.

Common Pitfalls:
Transposing Windows 2000+ AD concepts back onto NT; assuming Server Manager handled all OS-level operations.

Final Answer:
Synchronize the domain (force replication between PDC and BDCs)