Question 37 — AZ-104 Practice Exam 1
For each storage service, drag it to the appropriate boxes in the Correct Match column to match it against its description in the Option column.
Each item may be used once, more than once, or not at all.
| Option | Correct Match |
|---|---|
| Provides SMB and NFS access with client libraries and a REST interface, accessible from anywhere | [Gap 1] |
| Stores unstructured data in block blobs with client libraries and a REST interface at massive scale | [Gap 2] |
| Uses true directory objects and is accessed through file shares across multiple virtual machines | [Gap 3] |
| Uses a flat namespace and data is accessed through containers | [Gap 4] |
| Ideal for “lift and shift” apps that use native file system APIs and share data with other Azure apps | [Gap 5] |
| Ideal for streaming and random-access scenarios | [Gap 6] |
- Azure Blob Storage
- Azure Files
- Azure File Sync
- On-premises file server
Correct answers
- Gap 1: Azure Files
- Gap 2: Azure Blob Storage
- Gap 3: Azure Files
- Gap 4: Azure Blob Storage
- Gap 5: Azure Files
- Gap 6: Azure Blob Storage
Explanations
Correct Matches
Azure Files – Provides SMB and NFS access with client libraries and a REST interface that can be reached from anywhere, aligning with the service’s protocol support and access model. It also uses true directory objects and is accessed via file shares across multiple virtual machines, making it ideal for lifting and shifting applications that already rely on native file system APIs.
Azure Blob Storage – Stores unstructured data as block blobs and exposes client libraries and a REST interface. The service uses a flat namespace with data organized in containers, and is well-suited to streaming and random-access scenarios.
Unused Item(s)
On-premises file server – Not a cloud PaaS offering and does not match the described Azure cloud characteristics.
Azure File Sync – A replication/sync technology for Azure Files rather than a primary storage service that satisfies the listed descriptions.