How to Recover Deleted or Modified Files in Azure File Share with Snapshots
Your company stores departmental documents in an Azure file share. Users need to be able to recover previous versions of files that were deleted or modified accidentally. You need a solution that supports recovery at the file share level without deploying additional virtual machines. What should you configure?
Quick Answer
The correct answer is to create share snapshots for the Azure file share. This works because a share snapshot is a point-in-time, read-only copy of the entire file share, capturing the state of all files at the moment it is taken. When a file is deleted or modified, users can mount a previous snapshot directly from the file share’s properties and copy back the original version, all without deploying any additional virtual machines or infrastructure. On the AZ-104 exam, this question tests your understanding of native Azure storage recovery options versus third-party backup solutions; a common trap is to confuse share snapshots with Azure Backup or file sync, which require extra resources. Remember the key distinction: snapshots are instant, share-level, and VM-free. For a quick memory tip, think “Snapshots save the share, no server to spare.”
⚠ Common exam trap
A common mix-up: candidates confuse blob versioning (a Blob Storage feature) with file share snapshots (an Azure Files feature), or they mistakenly think cloud tiering or immutable storage can serve as a version recovery mechanism, when in fact they serve entirely different purposes.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create share snapshots for the Azure file share.
Azure file share snapshots provide point-in-time, read-only copies of the entire file share, allowing users to recover previous versions of files that were deleted or modified accidentally. This feature operates at the file share level without requiring any additional virtual machines, making it a straightforward and cost-effective solution for version recovery.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable blob versioning.
Why it's wrong here
Blob versioning is for blob storage, not Azure Files.
When this WOULD be correct
You need to automatically retain previous versions of blobs in an Azure Storage account to protect against accidental deletion or overwrite, and you want to enable this at the storage account level without additional infrastructure.
- ✗
Configure Azure File Sync cloud tiering.
Why it's wrong here
Cloud tiering optimizes local storage usage but does not provide the file recovery capability required here.
When this WOULD be correct
An organization wants to reduce on-premises storage usage while keeping frequently accessed files cached locally for fast access. The question would specify needing to extend on-premises file shares to Azure and optimize storage costs.
- ✓
Create share snapshots for the Azure file share.
Why this is correct
Share snapshots provide point-in-time recovery for Azure Files without adding extra infrastructure.
- ✗
Enable immutable blob storage.
Why it's wrong here
Immutable storage is for blob data protection and compliance scenarios, not Azure Files recovery.
When this WOULD be correct
A company needs to store critical business records in Azure Blob Storage with a policy that prevents data from being deleted or overwritten for a specified retention period, such as for regulatory compliance (e.g., SEC Rule 17a-4).
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.
✓Create share snapshots for the Azure file share.Correct answer▾
Why this is correct
Share snapshots provide point-in-time recovery for Azure Files without adding extra infrastructure.
✗Enable blob versioning.Wrong answer — click to see why▾
Why this is wrong here
Blob versioning is a feature of Azure Blob Storage, not Azure Files. The question specifies an Azure file share, which does not support blob versioning; it uses share snapshots for point-in-time recovery.
★ When this WOULD be the correct answer
You need to automatically retain previous versions of blobs in an Azure Storage account to protect against accidental deletion or overwrite, and you want to enable this at the storage account level without additional infrastructure.
Why candidates choose this
Candidates may confuse Azure Files with Azure Blob Storage, or assume that 'versioning' is a universal recovery feature across all Azure storage services.
✗Configure Azure File Sync cloud tiering.Wrong answer — click to see why▾
Why this is wrong here
Azure File Sync cloud tiering optimizes storage by caching frequently accessed files locally, but it does not provide point-in-time recovery of file versions or deleted files at the share level.
★ When this WOULD be the correct answer
An organization wants to reduce on-premises storage usage while keeping frequently accessed files cached locally for fast access. The question would specify needing to extend on-premises file shares to Azure and optimize storage costs.
Why candidates choose this
Candidates may confuse cloud tiering with backup or recovery capabilities, thinking that tiering offloads files to Azure and thus provides versioning or recovery, but it only manages caching and does not retain file versions.
✗Enable immutable blob storage.Wrong answer — click to see why▾
Why this is wrong here
Immutable blob storage is designed for Azure Blob Storage, not Azure Files, and it prevents deletion/modification rather than enabling recovery of previous versions at the file share level.
★ When this WOULD be the correct answer
A company needs to store critical business records in Azure Blob Storage with a policy that prevents data from being deleted or overwritten for a specified retention period, such as for regulatory compliance (e.g., SEC Rule 17a-4).
Why candidates choose this
Candidates may confuse immutable storage with versioning or snapshot capabilities, assuming it can recover previous versions, but it actually locks data to prevent changes.
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
About these practice questions
This AZ-104 question is part of Courseiva's 1,049-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on AZ-104
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A user deleted a nested folder tree from an Azure file share yesterday. Other folders in the share were updated after the deletion and must not be rolled back. Which two actions should the administrator take? Select two.
hard- A.Restore the entire file share from the latest snapshot.
- ✓ B.Open a snapshot taken before the deletion.
- ✓ C.Copy only the deleted folder tree back into the live share.
- D.Convert the file share to the Hot access tier.
- E.Delete the newer folders so the share matches the snapshot exactly.
Why B: Azure file share snapshots provide a point-in-time, read-only copy of the entire share. By opening a snapshot taken before the deletion, the administrator can browse the exact folder tree as it existed at that time. Option C is correct because the administrator can copy only the deleted folder tree from the snapshot back into the live share, leaving all other folders (including those updated after the deletion) intact.
Variation 2. A finance department stores spreadsheets in an Azure file share. Yesterday a user deleted a subfolder tree, but other folders were modified after that point and must not be rolled back. The administrator wants to restore only the deleted subfolder tree to its state from yesterday. What should the administrator use?
hard- A.Restore the entire share from Azure Backup to the yesterday recovery point.
- ✓ B.Use the Azure Files snapshot taken before the deletion and copy back only the required folders.
- C.Enable blob soft delete on the storage account and then recover the folders.
- D.Create a new file share and use synchronization to merge the deleted content.
Why B: Azure Files supports snapshot-based restore at the share level. By taking a snapshot before the deletion, the administrator can mount that snapshot as a read-only copy of the share, then copy back only the deleted subfolder tree without affecting any modifications made to other folders after the snapshot was taken. This meets the requirement of restoring only the deleted content while preserving later changes.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.