When changes are made to a computer in an OU, how will this change be replicated to other domain controllers?

When a change is made to a computer in an Organizational Unit (OU), the correct mechanism of replication involves the domain controller (DC) where the change was made notifying its replication partners. This process is initiated by the originating DC which sends out a notification to its partner DCs that a change has occurred. The partner DCs, upon receiving this notification, will then initiate a request for the updated data, ensuring that they have the most current information.

This model of replication is efficient because it allows for changes to propagate throughout the domain without the need for immediate simultaneous updates to all DCs. Instead, each partner DC handles replication based on the notifications it receives, following a system that balances timely updates with resource management.

Other options describe incorrect scenarios. For example, stating that changes replicate instantly to all domain controllers does not reflect the actual process, as there can be slight delays until the notification and subsequent requests are processed. The idea of replication occurring only during scheduled maintenance or on a weekly basis is not accurate as well; replication is designed to be dynamic and request-driven rather than limited to specific times or frequencies. This flexibility in the replication process allows for a more responsive and up-to-date directory service.