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.

• ✗

  Blob versioning

  Why it's wrong here

  Blob versioning is a feature designed exclusively for Azure Blob Storage, not for Azure file shares. When enabled, it automatically maintains a history of every blob version, allowing retrieval of prior states, but Azure Files stores data using the SMB/FileREST protocol in a different namespace and does not expose blob versioning on its file share objects. To use blob versioning you would have to migrate your data to blob storage, which changes the access pattern and file semantics. Therefore, blob versioning cannot recover prior versions of files in an Azure file share.

  When this WOULD be correct

  If the question asked about recovering previous versions of blobs in an Azure Blob Storage container after accidental modification or deletion, then blob versioning would be the correct feature to configure.

• ✓

  Share snapshots for Azure Files

  Why this is correct

  Share snapshots are read-only, point-in-time copies of an Azure file share that capture the exact state of all files at the moment the snapshot is created. Because the snapshot preserves the contents of every file as it existed at that instant, you can mount the snapshot or use its share path to copy an earlier version of a specific file back over the live version, achieving full point-in-time recovery. This is the native Azure Files mechanism for keeping and restoring previous file versions, and it works directly on SMB shares without requiring another storage service.

• ✗

  A shared access signature

  Why it's wrong here

  A shared access signature (SAS) is a security credential that grants delegated, time-limited permissions to specific storage resources, such as a file or file share, for operations like read, write, list, or delete. It does not create or store any historical data, backups, or snapshots; it only authorizes access to the current state of the resource. Using a SAS could allow a client to overwrite a file, but it cannot undo that overwrite or restore an earlier version of the file. Recovery requires an actual data-capturing mechanism like snapshots or backups, not an access token.

  When this WOULD be correct

  A question asking for a method to grant time-limited, delegated access to a specific file share for a third-party application, without sharing the storage account key, would have SAS as the correct answer.

• ✗

  Storage account failover

  Why it's wrong here

  Storage account failover is a disaster-recovery capability in Azure Storage that switches the primary endpoint to the secondary region when the original primary fails, used with geo-redundant storage (GRS/RA-GRS). It changes which data center hosts the live endpoint and affects replication and availability across regions, but it does not maintain a timeline of previous file versions. After failover, you access the data as it was replicated to the secondary, which may be stale but is still only a single copy, not a versioned history. It is meant for continuity, not point-in-time recovery of individual files.

  When this WOULD be correct

  This option would be correct in a scenario where the question asks: 'You need to ensure that your storage account remains available during a regional outage. Which feature should you configure?'

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