Azure Blob Storage Archive Tier Lifecycle Policy

Develop solutions that use Azure Blob Storage

Answer Correct answer: B — Create a lifecycle policy with tierToArchive and daysAfterModificationGreaterThan set to 0.

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?

Use a Put Block List operation with a request header of x-ms-immutability-policy-mode.
Create a lifecycle policy with an action of tierToArchive and configure daysAfterModificationGreaterThan for 0. Correct Answer
Use a Put Blob operation with a request header of x-ms-immutability-policy-until-date.
Create a lifecycle policy with an action of tierToArchive and configure a filter for blobIndexMatch.

Community Votes

100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

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.

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.

Community Discussion (4 comments)

cmmr 👍 1

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

Vichu_1607 👍 2 Selected: B

B. Create a lifecycle policy with an action of tierToArchive and configure daysAfterModificationGreaterThan for 0.

overhill 👍 1

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

overhill 👍 1

First question I see without a single comment.. Well I also think B is the answer but I'm not sure at all

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

Creating a lifecycle management policy with the tierToArchive 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 whether daysAfterModificationGreaterThan 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

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.

Related Analysis

← Back to AZ-204 Study Guide