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.

• ✗

  Restore the entire share from Azure Backup to the yesterday recovery point.

  Why it's wrong here

  Azure Backup recovery points are full, VSS-consistent snapshots of the share, and restoring from a recovery point replaces the entire share with the state at that point in time. If you restore the whole share to yesterday's recovery point, any files created or modified after that recovery point — including unrelated, legitimate changes made by finance users after the deletion — will be overwritten or lost. Although Azure Backup supports item-level recovery in some configurations, the described action of restoring the entire share is too broad and risks far more data loss than necessary.

  When this WOULD be correct

  If the requirement were to restore the entire file share to a previous state, and no other folders had been modified after the recovery point, then using Azure Backup to restore the whole share would be appropriate.

• ✓

  Use the Azure Files snapshot taken before the deletion and copy back only the required folders.

  Why this is correct

  Azure Files snapshots are read-only, point-in-time copies of the entire file share. Because the snapshot was taken before the deletion, it still contains the full folder tree. You can mount that snapshot over SMB or via the Azure portal, then copy back only the affected folders to the live share using tools like AzCopy or Robocopy, leaving all other files and any subsequent valid changes untouched. This is the minimal-impact recovery method.

• ✗

  Enable blob soft delete on the storage account and then recover the folders.

  Why it's wrong here

  Blob soft delete is a data protection feature that applies exclusively to Azure Blob storage, not to Azure Files. Although a storage account can contain containers and file shares side by side, enabling blob soft delete only affects blobs; it has no effect on SMB file shares or their directory structures. Azure Files has its own native protection mechanisms — share snapshots and Azure Backup — and "folders" inside a file share are not recoverable through blob APIs or blob soft-delete policies.

  When this WOULD be correct

  An administrator needs to recover accidentally deleted blobs in an Azure Blob Storage container, and the storage account has blob soft delete enabled. The administrator can use the soft delete feature to undelete the blobs within the retention period.

• ✗

  Create a new file share and use synchronization to merge the deleted content.

  Why it's wrong here

  Synchronization, whether Azure File Sync or manual syncing tools, moves data based on the current state of the source and destination; it does not preserve or replay historical versions. Creating a new file share and syncing would pull in the already-deleted state from the live share, so the deleted folders would remain absent. Since the deletion event is not captured as a recoverable point in a sync process, file sync cannot reconstruct the removed folder tree and is not a point-in-time restore mechanism.

  When this WOULD be correct

  An administrator needs to migrate data from an on-premises server to Azure while maintaining continuous access and minimizing downtime. Using Azure File Sync to synchronize the on-premises share with a new Azure file share would be correct.

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