Microsoft Azure Architect Design (AZ-304) Practice Test

Why is password hash synchronization preferred for enabling SSO in Azure AD environments?

1. It requires users to frequently change their passwords

2. It simplifies the process by not needing on-premises components

3. It leverages on-premises AD group policies

4. It offers real-time synchronization of passwords

The correct answer is: It simplifies the process by not needing on-premises components

Password hash synchronization is preferred for enabling Single Sign-On (SSO) in Azure AD environments largely because it simplifies the process by eliminating the need for on-premises components. This approach allows organizations to maintain a unified identity for users across both cloud and on-premises applications without the complexities associated with traditional federated authentication methods. By synchronizing password hashes from on-premises Active Directory to Azure AD, organizations can provide users with seamless access to resources without requiring the on-premises infrastructure to be continuously involved in the authentication process. This reduces management overhead and increases reliability, as there’s less dependency on specific connections or the health of on-premises servers. Users can authenticate directly with Azure AD, which is especially beneficial in cloud-centric or hybrid environments. This method is also easier to configure and maintain as it does not involve setting up additional components like ADFS or Web Application Proxy, which are typically necessary for federation scenarios. By simplifying the authentication workflow, organizations can improve their operational efficiency and reduce potential points of failure in the identity management process.