A developer accidentally deleted a blob that had several snapshots. You must be able to recover deleted blobs for up to 14 days, including their snapshots, with minimal operational overhead. What should you do?

Enabling blob soft delete with a 14-day retention period directly addresses the requirement to recover deleted blobs and their snapshots for up to 14 days with minimal overhead. When soft delete is enabled, deleted blobs transition to a soft-deleted state rather than being permanently removed, allowing them to be restored using the Undelete Blob operation. This preserves all associated snapshots. Container soft delete only protects containers, not individual blobs, and doesn't inherently restore snapshots. Creating daily snapshots and copying from them is a manual and high-overhead process for recovery, especially for numerous blobs. Point-in-time restore is primarily for container-level or account-level recovery from accidental deletion or corruption, but soft delete is more direct and efficient for individual blob recovery. The change feed tracks changes but doesn't provide a direct mechanism to restore deleted blobs and their snapshots; replaying events to rebuild a blob would be complex and error-prone.