AZ-305 Practice Question 92: Entra Kerberos Azure Files Hybrid

Microsoft Azure Solutions Architect Expert (AZ-305) · Test 10 · question 2 of 10

Identity, Governance & Monitoringhard

A company is retiring its last on-premises domain controller after moving all workloads to Microsoft Entra ID. It still has an Azure Files share that end users map as a network drive from Windows 11 devices over SMB, authenticating with their existing hybrid identities (on-premises Active Directory accounts synchronized to Entra ID with Microsoft Entra Connect Sync). Users must keep authenticating with their same corporate credentials, NTFS-style directory and file permissions must still be enforced, and the design must not require line of sight to any domain controller or Microsoft Entra Domain Services instance from the client devices.

What should you include in the design?

Select one answer
Show answer and explanation

Answer:

  • C. Enable Microsoft Entra Kerberos authentication for hybrid identities on the storage account, and keep Microsoft Entra Connect Sync running to synchronize the AD DS accounts

Microsoft Entra Kerberos authentication for Azure Files lets hybrid identities, on-premises AD DS accounts synchronized to Entra ID, authenticate over SMB with Kerberos tickets issued by Entra ID itself. Client devices no longer need line of sight to a domain controller to authenticate, and directory or file level permissions set with Windows ACLs continue to be enforced, because the identity source is still AD DS for permission evaluation while Entra ID issues the ticket. The one exception is administrative: setting those ACLs for hybrid identities still needs connectivity to an on-premises domain controller from the machine used to configure them. Microsoft Entra Connect Sync (or Cloud Sync) must keep running so the accounts remain synchronized.

Option A is wrong because Microsoft Entra Domain Services stands up a managed pair of domain controllers that clients still need network access to, which the requirement rules out. Option B is wrong because it keeps a domain controller dependency the company is explicitly retiring. Option D is wrong because switching to NFS drops Windows-style NTFS permissions and Windows client compatibility, and NFS Azure file shares do not authenticate individual Windows users with Microsoft Entra ID. Option E is wrong because Azure RBAC data roles control share-level and directory-level access at a coarser grain than NTFS permissions and removing NTFS permissions would drop the granular access control the company already has.

Reference: Microsoft Entra Kerberos Authentication for Azure Files

Practice Test 10 ›

Study guides for AZ-305