Your company has a hub-and-spoke topology with a central WSUS server (WSUS01) in the hub and a WSUS server (WSUS02) in a branch office. Branch clients must download updates from WSUS02, but all approvals and computer group structure must be controlled only from WSUS01 and mirrored on WSUS02. You also want WSUS02 to sync on a schedule without branch admin involvement. Which two actions should you take?

Configuring WSUS02 as a replica of WSUS01 ensures that all approvals, computer group structures, and update metadata are inherited from WSUS01. This meets the requirement for centralized control from WSUS01 and mirroring on WSUS02. Approving updates on WSUS01 and managing target groups there ensures that all update decisions originate from the central server, which is then replicated to WSUS02. This setup also allows WSUS02 to synchronize on a schedule without local intervention, as it simply mirrors WSUS01. Approving updates on WSUS02 is incorrect because it contradicts the requirement for centralized approval from WSUS01. Configuring WSUS02 as an autonomous downstream server is incorrect because autonomous servers allow local administration and approvals, which goes against the centralized control requirement. Enabling client-side targeting on WSUS01 is incorrect because it shifts group assignment control to the clients, not the central WSUS01 server.