Memory hook: Versions preserve earlier content; soft delete recovers deletion; lifecycle controls aging.
Must remember
- Blob containers hold objects; Azure Files exposes managed file shares over supported protocols. Blob access and a mounted file share are different application interfaces. Identity-based SMB access combines share-level permissions with file/directory permissions.
- Blob access tiers trade storage price against access/retrieval charges and availability behaviour. Hot, cool, cold and archive fit different access patterns; archive rehydration takes time and minimum-duration charges can apply. Check account/redundancy compatibility.
- Versioning retains previous eligible blob versions. Soft delete retains deleted eligible data for a configured period. Container soft delete, blob soft delete and file-share soft delete protect different objects. A snapshot is a point-in-time copy/reference with its own lifecycle.
- Lifecycle rules filter eligible blobs/versions and automate tiering/deletion. Consider current versions, previous versions and snapshots separately. Moving to a cheaper tier too early can create retrieval and early-deletion costs.
- Azure Files snapshots/backup support recovery according to configuration. Restore the correct file/share point and validate permissions and usability. A retained snapshot can continue consuming storage after active files are removed.
- Object replication has supported block-blob/versioning/change-feed requirements and destination behaviour. It does not duplicate every account setting or immediately provide a tested application disaster-recovery plan.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Recover yesterday's overwritten blob | A retained previous version or suitable backup. |
| Recover a recently deleted share | Configured share soft delete/backup, depending on the event. |
| Rarely used data must remain immediately readable | Choose an online tier rather than assuming archive fits. |
Traps
- Soft delete must have protected the resource before the event.
- Archive is not an instant-access tier.
- Deleting current content can leave charged historical versions.
Active recall
1. What differs between versioning and soft delete?
Versioning preserves changes; soft delete provides recovery after supported deletion events.
2. Why review previous versions in lifecycle rules?
They can remain billable even after the current object changes or is deleted.
3. Does a successful mount prove the user may open every file?
No. File/directory permissions can further restrict access.
4. What should be checked before archive tiering?
Required retrieval time, minimum duration, rehydration cost and feature compatibility.
5. Why validate restored data with the application?
Bytes existing does not prove permissions, format and dependencies are usable.