HOTSPOT
You are planning a Microsoft Azure AD solution for a company.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Hot Area:
HOTSPOT
HOTSPOT
You are planning a Microsoft Azure AD solution for a company.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Hot Area:
I agree with the comment from NA, except for one detail. In the second one, the key is that they say AAD REQUIRES! integration with Active Directory Domain Services. AAD, certainly can integrate with LDAP, but it is not REQUIRED.
For me, it would be YES, NO, YES
answers are no, no, yes
Yes – https://docs.microsoft.com/en-us/azure/active-directory-domain-services/manage-group-policy
Settings for user and computer objects in Azure Active Directory Domain Services (Azure AD DS) are often managed using Group Policy Objects (GPOs).
Yes – https://docs.microsoft.com/en-us/azure/active-directory-domain-services/tutorial-configure-ldaps
To communicate with your Azure Active Directory Domain Services (Azure AD DS) managed domain, the Lightweight Directory Access Protocol (LDAP) is used. By default, the LDAP traffic isn’t encrypted, which is a security concern for many environments.
Yes – https://docs.microsoft.com/en-us/azure/active-directory/azuread-dev/active-directory-authentication-libraries
The Azure Active Directory Authentication Library (ADAL) v1.0 enables application developers to authenticate users to cloud or on-premises Active Directory (AD), and obtain tokens for securing API calls.
ADAL must be yes
Microsoft Azure Active Directory Authentication Library (ADAL)
Microsoft Azure Active Directory Authentication Library (ADAL) is a tool in the .NET framework that lets client applications developers authenticate users to an on-premises Active Directory deployment or to the cloud. ADAL will then secure API calls by locating tokens for access. Microsoft says ADAL can helps client application developers be more focused on their application’s business logic because of ADAL’s ability to handle complexity and securing resources without needing extensive security expertise.
Before using ADAL, organizations must be running .NET Framework 4.5 and, if running it on on-premises AD, Active Directory Federation Services for Windows Server 2012 R2. If organizations are using Azure AD as the main identity provider, they must have Internet connectivity, an Azure subscription and an Azure AD tenant.
LDAP integration https://docs.microsoft.com/en-us/azure/active-directory-domain-services/tutorial-configure-ldaps
Joined machines require intune to be managed https://docs.microsoft.com/en-us/mem/intune/configuration/administrative-templates-windows