Lab — A lifecycle rule is a one-way door
AZ-104 › Unit 2 › Lab
Lab — A lifecycle rule is a one-way door
Lab brief
- AZ104-U2.T3
- 20 minutes
- A Standard_LRS storage account, a container, a lifecycle policy
- required
- Core
The claim to make physical: a lifecycle policy can put a blob into archive and cannot bring it back. Also that the rule you just wrote does nothing for up to a day.
Before you start
A subscription and one small Standard_LRS account. Do not upload anything large; a few kilobytes demonstrates every behaviour here.
Walkthrough
A lifecycle rule is a one-way door
1. Create the account, container and a blob
Standard_LRS again, one container, one small blob. Read its access tier — it is Hot.
Did it teach you what it was meant to?
A lifecycle rule archived 40 TB of footage. The business now needs one file back this afternoon. What does step 5 tell you?
You added a rule an hour ago and nothing has moved. What is the most likely explanation?
What goes wrong
Tear it down
Run this whether or not the lab worked. Everything above was chosen to cost approximately nothing, and leaving it in place is how approximately nothing becomes something.
Teardown
Delete the policy, then the resource group
Remove the management policy, then az group delete. If a blob is still in archive, deleting the whole account is the cleanest exit — the early-deletion charge on a few kilobytes is negligible, which is precisely why this lab used a tiny blob.
Where these figures come from
Every figure above was read from the raw documentation below on the day this sheet was written. The sha1 is git hash-object over the bytes as fetched, so a doc that changes underneath this sheet can be detected rather than assumed.
| Document | sha1 |
|---|---|
| Configure a lifecycle management policy | 17df3a6d6b25 |
| Optimize costs by automatically managing the data lifecycle | a6e60139abfb |
| Access tiers for blob data | 78c82ab0e7da |
| Soft delete for blobs | c0acd68a6998 |