Your company has an Azure subscription with an Azure Active Directory (Azure AD) tenant. Your company wants to deploy a system that allows users to have a unified experience across all their Windows devices. The security policies of your company require that all user and application data must be encrypted before moving to the cloud and also be encrypted at rest when stored in the cloud.
All computers in your company runs different versions of Windows 7, Windows 8.1, and Windows 10. Your company has an Active Directory Domain Service (AD DS) domain on the local infrastructure. All the computers in the company are joined to the AD DS domain.
You need to deploy Enterprise State Roaming. Your solution needs to require the lowest possible costs.
Which two prerequisites do you need to meet before configuring Enterprise State Roaming? Each correct answer presents part of the solution.
You should purchase Azure AD Premium P1 licenses. You can enable Enterprise State Roaming on any Azure AD Premium license or Enterprise Mobility + Security (EMS) license. In this case, the Premium P1 license has the lower costs.
You should also configure Azure AD Connect. Since all computers in the company are joined to an AD DS domain, you need to deploy Azure AD Connect. This connector allows you to synchronize objects in your on-premises AD DS domain with an Azure AD tenant.
You should not purchase an Azure AD Basic license. This license level does not allow you to enable the Enterprise State Roaming feature.
You should not deploy AD FS. This is not a requirement for deploying the Enterprise State Roaming feature in hybrid scenarios. Azure AD Connect is the required component for hybrid synchronization scenarios.
You should not update all Windows 7 and Windows 8.1 computers to Windows 10. All of these versions are supported for Enterprise State Roaming.