Azure Files, Queues, Tables and Managed Disks
😟 THE PROBLEM
An old file server is full, and app components crash when traffic spikes.
😊 THE SOLUTION
Use Azure Files for shares and Queue Storage to smooth out work.
- Ageing on-premises file server✓ Azure Files SMB shares
- Back end overwhelmed by spikes✓ Queue messages and process steadily
- Simple settings need a home✓ Table Storage
Quick answer
Besides Blob Storage, Azure Storage offers Azure Files (fully managed file shares over SMB and NFS), Queue Storage (large numbers of messages between application components), Table Storage (NoSQL key/attribute data) and Managed Disks (block-level storage volumes for virtual machines).
Exam objective: 2.3.1 Compare Azure Storage services. (Skills measured as of July 20, 2026)
Start with a question
Your office file server is full and old. Where do the shared folders go?
To Azure Files: the same mapped drive experience, but managed in the cloud.
Explain it like I’m 10
The technical explanation
Azure Files
- SMB and NFS shares
- Mount from Windows, Linux, macOS
- Replace file servers
- Sync with Azure File Sync
Queues
- Messages up to 64 KB
- Millions of messages
- Decouple components
Tables
- NoSQL key/attribute
- Schemaless
- Cheap, simple
Managed Disks
- Block storage for VMs
- HDD, Standard SSD, Premium SSD, Ultra
- Azure manages the storage
Real-world business scenario
An architecture firm
- The problem
- An ageing on-premises file server held project drawings that 80 staff open as a mapped drive.
- What they used
- Moved the shares to Azure Files and kept a local cache with Azure File Sync.
- Why that choice
- Same drive-letter experience, no server hardware, and cloud backup.
- The result
- The file server was retired and remote staff can access drawings securely.
When to use it and when not to
✓ Use it when…
- **Files** for shared drives.
- **Queues** for background job processing.
- **Tables** for simple NoSQL data.
- **Disks** for VMs.
✕ Think twice when…
- Tables for complex queries (consider Cosmos DB or SQL).
Interview preparation
Say your answer out loud first, then open the model answer. Interviewers care more about your reasoning than the exact words.
Beginner Match each storage service to a use case.
Model answer
Azure Files for shared folders that many computers map as a drive. Queues for passing work messages between parts of an app. Tables for simple NoSQL data such as user settings. Managed Disks for the hard drives of virtual machines.
Intermediate Why would an app use a queue?
Model answer
To decouple components. The front end drops a message on the queue and returns quickly, and back-end workers process messages at their own pace. If workers are slow or down, messages wait instead of being lost, which smooths out traffic spikes.
Experienced developer Azure Files or Blob Storage for a document-processing app?
Model answer
Azure Files if existing software expects a file system path or SMB share, or for lift-and-shift of file servers. Blob Storage for new cloud-native apps reading through HTTP APIs or SDKs, which is cheaper and more scalable, with tiers and events.
Test yourself with exercises
3 original practice questions in the AZ-900 style. Pick your answers, then check them. You will see why each option is right or wrong. Score 75% or more and this topic is marked complete.
Quick revision
Key points
- Azure Files = managed SMB/NFS file shares.
- Queues = messages between components (asynchronous processing).
- Tables = NoSQL key/attribute data.
- Managed Disks = VM block storage.
Important terminology
- Azure Files
- Managed file shares accessible over SMB or NFS, like a network drive.
- Queue Storage
- Stores messages (up to 64 KB each) so app components can work asynchronously.
- Table Storage
- Schemaless NoSQL storage of structured key/attribute data.
- Managed Disk
- A block storage volume attached to an Azure VM.
Common mistakes
- Confusing Queue Storage (messages) with Table Storage (data).
Exam tips
- "Replace an on-premises file server with SMB shares" = Azure Files.
- "Decouple components with messages" = Queue Storage.
Five quick revision questions
-
1.Which service provides SMB file shares?Show
Azure Files.
-
2.Which service stores messages between app components?Show
Queue Storage.
-
3.Which service stores NoSQL key/attribute data?Show
Table Storage.
-
4.What provides storage volumes for VMs?Show
Managed Disks.
-
5.How big can a queue message be?Show
Up to 64 KB.
Official references
Finished this lesson? Tick it off. Your progress is saved in this browser.