Microsoft Certified: Azure Developer Associate (AZ-204)Develop for Azure storageMedium
A company is developing a new application that stores large binary files, such as images and videos. The application requires the ability to retain previous versions of these files whenever they are modified or deleted, allowing for point-in-time recovery and compliance auditing. Which Azure Blob Storage feature should be enabled to meet this requirement?
- AChange feed for Blob Storage
- BImmutable storage
- CBlob versioning
- DSoft delete for blobs
Show answer & explanationAnswer & explanation
Correct answer: C. Blob versioning
Blob versioning automatically creates a new version of a blob each time it's modified or deleted. This allows you to restore previous states of the blob and audit changes over time, directly addressing the requirement for retaining previous versions.
Why the other options are wrong
- A. Change feed provides a log of all changes to blobs, but it's a data stream, not a mechanism for storing and retrieving previous versions of the blob content itself.
- B. Immutable storage prevents blobs from being modified or deleted for a specified retention period, which is for compliance but not for maintaining multiple versions of a changing file.
- D. Soft delete protects against accidental deletion by retaining deleted blobs for a period, but it doesn't create new versions on modification.
Azure Blob Versioning
A feature of Azure Blob Storage that automatically saves the previous state of a blob each time it's modified or deleted, allowing recovery of earlier versions.
- Creates new versions on write or delete.
- Enables point-in-time recovery.
- Supports compliance auditing.
- Increases storage costs due to multiple versions.
Memory trick: Versioning is like a 'Time Machine' for your blobs, letting you go back to any version.