AZ-900 Describe Azure architecture and services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Azure Files

  Why this is correct

  Azure Files provides fully managed SMB (Server Message Block) and NFS file shares that you can mount on multiple Azure VMs concurrently, exactly what a legacy application needing shared file storage requires. This eliminates the operational burden of deploying and patching your own file server, while also supporting access over the internet via SMB 3.0 or through Azure File Sync for on-premises caching. Because the shares are backed by Azure storage, you get built-in redundancy and encryption, making Azure Files the correct PaaS choice for this workload.

• ✗

  Azure Blob Storage

  Why it's wrong here

  Incorrect. Azure Blob Storage is an object storage service for unstructured data (e.g., images, videos, backups). It does not natively support the SMB protocol and is not designed to be mounted as a file system by multiple VMs.

  When this WOULD be correct

  Azure Blob Storage would be correct for a scenario where the company needs to store large amounts of unstructured data, such as images, videos, or backups, accessed via REST APIs or SDKs, and does not require SMB protocol or file share mounting.

• ✗

  Azure Managed Disks

  Why it's wrong here

  Azure Managed Disks are block-level volumes designed for attachment to a single virtual machine; each disk is exclusively assigned to one VM and cannot be concurrently mounted by multiple instances. While Azure supports 'shared disks' for specific clustered applications, they require complex configuration and are not a general-purpose file share solution. For a legacy app that stores files needing simultaneous multi-VM access, managed disks would force you to create and manage a separate file server VM, which contradicts the goal of avoiding file-server administration.

• ✗

  Azure Queue Storage

  Why it's wrong here

  Azure Queue Storage is a message-queue service that facilitates asynchronous communication by storing messages (e.g., up to 64 KB each) for decoupled application components; it is not a file storage or file-access protocol. You cannot mount a queue as a file system, nor can applications use SMB or NFS against it, and files are not stored or retrieved in a directory structure. This service addresses messaging needs, not shared file storage, so it fails to meet the application's requirement for concurrent file access by multiple VMs.

  When this WOULD be correct

  An application needs to reliably deliver messages between components, such as processing orders in an e-commerce system where order submissions are queued for backend processing, ensuring no messages are lost.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-900 exam frequently reuses these exact scenarios with slightly different constraints.

Analysis generated from the official AZ-900blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Go deeper

Related to this question