Solaris Heavy Industries is designing a hybrid identity and collaboration solution. The company has an on-premises Active Directory Domain Services (AD DS) forest named solaris.local that contains 12,500 user accounts. They recently acquired a subsidiary that uses an independent Microsoft Entra ID tenant named aurora-aviation.onmicrosoft.com.
You need to design a solution that meets the following requirements:
- Users in solaris.local must be synchronized to the primary Microsoft Entra tenant (solaris-heavy.onmicrosoft.com) and must be able to authenticate to Azure resources even if the on-premises network link to Azure is temporarily offline.
- On-premises users must be able to change their passwords using Microsoft Entra Self-Service Password Reset (SSPR), and the changes must update the on-premises AD DS immediately.
- Guest users from aurora-aviation.onmicrosoft.com must be allowed to access shared resources in solaris-heavy.onmicrosoft.com securely.
- You must minimize administrative overhead and avoid hosting extra on-premises federation servers.
Which two components should you include in the hybrid identity design? (Select two.)
- Microsoft Entra Connect Sync with Password Hash Synchronization (PHS) and password writeback enabledAnswer
- Microsoft Entra B2B collaboration with cross-tenant access settings configured to allow guest accessAnswer
- CMicrosoft Entra Connect Sync with Pass-through Authentication (PTA) and password writeback enabled
- DActive Directory Federation Services (AD FS) with active-passive federated trust servers