This is especially true when it comes to cloud storage, where the costs of retaining unneeded or rarely accessed data can quickly add up. Microsoft Azure addresses this by providing Blob Lifecycle Management, a tool that allows you to set rules for the automation of blob data movement through tiers or even deletion of data at certain thresholds.
Blob Storage Tiers
Before going into the Blob Lifecycle management, it’s important to understand the three different tiers of blob storage: Hot, Cool, and Archive.
- Hot – This is the default tier. Data in this tier has the highest storage cost, but the lowest access cost. It’s best suited for data that needs to be frequently accessed.
- Cool – This tier has a lower storage cost, but higher access cost. It’s designed for data that will remain in the cool tier for at least 30 days.
- Archive – This tier has the lowest storage cost, but the highest access cost. Data in this tier is offline and not readily available. To read data in the archive tier, you must first change the tier of the blob to hot or cool. This can take several hours.
Configuring Blob Lifecycle Management
Blob Lifecycle Management enables you to transition your data to the best storage tier based on how you access it or to delete it at the end of its life cycle. Implementing it involves creating lifecycle management rules, and these can be applied at a storage account level to all blobs in your Blob storage.
Follow these simple steps to set up a lifecycle management policy using Azure portal:
- Navigate to the Azure portal and open your storage account.
- In the left menu of the storage account page, click on “Lifecycle Management”.
- Click the ‘+ Add Rule’ button and provide a name for the rule and, if desired, a description.
- Select a rule type. You can create rules for blob ‘Base Blobs’, or for blob ‘Snapshots’.
- Define filters that include or exclude blobs based on blob type and the prefix match (i.e., folder name). Not defining a filter implies that the rule applies to all blobs in the storage account.
- Set actions for block blobs based on blob’s last modification time. This includes moving blobs to cooler storage tiers or deleting blobs after they are so many days old.
- Click on ‘Add’ to save the policy.
This will automatically execute the specified actions, once the blobs have passed the defined criteria.
Conclusion
Blob Lifecycle Management is a powerful feature of Azure Storage that can help you significantly decrease your storage costs by automatically transitioning your data to the most cost-effective access tier, or even delete them at the end of their lifecycle. Remember that moving data between tiers does incur a cost, and retrieval from the cool and archive tiers also comes with increased costs and retrieval times, so it’s important to use wisely. Being aware of these nuances can help you make the most efficient use of Azure, and assist in your preparation for the AZ-104 Microsoft Azure Administrator exam.
Practice Test
True/False: You can transition blobs from one lifecycle tier to another.
- True
- False
Answer: True
Explanation: The Azure Blob storage lifecycle management policy allows you to transition blobs from one lifecycle tier to another. For example, you could move a blob from hot to cool after a certain number of days.
Which of the following Azure services would you use to configure blob lifecycle management?
- (a) Azure API Management
- (b) Azure Storage Explorer
- (c) Azure Policy
- (d) Azure Storage
Answer: (d) Azure Storage
Explanation: Blob lifecycle management in Azure is part of Azure Storage service. This service enables you to automate the lifecycle management of your blob data.
True/False: You can define actions to delete blob data after a certain period.
- True
- False
Answer: True
Explanation: With Azure Blob storage lifecycle management policy, you can configure rules to delete blob data after a specified period of inactivity.
Which kind of blob data types does the Azure Blob Storage support?
- (a) Block blobs
- (b) Append blobs
- (c) Page blobs
- (d) All of the above
Answer: (d) All of the above
Explanation: Azure Blob Storage supports block blobs, append blobs, and page blobs (disks).
Can you apply more than one lifecycle management policy to a single storage account?
- Yes
- No
Answer: No
Explanation: You can only apply one lifecycle management policy per storage account.
True/False: Lifecycle management policy rules are case sensitive.
- True
- False
Answer: False
Explanation: The lifecycle management policy rules are not case sensitive.
True/False: Lifecycle management policy does not support moving blobs automatically from cool to archive tier.
- True
- False
Answer: True
Explanation: The policy does not support moving blobs automatically from the cool tier to the archive tier.
Which of these operations does the Azure Blob Storage lifecycle management NOT support?
- (a) Delete
- (b) Tier to Cool
- (c) Tier to Archive
- (d) Rename
Answer: (d) Rename
Explanation: The Azure Blob Storage lifecycle management supports Delete, Tier to Cool, and Tier to Archive operations, but not Rename.
True/False: Azure blob lifecycle policies are set at the container level.
- True
- False
Answer: False
Explanation: In Azure, lifecycle policies apply at the storage account level, not the container level.
True/False: Azure Blob Storage lifecycle management policy rules are processed in order of their creation.
- True
- False
Answer: False
Explanation: Blob lifecycle management policy rules are not processed in order of their creation. They are processed based on a set of predetermined rules.
You can apply multiple rules within a single lifecycle management policy.
- True
- False
Answer: True
Explanation: You can configure multiple rules within a single lifecycle management policy to manage and control your blob data.
Which tier you cannot move your data to using Azure Blob Storage lifecycle management policy?
- (a) Hot tier
- (b) Cool tier
- (c) Archive tier
Answer: (c) Archive tier
Explanation: Lifecycle management policy supports moving blobs to cooler tiers (cool or archive) over time, but moving blobs automatically to archive tier is not supported.
True/False: Azure Blob Storage lifecycle management policy can filter blobs based on blob name prefixes.
- True
- False
Answer: True
Explanation: Azure Blob Storage lifecycle management policy supports filtering blobs to manage in a rule by blob name prefixes.
What is the minimum age at which you can define an action in a lifecycle management policy?
- (a) 1 day
- (b) 7 days
- (c) 30 days
- (d) 90 days
Answer: (b) 7 days
Explanation: The minimum age at which you can define an action like delete or tiering blobs in a lifecycle management policy is 7 days.
True/False: A wildcard (*) can be used in a blob name prefix filter.
- True
- False
Answer: False
Explanation: Wildcards are not supported in blob name prefix filters when defining rules in a lifecycle management policy.
Interview Questions
What is Blob Lifecycle Management in Azure?
Blob lifecycle management in Azure manages the lifecycle of blobs within a storage account. It provides the flexibility to automatically transition blobs to a cooler storage tier (Hot to Cool, Cool to Archive) or delete blobs after a defined period of time.
What are the blob storage tiers in Azure?
There are three storage tiers in Azure: Hot, Cool, and Archive. The Hot tier has higher storage costs but lower access costs, and it is for data that is accessed often. The Cool tier has lower storage costs but higher access costs, and it’s for data that is infrequently accessed and stored for at least 30 days. The Archive tier has the lowest storage costs but the highest access costs, and it’s for data that is rarely accessed and stored for at least 180 days.
Can you move a blob from the Archive tier back to the Hot or Cool tiers?
Yes, you can move data back from the Archive tier to the Hot or Cool tiers. However, the data must be rehydrated which can be a lengthy process, and associated costs will apply.
How do you create a lifecycle management policy in Azure?
A lifecycle management policy is created in the Azure Portal by navigating to the storage account where you wish to apply the policy, selecting Lifecycle Management from the Blob Service menu, and then using the rule editor to define the policy.
Is there a cost associated with Blob Lifecycle Management in Azure?
No, there is no additional cost for using the Blob Lifecycle Management feature. However, there may be costs associated with data transfer between different tiers or deletion of data.
What is the minimum age a blob must be before it can be transitioned to a different tier or deleted by a rule in Azure Blob Lifecycle Management?
The minimum age a blob must be before a rule can apply is 1 day.
Can you apply multiple rules to the same set of blobs in Azure Blob Lifecycle Management?
Yes, multiple rules can be applied to the same set of blobs as long as the actions of those rules do not conflict.
How can you control which blobs a rule applies to in Azure Blob Lifecycle Management?
Rules can be scoped to all blobs in the storage account, a specific container, or a set of blobs that have a specific prefix.
When are the actions in a rule executed in Azure Blob Lifecycle Management?
The actions in a rule are executed once a day.
Can a blob that’s currently being rehydrated be read or modified?
No, a blob that’s currently being rehydrated from the Archive tier to the Hot or Cool tier cannot be read or modified until the rehydration process is complete.
What happens if a blob is deleted before the minimum retention period set by a rule in Azure Blob Lifecycle Management?
If a blob is deleted before the minimum retention period set by a rule, there are no additional charges beyond regular delete operation costs.
Can a blob be moved directly from the Hot tier to the Archive tier in Azure Blob Lifecycle Management?
Yes, a blob can be moved directly from the Hot tier to the Archive tier. However, it’s generally more cost-effective to move a blob to the Cool tier before transitioning to the Archive tier.
What is the purpose of the “filter” in a rule in Azure Blob Lifecycle Management?
A “filter” in a rule allows for the selection of a subset of blobs to which the rule applies. This can be based on the blob’s prefix.
Can Microsoft Azure Blob Storage lifecycle management move a blob from Archive tier back to Cool or Hot tier automatically?
No. Blobs in the Archive tier must be manually rehydrated back to the Cool or Hot tier. Automated lifecycle management rules can only move blobs to a cooler tier (Hot to Cool, or Cool to Archive), not the other way around.
Can I edit an existing lifecycle management rule in Azure Blob Storage?
Yes, existing lifecycle management rules can be edited at any time. Changes will take effect within 24 hours.
extutorials.com