Question 41 — AZ-104 Practice Exam 4
A team is lifting a legacy line-of-business app to the cloud. The app expects a traditional file share, uses native file system APIs, and multiple Azure virtual machines must read and write to the same shared files. Administrators also want users to keep their existing identity-based access experience. (Select one answer)
Use Azure Blob Storage with containers and block blobs for file share semantics
Use Azure Files and access it via SMB/NFS with Microsoft Entra or AD DS–synced identities
Use Azure File Sync alone to provide the cloud file share for the app
Keep an on-premises NAS and mount it to Azure VMs over the internet
Correct answers
Use Azure Files and access it via SMB/NFS with Microsoft Entra or AD DS–synced identities
Explanations
Correct:
Use Azure Files and access it via SMB/NFS with Microsoft Entra or AD DS–synced identities
The app expects a file share and native file system APIs; Azure Files provides SMB/NFS file shares accessible by multiple VMs and supports identity-based access using Microsoft Entra or synced AD DS identities.
Wrong:
Use Azure Blob Storage with containers and block blobs for file share semantics
Blob Storage uses a flat namespace and container model; it’s ideal for streaming/random access, not native file share semantics for lift-and-shift apps.
Use Azure File Sync alone to provide the cloud file share for the app
Azure File Sync replicates Azure Files to Windows Servers; it is not itself the cloud file share service the app would mount.
Keep an on-premises NAS and mount it to Azure VMs over the internet
This contradicts the cloud lift goal and does not leverage the managed, serverless file share provided by Azure Files.