Azure Blob Storage Archive Tier Lifecycle Policy
Short answer
B Create a lifecycle policy with tierToArchive and daysAfterModificationGreaterThan set to 0.
Question
Key Takeaways
Configuring a lifecycle policy with tierToArchive and daysAfterModificationGreaterThan set to 0 ensures blobs are eligible for archiving immediately after modification.
Azure Blob Storage lifecycle management policies automate moving data to the archive tier. This page establishes that setting daysAfterModificationGreaterThan to 0 ensures blobs are moved to archive immediately upon creation.
Common mistake: Choosing Option D because of a mistaken belief that daysAfterModificationGreaterThan requires a minimum of 1 day, when 0 is actually a valid value for immediate eligibility.
Expert Analysis
Why the Answer Is Correct
Creating a lifecycle management policy with thetierToArchive action and setting daysAfterModificationGreaterThan to 0 makes blobs eligible for archiving immediately after they are created or modified. This directly fulfills the requirement to ensure data copied to the Blob Storage is moved to the archive tier as soon as possible. The value 0 indicates that no days need to pass after the modification for the policy to apply.Why the Other Options Are Wrong
Options A and C use headers related to immutability policies (x-ms-immutability-policy-mode and x-ms-immutability-policy-until-date), which are for WORM (Write Once, Read Many) storage and legal holds, not for access tiering. Option D uses a blobIndexMatch filter, which would only apply the policy to blobs with specific index tags, failing the requirement to move all copied data to the archive tier.Community Comment Notes
Some community members debated whetherdaysAfterModificationGreaterThan can be set to 0. As overhill noted, the value indicating the age in days after last modification can indeed be 0, meaning immediate eligibility. Another commenter suggested "B would require at least 1 day to reach the threshold", but official documentation confirms that 0 is a valid and supported value for this property to trigger immediate tiering. Official Reference
https://learn.microsoft.com/en-us/azure/storage/blobs/lifecycle-management-overview
This link opens the official vendor documentation in a new tab.
Exam Strategy
When asked to automatically tier blobs immediately upon creation, look for lifecycle management policies with daysAfterModificationGreaterThan set to 0. Do not confuse tiering actions with immutability policy headers or blob index tag filters unless explicitly specified.
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 4 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 4
-
Vichu_1607 👍 2 Answered BB. Create a lifecycle policy with an action of tierToArchive and configure daysAfterModificationGreaterThan for 0.
-
overhill 👍 1I 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
-
cmmr 👍 1B 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
-
overhill 👍 1First question I see without a single comment.. Well I also think B is the answer but I'm not sure at all
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.