Drag a concept onto its matching description — or click a concept then click the description.
Concepts
Matches
Azure File Sync
SMB with AD DS-based identity authentication
NFS 4.1 share
SAS token
AZ-104 Implement and Manage Storage Practice Question
Match each file-sharing requirement to the best Azure Files mounting or integration approach.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
SMB: Requires storage account credentials and port 445 for mounting
SMB mounting requires storage account credentials; NFS needs private endpoint; REST API for programmatic access; Azure AD DS enables identity-based access; File Sync caches on-premises.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
SMB: Requires storage account credentials and port 445 for mounting
Why this is correct
SMB is the native file-sharing protocol for Azure Files, and mounting a share typically requires a storage account key or a shared access signature as the credential and must be reachable over TCP port 445. On Windows, users can run `net use` to map a drive, while Linux/macOS clients often use `mount.cifs` with the storage account name as the username. Because port 445 is used by SMB, secure connectivity may require an ExpressRoute or VPN if the client network blocks that port.
- ✓
NFS: Requires private endpoint for mounting
Why this is correct
The NFS protocol for Azure Files requires the file share to be created in the Premium tier and to be accessed through a private endpoint, so the storage account must be attached to a virtual network. Once the private endpoint is configured with a private IP address, clients can mount the share using the standard NFS 4.1 protocol over port 2049, without providing a storage account key. This makes NFS suitable for Linux/UNIX clients and orchestrators, but the private endpoint requirement is mandatory because NFS endpoints are not exposed through the public storage service.
- ✓
REST API: Used for programmatic access to Azure file shares
Why this is correct
The Azure Files REST API, which is part of the Azure Storage REST API, provides programmatic control over file shares, directories, and files via HTTPS operations such as PUT, GET, and DELETE on resource URIs. It is the foundation for Azure PowerShell cmdlets, the Azure CLI, and client libraries in languages like .NET, Python, and Java, allowing automation of file share management and data transfer. This is the correct match for 'programmatic access' because it offers an API surface rather than a protocol for interactive mounting.
- ✗
Azure AD DS: Used for programmatic access to Azure file shares
Why it's wrong here
Azure AD Domain Services is a managed domain service that provides Kerberos and NTLM authentication, and when enabled for Azure Files, it grants identity-based access so users can map shares using their Azure AD credentials instead of storage account keys. However, it does not expose any REST API or SDK-like interface for programmatically enumerating or modifying files, so it cannot fulfill a 'programmatic access' requirement. The wrong association here is pairing an identity/authentication service with an API access requirement; programmatic access is handled by the Azure Files REST API and its language SDKs.
- ✗
File Sync: Enables identity-based access to Azure file shares
Why it's wrong here
Azure File Sync is a service that replicates an Azure file share to a Windows Server, providing on-premises caching, cloud tiering, and multi-site sync, but it does not itself manage user authentication or authorization to the share. Identity-based access to Azure Files is enabled through Azure AD DS or on-premises AD DS with Kerberos—not by File Sync, which is purely a synchronization/caching layer. Therefore, this option is incorrect for the 'enables identity-based access' requirement because that capability belongs to Azure AD DS, not to File Sync.
Go deeper
Related to this question
Learn chapter
Privileged Identity Management (PIM)
Key term
Private endpoint
A private endpoint is a network interface that securely connects a service over a private IP address inside a virtual network, keeping traffic off the public internet.
Key term
Azure Files
Azure Files is a cloud-based file sharing service that lets you create and access file shares using the Server Message Block (SMB) protocol or Network File System (NFS) protocol, just like you would access files on a local network drive.
About these practice questions
One of 1,049 original AZ-104 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.