AZ-204 Azure Blob Lifecycle Management Practice Question
You have an Azure Storage account with cool tier blobs. You need to implement lifecycle management to move blobs to the archive tier after 30 days if they have not been accessed, and delete them after 365 days. Which lifecycle management rule action should you configure?
⚠ Common exam trap
The trap is that 'daysAfterModificationGreaterThan' is a common condition, but for access-based rules, you must use 'daysAfterLastAccessTimeGreaterThan' and explicitly enable blob access tracking on the storage account.
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
✓
Use a rule with condition 'daysAfterLastAccessTimeGreaterThan' to tier and delete, and enable blob access tracking.
The requirement specifies 'if they have not been accessed', which requires tracking last access time. Lifecycle management rules support the 'daysAfterLastAccessTimeGreaterThan' condition, but blob access tracking must be enabled for this condition to work. Option A includes both the condition and enabling access tracking, making it the correct choice. Option D uses 'daysAfterModificationGreaterThan', which tracks last modification time, not access time, so it does not meet the requirement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use a rule with condition 'daysAfterLastAccessTimeGreaterThan' to tier and delete, and enable blob access tracking.
Why this is correct
Correct. This option includes the condition 'daysAfterLastAccessTimeGreaterThan' which tracks when the blob was last read, and also enables blob access tracking, which is required for that condition to work. This aligns with the requirement to move blobs that have not been accessed.
- ✗
Use a rule with condition 'daysAfterLastAccessTimeGreaterThan' to tier and delete.
Why it's wrong here
While 'daysAfterLastAccessTimeGreaterThan' is the correct condition type for managing blobs based on access, this option is incomplete because it omits the critical step of enabling blob access tracking. Without explicitly activating 'Last access time tracking' on the storage account, the 'LastAccessTime' property for blobs will not be populated or updated. Consequently, the lifecycle management rule would lack the necessary data to evaluate the condition, rendering it ineffective for tiering or deleting based on access.
- ✗
Use a rule with condition 'daysAfterSnapshotCreationGreaterThan' to tier and delete.
Why it's wrong here
Using 'daysAfterSnapshotCreationGreaterThan' is incorrect because this condition specifically targets the age of *blob snapshots*, not the primary blob objects themselves. The question's requirement is to manage blobs based on their *access patterns*, making a snapshot-specific condition irrelevant for evaluating when a base blob was last read or written to. This rule would only apply if the goal was to manage the lifecycle of backup copies, not the active data.
- ✗
Use a rule with condition 'daysAfterModificationGreaterThan' to tier after 30 days and delete after 365 days.
Why it's wrong here
The condition 'daysAfterModificationGreaterThan' tracks the time since a blob's content or metadata was last altered, not when it was last read. The problem statement explicitly requires managing blobs 'if they have not been accessed', which refers to read operations. Therefore, relying on modification time would incorrectly tier or delete blobs that are actively being read but not modified, failing to meet the specified access-based criteria.
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
Courseiva writes every AZ-204 question from scratch — 881 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.