Question 35 — Domain 3-Describe Azure management and governance | AZ-900 Practice Exam | 230 Questions
For each domain solution listed below the table, drag it to the appropriate boxes in the Correct Match column to match it against its description in the Option Column. Each item may be used once, more than once or not at all.
| Option | Correct Match |
|---|---|
| Extends on-premises AD objects to the cloud using synchronization | [Gap 1] |
| Requires you to manage the operating system on an Azure VM | [Gap 2] |
| Fully managed service offering legacy protocols like LDAP and Kerberos | [Gap 3] |
| Acts as the identity provider for modern authentication (e.g., Microsoft 365) | [Gap 4] |
| Demands manual patching for domain controllers | [Gap 5] |
| Enables single sign-on for cloud services | [Gap 6] |
| Allows Group Policy and NTLM support in Azure without custom VMs | [Gap 7] |
| Synchronizes from Entra ID but is a standalone managed domain | [Gap 8] |
- On-premises AD with Azure AD Connect
- Azure Active Directory Domain Services
- Self-managed AD on Azure VM
- Azure Entra ID (Azure AD)
Correct answers
- Gap 1: On-premises AD with Azure AD Connect
- Gap 2: Self-managed AD on Azure VM
- Gap 3: Azure Active Directory Domain Services
- Gap 4: Azure Entra ID (Azure AD)
- Gap 5: Self-managed AD on Azure VM
- Gap 6: Azure Entra ID (Azure AD)
- Gap 7: Azure Active Directory Domain Services
- Gap 8: Azure Active Directory Domain Services
Explanations
Extends on-premises AD to Azure through synchronization: On-premises AD with Azure AD Connect
Azure AD Connect enables synchronization between an on-premises AD and Entra ID, allowing organizations to maintain hybrid identity solutions.
Requires manual management of operating system and domain controllers: Self-managed AD on Azure VM
When running AD on an Azure VM, administrators are responsible for OS-level patching, security, and domain controller maintenance.
Provides managed legacy authentication and directory services: Azure Active Directory Domain Services
Azure AD DS offers legacy authentication capabilities like NTLM, Kerberos, and LDAP while Microsoft fully manages the infrastructure.
Serves as the main identity provider for cloud applications like Microsoft 365: Azure Entra ID (Azure AD)
Entra ID is the cloud-based directory primarily used for modern authentication across SaaS applications, Azure services, and Microsoft 365.
Includes features like Group Policy, LDAP, NTLM, and Kerberos in a managed service: Azure Active Directory Domain Services
Azure AD DS provides Group Policy support and legacy authentication protocols to support applications requiring traditional Active Directory features.
Needs administrators to configure and maintain Active Directory on a virtual machine: Self-managed AD on Azure VM
With this approach, organizations must manually manage domain controllers, including configuration, backups, and security updates.
Supports legacy authentication methods within a cloud-based managed domain: Azure Active Directory Domain Services
Azure AD DS allows legacy applications to authenticate using LDAP, NTLM, and Kerberos, making it suitable for migrating older applications to Azure.
Provides a fully modern authentication approach without support for legacy protocols: Azure Entra ID (Azure AD)
Entra ID supports OAuth, OpenID Connect, and SAML, making it ideal for modern cloud applications but not for legacy authentication needs.