You run one Azure AD Connect server, two AD FS servers, and two Web Application Proxy (WAP) servers. You need to be alerted if directory synchronization stops or error rates spike, and you want to view AD FS usage analytics (for example, sign-in success rates and top apps) in the Azure portal. What should you do? (Choose two)

Installing and registering the Azure AD Connect Health for Sync agent on the Azure AD Connect server enables monitoring of directory synchronization, providing alerts for stopped syncs or error spikes. This directly addresses the requirement for sync monitoring. Installing Azure AD Connect Health agents on both AD FS servers and both WAP servers allows for collecting AD FS usage analytics, such as sign-in success rates and top applications, which can then be viewed in the Azure portal. This fulfills the requirement for AD FS usage analytics. Enabling Azure AD sign-in diagnostic settings is for Azure AD sign-ins, not specifically AD FS usage analytics. Creating an Azure Monitor alert on the Subscription Activity Log monitors Azure service health, not directory sync or AD FS performance. Enabling Staging mode on a second Azure AD Connect server is for high availability or testing, not for collecting sync metrics for alerting.