A domain controller DC1 (Windows Server 2019) experienced disk corruption. You have a recent Windows Server Backup System State backup for DC1. An OU named ‘Projects’ was deleted 40 days ago (Recycle Bin retention is 30 days). SYSVOL on DC1 is now empty, but other DCs have healthy SYSVOL. You must: 1) restore the ‘Projects’ OU and 2) recover SYSVOL on DC1 without impacting healthy DCs. What should you do on DC1? (Choose two)

To restore the 'Projects' OU, you must perform a System State restore from a backup taken before the OU deletion. This requires booting into Directory Services Restore Mode (DSRM) and using Windows Server Backup. After the System State restore, the 'Projects' OU will exist but will not be replicated to other DCs. To ensure it replicates, you must perform an authoritative restore of the OU using ntdsutil. For the empty SYSVOL on DC1, since other domain controllers have healthy SYSVOL, you should perform a non-authoritative SYSVOL recovery. This allows DC1 to rebuild its SYSVOL content by replicating from a healthy partner, preventing it from overwriting good SYSVOL data on other DCs. Performing an authoritative DFSR recovery for SYSVOL would make DC1 the source, potentially overwriting healthy SYSVOL data on other DCs with its empty SYSVOL. Using wbadmin to recover ntds.dit while online is not possible for a System State restore. Decommissioning and promoting a new DC is an extreme measure not required here.