AZ-305 Design business continuity solutions 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.

• ✓

  Configure Azure Backup on the Azure file share using a Recovery Services vault with geo-redundant storage (GRS). Enable cross-region restore on the vault.

  Why this is correct

  Azure Backup for Azure Files is the native managed backup service that takes scheduled snapshots of the file share and stores recovery points in a Recovery Services vault. By selecting GRS for the vault and enabling cross-region restore, you gain the ability to restore the entire share to the paired region (East US to West US) if a regional disaster occurs. The service also supports granular item-level restore, allows you to specify backup frequency and retention, and automatically manages the snapshot lifecycle, making it the only option here that meets both backup and DR requirements.

• ✗

  Use Azure File Sync to sync the file share to an on-premises server, and then back up the on-premises server using Azure Backup.

  Why it's wrong here

  Azure File Sync is a synchronization and cloud tiering service designed to keep an Azure file share and an on-premises Windows server in sync; it is not a backup mechanism. If you back up the on-premises server, you are only backing up a cached replica, not the authoritative cloud share, and any accidental deletions or corruption that syncs from the client to the cloud will also be replicated to the local cache. This approach exposes you to data loss and provides no file-level restore history or cross-region recovery of the Azure file share, so it fails to meet the requirement.

• ✗

  Enable soft delete and versioning on the storage account, and configure replication to a secondary region using RA-GRS.

  Why it's wrong here

  Enabling soft delete and versioning on the storage account is meaningful for blobs, but Azure file shares do not support blob-style versioning; share snapshots are the closest equivalent, and the option does not mention a backup policy. Soft delete protects against accidental share deletion but is not a scheduled backup service and provides no point-in-time restore to arbitrary times. RA-GRS replication gives you read-only access to a secondary region, but without the Recovery Services vault and cross-region restore, you cannot perform a full restore or granular file recovery from that secondary copy, so this falls short of the required backup and DR capability.

• ✗

  Create a scheduled Azure Automation runbook that takes snapshots of the file share every day and copy them to a storage account in West US.

  Why it's wrong here

  Building a custom Azure Automation runbook to take daily snapshots and copy them to West US introduces significant operational complexity, including writing custom scripts to manage snapshot creation, retention, and geographic copying. Azure file share snapshots are bound to the storage account and must be manually copied to another region; there is no built-in monitoring, alerting, or restore UI, and the runbook becomes a single point of failure if credentials expire or execution fails. This DIY approach lacks the enterprise qualities of Azure Backup, such as policy-based scheduling, archive tiering, and failover support, so it is not a managed or reliable solution.

Go deeper

Related to this question