You are configuring a lifecycle management policy for a Standard General Purpose v2 (GPv2) storage account to minimize costs for log blobs. The policy will transition blobs through various access tiers and eventually delete them.
Arrange the following lifecycle policy events in the correct chronological order of execution for a newly created blob, starting from the earliest event to the latest.
- 1The blob is uploaded to the storage account and initially stored in the Hot access tier.
- 2The lifecycle rule transitions the blob to the Cool tier using the `tierToCool` action.
- 3The lifecycle rule transitions the blob to the Archive tier using the `tierToArchive` action.
- 4The lifecycle rule permanently deletes the blob using the `delete` action.
Answer
The correct chronological order starts with uploading the blob to the Hot tier, followed by transitioning it to the Cool tier (`tierToCool`), then transitioning it to the Archive tier (`tierToArchive`), and finally permanently deleting the blob (`delete`).
The correct chronological sequence for optimizing costs moves the blob from the Hot tier (initial upload) to the Cool tier (`tierToCool`), then to the Archive tier (`tierToArchive`), and lastly to the deleted state (`delete`). This aligns with the progressive decline in storage tier costs and access frequencies.
Step-by-Step Solution
Key Concept
Azure Storage Lifecycle Management allows automatic transitioning of blobs to cooler storage tiers (Hot to Cool, Cool to Archive) and deletion based on age rules.