Microsoft Certified: Azure Developer Associate (AZ-204)Develop for Azure storageEasy
A web application stores user profile images in Azure Blob Storage. These images are frequently accessed for the first 30 days, then rarely accessed for the next 90 days, and finally almost never accessed but must be retained for compliance. To optimize costs, the company wants to automatically move blobs between tiers based on their access patterns. Which Azure Blob Storage feature should be implemented?
- AImmutable storage
- BBlob index tags
- CLifecycle management policies
- DSoft delete
Show answer & explanationAnswer & explanation
Correct answer: C. Lifecycle management policies
Azure Blob Storage lifecycle management policies allow you to define rules to automatically transition blobs between access tiers (Hot, Cool, Archive) or delete them based on age, last modified time, or access time. This directly addresses the requirement for cost optimization by automating tier transitions.
Why the other options are wrong
- A. Immutable storage is for WORM (Write Once, Read Many) compliance, not for cost optimization through tiering.
- B. Blob index tags are for searching and categorizing blobs, not for automatic tiering.
- D. Soft delete protects against accidental deletion, but does not manage tiering.
Azure Blob Lifecycle Management
Automates the process of tiering blobs to different access tiers (Hot, Cool, Archive) or deleting them based on rules, optimizing storage costs.
- Moves data between Hot, Cool, and Archive tiers.
- Rules are based on age, last modified, or last accessed time.
- Helps optimize storage costs and meet compliance requirements.
Memory trick: Think of lifecycle management as an automated 'storage butler' for your blobs.