AZ-305 Practice Question 36: File Share Protection
Microsoft Azure Solutions Architect Expert (AZ-305) · Test 4 · question 6 of 10
A consultancy has moved its department file server to a 4 TB Azure file share. The requirements for protecting it are:
- a daily backup, with daily, weekly, and monthly retention, - the ability to restore a single file that a user overwrote, not only the whole share, - protection if someone deletes the file share itself, - no servers, agents, or scripts to maintain.
What should you recommend?
Show answer and explanation
Answer:
Azure Files backup is a native, managed solution whose stated benefits line up with the list: zero infrastructure to deploy, customized daily, weekly, monthly, or yearly retention, built-in scheduling and pruning, and instant restore of just the files you select because the backups are share snapshots. Configuring it also enables soft delete on the storage account with a 14-day retention, so a deleted file share and its snapshots are recoverable, and Azure Backup takes a lease on its snapshots so they cannot be deleted accidentally.
Option A rebuilds a fraction of that by hand. The consultancy would own the runbook, its schedule, its identity, and its failure handling; the snapshots would carry no lease protecting them from deletion; and deleting the share would still take everything with it.
Option B inverts the design. Azure File Sync exists to keep an on-premises server and the cloud share in step, not to protect the share, and it puts back the file server and backup software the consultancy just retired.
Option D changes durability, not recoverability. Redundancy protects against infrastructure failure by replicating every write, including the overwrite and the deletion. It cannot return yesterday's version of a file.
Reference: About Azure Files backup