AZ-104 Implement and Manage Storage 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 Blob Storage with lifecycle rules, because it can present files to multiple branches.

  Why it's wrong here

  Azure Blob Storage is object storage that supports data lifecycle management to move blobs between hot, cool, and archive tiers based on last-modified dates, but it cannot present a distributed SMB namespace to Windows file servers. Lifecycle rules do not push content to branch servers or maintain file-level locks and ACLs needed for shared Windows folders. Attempting to use Blob storage for this scenario would require building a custom sync layer, whereas Azure Files is the managed SMB offering in Azure.

  When this WOULD be correct

  A company needs to store large amounts of unstructured data (e.g., backups, logs, media) and automatically move it to cooler tiers (e.g., cool or archive) based on age to optimize costs. Lifecycle rules manage tier transitions automatically.

• ✓

  Azure File Sync, because it synchronizes on-premises file servers with an Azure file share and supports cloud tiering.

  Why this is correct

  Azure File Sync is designed for this exact scenario. It keeps an Azure file share as the central source of truth while synchronizing branch servers and optionally tiering infrequently used files to the cloud. That gives users local performance, file-share consistency, and better resilience during temporary WAN disruptions. It is the best fit when multiple Windows servers need synchronized file content.

• ✗

  A private endpoint to Blob Storage, because it provides local caching for SMB file shares.

  Why it's wrong here

  A private endpoint provides a private IP address from your virtual network to access Azure Blob Storage, but it does not create local caches or synchronize file content to branch Windows servers. It only manages network connectivity and allows controlled ingress/egress; it cannot replicate an SMB file share across locations. Without a sync engine like Azure File Sync, each branch server would still need its own independent storage and content management.

  When this WOULD be correct

  A question asks: 'You need to ensure that an Azure Storage account is accessible only from a specific virtual network, without exposing it to the public internet. Which Azure feature should you deploy?' In this scenario, a private endpoint is the correct answer.

• ✗

  A managed disk shared across the branch servers, because it gives the same content to all locations.

  Why it's wrong here

  A managed disk is a block-level storage device attached to a single Azure VM, and even Azure Shared Disks only support simultaneous attachment by cluster VMs within the same availability zone. You cannot mount a managed disk to on-premises Windows file servers in different branch offices, nor does it provide replication or conflict-resolution logic. It is infrastructure for VM storage, not a cross-site file-synchronization fabric, so it fails to meet the requirement for shared content across 15 branches.

  When this WOULD be correct

  You need to provide a high-performance, low-latency shared block storage for a single virtual machine or a clustered application (e.g., SQL Server FCI) that requires SCSI-3 Persistent Reservations for shared access.

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-104 exam frequently reuses these exact scenarios with slightly different constraints.

Analysis generated from the official AZ-104blueprint 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