AZ-204 Develop for Azure storage Practice Question
Which TWO of the following are features of Azure Blob Storage lifecycle management? (Choose two.)
⚠ Common exam trap
A common mix-up: candidates confuse lifecycle management with other Azure Blob Storage features like immutability policies (legal hold), replication, or encryption, which are separate capabilities with different purposes and configurations.
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
✓
Automatically delete blobs after a specified number of days.
Azure Blob Storage lifecycle management policies let you define rule-based actions that run against blobs based on age or last-modified time. Option A is correct because a lifecycle rule can include a delete action that automatically removes blobs after a specified number of days, which is a core use case for expiring stale data. Option B is correct because lifecycle rules can also include tiering actions, such as moving blobs from Hot to Cool or Cool to Archive after a specified number of days, to reduce storage costs. Option C is not a lifecycle management feature; legal hold is an immutability setting applied through immutability policies or container-level holds, not through lifecycle rules. Option D is not part of lifecycle management; cross-region replication is handled by object replication or geo-redundant storage (GRS/RA-GRS) configurations. Option E is not a lifecycle action; encryption at rest is applied automatically by Azure Storage using Storage Service Encryption (SSE) and is not configured via lifecycle management policies.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Automatically delete blobs after a specified number of days.
Why this is correct
Azure Blob Storage lifecycle management policies allow users to define rules that automatically transition or delete blobs based on their age, access time, or other criteria. A common rule is to delete blobs that are older than a specified number of days, moving them to a soft-delete state or permanently removing them. This feature helps optimize storage costs and manage data retention policies efficiently.
- ✓
Automatically move blobs to a cooler tier after a specified number of days.
Why this is correct
Azure Blob Storage lifecycle management policies enable automatic tiering of blobs between hot, cool, and archive access tiers. Users can configure rules to move blobs that haven't been accessed for a certain period (e.g., 30 days) from the hot tier to a cooler tier, such as Cool or Archive. This automation significantly reduces storage costs for infrequently accessed data without manual intervention.
- ✗
Automatically apply legal hold to blobs.
Why it's wrong here
While Azure Blob Storage supports legal hold functionality, it is implemented through immutability policies, specifically by setting a time-based retention policy or a legal hold policy directly on a container or blob version. This feature prevents deletion or modification of data for compliance purposes. Lifecycle management policies, however, are designed for automated tiering and deletion, not for applying legal holds.
- ✗
Automatically replicate blobs to another region.
Why it's wrong here
Azure Blob Storage provides data redundancy and disaster recovery through replication options like Geo-Redundant Storage (GRS) or Zone-Redundant Storage (ZRS), which are configured at the storage account level upon creation or modification. This ensures data is automatically replicated across different regions or availability zones. Lifecycle management policies operate within a single storage account to manage blob lifecycle stages, not to configure cross-regional replication.
- ✗
Automatically encrypt blobs at rest.
Why it's wrong here
Azure Storage automatically encrypts all data at rest using Azure Storage encryption, which employs 256-bit AES encryption. This encryption is transparently applied by default to all blobs, files, queues, and tables, requiring no explicit configuration or action from the user. Therefore, it is not a feature that needs to be "automatically applied" via lifecycle management or any other user-configurable automation.
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
One of 883 original AZ-204 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.