AZ-204 Practice Question: Azure Blob Storage lifecycle management policy
A company stores customer images in Azure Blob Storage. They need to reduce costs by automatically moving blobs that have not been accessed for 30 days to Cool tier, and after 90 days to Archive tier. They also need to delete blobs after one year. Which two Azure features should they implement? (Choose two.)
⚠ Common exam trap
Candidates often think only lifecycle management is required, but versioning with a retention policy is also needed to handle blob versions that can accumulate and increase costs. Additionally, some may confuse access tier configuration (which is automatically available) as a separate feature, but it is not an option here.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Azure Blob Storage lifecycle management policy
Azure Blob Storage lifecycle management policy allows you to define rules to automatically transition blobs to Cool and Archive tiers based on last access time and delete them after one year. Additionally, versioning with a retention policy automatically removes old blob versions after a specified period, preventing unnecessary storage costs from accumulating. Together, these features optimize storage costs by managing both current blobs and their versions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Azure Blob Storage lifecycle management policy
Why this is correct
A lifecycle management policy offers a robust, automated solution for optimizing storage costs by defining rules to transition blobs between access tiers (Hot, Cool, Archive) or delete them based on age or last modification time. This policy directly automates the movement of less frequently accessed data to more cost-effective tiers or its permanent removal, significantly reducing storage expenses without requiring application changes or manual oversight.
- ✗
Azure Blob Storage object replication
Why it's wrong here
Object replication is primarily used for maintaining a copy of blobs in a different Azure region or storage account, enhancing data redundancy, disaster recovery capabilities, or supporting geo-distributed applications. While it ensures data availability, it inherently increases storage costs by duplicating data, rather than reducing them through tiering or deletion. It does not automate cost-optimized tier transitions within the source account.
- ✗
Azure Blob Storage soft delete
Why it's wrong here
Soft delete provides a safety net against accidental or malicious deletion of blobs by retaining deleted data for a configurable period, allowing for recovery. Its purpose is data protection and recovery, not proactive cost optimization. During the soft delete retention period, the deleted blobs still incur storage costs, and the feature itself does not automate tiering or permanent deletion of unneeded data to reduce expenses.
- ✗
Azure Blob Storage immutability policy
Why it's wrong here
An immutability policy is designed for data governance and regulatory compliance, preventing blobs from being modified or deleted for a specified duration or indefinitely. While crucial for data integrity and legal hold scenarios, it actively prevents actions like moving data to cheaper tiers or deleting old versions, which are essential for cost optimization. Therefore, it does not contribute to reducing storage costs by managing data lifecycle.
- ✓
Azure Blob Storage versioning with a retention policy
Why this is correct
Azure Blob Storage versioning automatically maintains previous states of a blob whenever it is modified or deleted, providing a historical record. When combined with a retention policy, older versions are automatically deleted after a specified period, preventing indefinite accumulation of data. This strategy directly optimizes costs by ensuring that only necessary versions are retained, reducing overall storage consumption over time without manual intervention.
Quick reference
Azure Blob Storage Tier Comparison
| Tier | Storage Cost | Retrieval Cost | Latency | Use Case |
|---|---|---|---|---|
| Hot | Highest | Lowest | Immediate | Active data, frequent reads |
| Cool | Lower | Higher | Immediate | Data accessed < once / month |
| Cold | Lower still | Higher | Immediate | Data accessed < once / quarter |
| Archive | Lowest | Highest + rehydration delay | Hours | Long-term compliance retention |
Go deeper
Related to this question
About these practice questions
This AZ-204 question is part of Courseiva's 881-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.