AZ-305 ยท Semi-structured and unstructured data design
Protecting unstructured data
Blob soft delete, container soft delete, versioning, change feed, point-in-time restore, immutable storage (time-based retention, legal hold), Azure Files share snapshots and soft delete.
Key points
- Blob soft delete (1-365 days): blobs, snapshots, versions; container soft delete: containers.
- Point-in-time restore: needs soft delete, versioning, change feed; retention 1+ day shorter than soft delete; no deleted containers or hierarchical namespace.
- Immutable storage (WORM): time-based retention (lock for SEC 17a-4(f)) or legal holds.
- Resource Manager lock: account only.
- Azure Files: share snapshots (up to 200), share soft delete.
Source: https://learn.microsoft.com/en-us/azure/storage/blobs/data-protection-overview
Practice questions
Which features must be enabled before you can turn on point-in-time restore for block blobs?
- Container soft delete, versioning and a legal hold
- Blob soft delete, blob versioning and change feed
- Change feed, object replication and RA-GRS
- Blob soft delete, container soft delete and a resource lock
Show answer
Answer: B. Blob soft delete, blob versioning and change feed
Point-in-time restore builds on blob soft delete, blob versioning and change feed. Container soft delete and immutability policies are separate protections and are not prerequisites; object replication is a copy mechanism, not a prerequisite.
Which options protect data in Azure file shares?
- Share snapshots, up to 200 per share
- Soft delete for file shares
- Azure Backup for Azure file shares
- Blob versioning on the storage account
- Point-in-time restore for block blobs
Show answer
Answer: A. Share snapshots, up to 200 per share, B. Soft delete for file shares, C. Azure Backup for Azure file shares
Azure Files uses share snapshots (incremental, up to 200 per share), share soft delete, which is enabled by default for new storage accounts, and Azure Backup, which schedules and retains snapshots. Blob versioning and point-in-time restore apply to blobs, not to file shares.
With blob soft delete enabled, you can recover a container that someone deleted, together with its blobs.
Show answer
Answer: False
False. Blob soft delete protects individual blobs, snapshots and versions only. To recover a deleted container and its contents you need container soft delete, which Microsoft recommends enabling alongside blob soft delete.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
