AZ-900 Describe Azure architecture and services 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.

• ✗

  Azure Backup for Blob Storage

  Why it's wrong here

  Azure Backup for Blob Storage is a managed backup service that creates scheduled or on-demand recovery points and retains them in a Backup Vault, allowing point-in-time restores. However, it is a separate, configurable solution that incurs additional cost and does not automatically prevent accidental overwrites or deletions at the moment they occur; it only enables recovery after the fact. The native, always-available protection that directly preserves prior versions and retains deleted blobs is blob versioning and soft delete, which are the features designed specifically for this scenario.

• ✓

  Blob versioning and soft delete

  Why this is correct

  Blob versioning and soft delete are native Azure Storage features that provide continuous protection against accidental modification and deletion. Blob versioning automatically captures a new version whenever a blob is overwritten, so you can restore to any prior version, while soft delete retains deleted blobs and their versions in a non-accessible state for a configurable retention period (e.g., 7 days). These features operate at the storage account level, require no separate service or extra compute, and are the direct mechanism for undoing accidental changes or deletions within a storage account.

• ✗

  Azure Site Recovery for storage

  Why it's wrong here

  Azure Site Recovery for storage is a disaster recovery service that orchestrates replication and failover of Azure VMs (and on-premises machines) to a secondary Azure region, ensuring business continuity during outages. It operates at the VM and disk level, not at the individual blob granularity, and it is neither designed for nor capable of restoring a previously overwritten blob or a blob deleted by a user. Therefore, it is unrelated to the accidental modification/deletion protection that blob versioning and soft delete provide.

• ✗

  Geo-redundant storage (GRS)

  Why it's wrong here

  Geo-redundant storage (GRS) is a redundancy setting that asynchronously replicates your storage account to a paired secondary region, protecting against regional datacenter outages. However, replication is not point-in-time and does not preserve historical versions; a logical event such as an accidental delete or overwrite is replicated to the secondary region just like any other operation, so the destructive change is copied as well. GRS therefore addresses physical infrastructure failures, not the logical data corruption that blob versioning and soft delete are specifically designed to mitigate.

Go deeper

Related to this question