A legacy line-of-business app in Azure still needs traditional domain-join and legacy protocol behaviors without the city running its own domain controllers. Which managed service fits that describe-level need?
Select an answer to reveal the explanation.
Short Explanation
Entra Domain Services is the managed “classic domain” feel in Azure—domain join and legacy-friendly protocols without babysitting DCs. Archive, AzCopy, and the Pricing Calculator do not stand up a managed domain. Lift the old join needs; keep the ops lighter.
Full Explanation
Microsoft Entra Domain Services fits a legacy line-of-business app in Azure that still needs traditional domain-join and legacy protocol behaviors without the city running its own domain controllers. The managed service provides domain-join, group policy, LDAP, and Kerberos/NTLM-compatible authentication in Azure so lift-and-shift apps can keep classic domain expectations while Microsoft operates the managed domain. AZ-900 distinguishes this managed domain offering from the cloud directory alone.
Azure Archive tier as a domain controller replacement is incorrect—Archive is a cold blob access tier, not a directory or domain service. AzCopy as a Kerberos domain-join fabric confuses a storage copy utility with domain-join infrastructure. Azure Pricing Calculator as a managed Active Directory domain is a cost-estimation tool, not a directory or domain controller substitute.
Exam caveat: Entra Domain Services is not identical to self-managed Active Directory Domain Services on IaaS VMs, and not every on-premises domain feature or trust design maps one-to-one; validate legacy app requirements before committing. Operational check: identify which LOB apps still require domain join or legacy protocols, evaluate Entra Domain Services against that checklist, and pilot domain join for one noncritical server before broader cutover.