Using Azure Blob Storage Lifecycle Policy
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You have an Azure subscription that contains an Azure Storage account.
You plan to implement changes to a data storage solution to meet regulatory and compliance standards.
Every day, Azure needs to identify and delete blobs that were NOT modified during the last 100 days.
Solution: You apply an Azure Blob storage lifecycle policy.
Does this meet the goal?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B.A
Azure Blob storage lifecycle management offers a rich, rule-based policy for GPv2 and Blob storage accounts. Use the policy to transition your data to the appropriate access tiers or expire at the end of the data's lifecycle.
The lifecycle management policy lets you:
-> Transition blobs to a cooler storage tier (hot to cool, hot to archive, or cool to archive) to optimize for performance and cost
-> Delete blobs at the end of their lifecycles
-> Define rules to be run once per day at the storage account level
-> Apply rules to containers or a subset of blobs (using prefixes as filters)
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-lifecycle-management-concepts?tabs=azure-portalThe proposed solution of applying an Azure Blob storage lifecycle policy does meet the stated goal of identifying and deleting blobs that were not modified during the last 100 days. Therefore, the answer is A - Yes.
An Azure Blob storage lifecycle policy is a rule set that defines when blobs in a storage account are automatically moved to a different tier or deleted. It allows you to automate blob management, reduce storage costs, and optimize performance. You can configure the policy to apply to specific containers or to the entire storage account.
In this scenario, the requirement is to delete blobs that have not been modified in the last 100 days. This can be achieved by creating a lifecycle policy that specifies the condition for blob deletion. For example, you could create a policy that identifies blobs that have not been modified for 100 days and then deletes them automatically.
To create a lifecycle policy, you can use the Azure Portal, Azure PowerShell, Azure CLI, or Azure Storage REST API. The policy can be based on various conditions, such as blob age, access tier, or custom metadata. Once the policy is created, it will be applied automatically to the specified containers or storage account.
In summary, applying an Azure Blob storage lifecycle policy is an effective way to meet the stated goal of identifying and deleting blobs that were not modified during the last 100 days. It is a simple and automated solution that can help you maintain compliance and reduce storage costs.
