Which two actions should be included in an authentication solution to meet the performance requirements?

To meet performance requirements for Azure Virtual Desktop (AVD) in new sites, you need to optimize authentication latency. Deploying domain controllers (DCs) for your on-premises Active Directory domain on Azure virtual machines in the new sites brings authentication services closer to the AVD session hosts, reducing network hops and improving login times. Creating an Active Directory site in each Azure region containing AVD session hosts allows you to configure site-specific settings, such as subnet associations, ensuring that session hosts primarily authenticate against the local Azure-based domain controllers. Joining all session hosts to Azure AD alone is insufficient if the primary identity source is on-premises Active Directory, as it doesn't address the latency to the on-premises domain. Creating an Azure AD DS managed domain is a separate identity solution and wouldn't integrate directly with an existing on-premises Active Directory for seamless authentication. Deploying read-only domain controllers (RODCs) can improve security but doesn't offer the same write capabilities or full performance benefits as a writable DC in a new site.