You have an Azure subscription that contains an Azure Files share named share1 and a user named User1. Identity-based authentication is configured for share1. User1 attempts to access share1 from a…

Question

Options

• AOAuth 2.0
• BJSON Web Token (JWT)
• CSAML
• DKerberos

• A
  5% (2)
• B
  15% (6)
• C
  3% (1)
• D
  78% (31)

Explanation

Azure Files Identity-Based Authentication

Why Kerberos is correct (D): When Azure Files uses identity-based authentication over SMB, it relies on Kerberos tokens for authorization. SMB (Server Message Block) is a Windows-native protocol that integrates directly with Active Directory authentication, and Kerberos is the standard authentication protocol used by Active Directory Domain Services (AD DS) and Azure Active Directory Domain Services (Azure AD DS) for this purpose.

Why the distractors are wrong:

• OAuth 2.0 (A) is used for delegated authorization in REST-based API access (e.g., accessing Azure Blob Storage via REST), not SMB-based file share access
• JWT (B) tokens are associated with OAuth 2.0 and OpenID Connect flows - again, REST/HTTP-based scenarios, not SMB
• SAML (C) is a federation protocol used for web-based single sign-on (SSO) and has no role in SMB file share authentication

Memory Tip: Think "SMB = Kerberos" - these two technologies are long-time partners in the Windows/Active Directory ecosystem. If a question mentions SMB + identity-based auth + Azure Files, Kerberos is almost always the answer, just as it would be in a traditional on-premises Active Directory environment.

No community discussion yet for this question.