A company uses an Azure Blob Storage for archiving.
The company requires that data in the Blob Storage is only in the archive tier.
You need to ensure data copied to the Blob Storage is moved to the archive tier.
What should you do?
A company uses an Azure Blob Storage for archiving.
The company requires that data in the Blob Storage is only in the archive tier.
You need to ensure data copied to the Blob Storage is moved to the archive tier.
What should you do?
B. Create a lifecycle policy with an action of tierToArchive and configure daysAfterModificationGreaterThan for 0.
First question I see without a single comment.. Well I also think B is the answer but I'm not sure at all
I think B is the right Answer 1) Creating a lifecycle policy with TierToArchieve is necessary to move blobs to Archieve and setting daysAfterModificationGreaterThan will set the days after modification to 0. From MSFT daysAfterModificationGreaterThan: Value indicating the age in days after last modification https://learn.microsoft.com/en-us/javascript/api/@azure/arm-storage/dateaftermodification?view=azure-node-latest
B would require at least 1 day to reach the threshold. D would allow tagging blobs and immediatelly applying the tierToArchive policy. I go with D
I stand corrected: "Archive data after ingest Some data stays idle in the cloud and is rarely, if ever, accessed. The following lifecycle policy is configured to archive data shortly after it's ingested. This example transitions block blobs in a container named archivecontainer into an archive tier. The transition is accomplished by acting on blobs 0 days after last modified time." https://learn.microsoft.com/en-us/azure/storage/blobs/lifecycle-management-overview It's B
" Name: daysAfterModificationGreaterThan Description: Value indicating the age in days after last modification int Value: Constraints: Min value = 0 " https://learn.microsoft.com/en-us/azure/templates/microsoft.storage/storageaccounts/managementpolicies?pivots=deployment-language-bicep
tierToArchive: { daysAfterCreationGreaterThan: int daysAfterLastAccessTimeGreaterThan: int daysAfterLastTierChangeGreaterThan: int daysAfterModificationGreaterThan: int <-- }