Question 673 of 997

Develop for Azure storage →mediumMultiple ChoiceObjective-mapped

Quick Answer

The correct solution is to create a lifecycle management policy with two rules: tier to Cool after 90 days and delete after 365 days. This works because Azure Blob Storage lifecycle management policies allow you to automate blob tiering and deletion based on blob age, requiring no custom code or recurring jobs—the policy engine runs continuously in the background, evaluating all blobs against your defined conditions. On the AZ-204 exam, this scenario tests your understanding of managing Azure Blob Storage lifecycle, often appearing as a cost-optimization question where developers must avoid manual scripts or scheduled tasks. A common trap is trying to use Azure Functions or Logic Apps for this, but the exam expects you to recognize that lifecycle management is the fully managed, no-code solution. Memory tip: think "90 Cool, 365 Gone" to remember the tiering and deletion thresholds.

AZ-204 Practice Question: Blob lifecycle management for automatic tiering…

This AZ-204 practice question tests your understanding of develop for azure storage. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. A key principle to apply: blob Storage lifecycle management policy. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Audit logs are written daily as block blobs to an Azure Storage account. Logs older than 90 days must move to Cool tier automatically; logs older than 365 days must be deleted. The developer wants to implement this with no custom code and no recurring jobs. What is the correct solution?

Question 1mediummultiple choice

Full question →

A
Create a lifecycle management policy with two rules: tier to Cool after 90 days and delete after 365 days
Lifecycle management policies are evaluated nightly by Azure. The two rules (tier after 90 days, delete after 365 days) are declared in JSON and applied to blobs matching the prefix filter. No code is required — the storage service acts on them automatically.
B
Write an Azure Function with a Timer trigger that lists all blobs, checks last-modified dates, and tiers or deletes them via the SDK
Why wrong: This approach works but introduces unnecessary complexity — custom code, a Function App, and trigger configuration to maintain. Lifecycle management policies accomplish exactly this without any code.
C
Enable Blob versioning and set a version retention policy of 365 days
Why wrong: Blob versioning retains deleted or overwritten versions for a retention period. It does not move blobs between tiers based on age, and it does not delete blobs after 365 days based on their creation time.
D
Configure a Logic App with a Recurrence trigger to enumerate and process blobs weekly
Why wrong: Like the Function approach, this requires external orchestration and custom logic. Lifecycle management is the native, zero-code alternative that runs on the storage service itself.

Full breakdown with real-world context →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Create a lifecycle management policy with two rules: tier to Cool after 90 days and delete after 365 days

Azure Blob Storage lifecycle management policies allow you to automate tier transitions and deletions based on blob age, without any custom code or recurring jobs. By defining a rule to tier blobs to Cool after 90 days and another rule to delete blobs after 365 days, the developer meets all requirements with a fully managed, no-code solution.

Key principle: Blob Storage lifecycle management policy

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
Create a lifecycle management policy with two rules: tier to Cool after 90 days and delete after 365 days
Why this is correct
Lifecycle management policies are evaluated nightly by Azure. The two rules (tier after 90 days, delete after 365 days) are declared in JSON and applied to blobs matching the prefix filter. No code is required — the storage service acts on them automatically.
Related concept
Blob Storage lifecycle management policy
✗
Write an Azure Function with a Timer trigger that lists all blobs, checks last-modified dates, and tiers or deletes them via the SDK
Why it's wrong here
This approach works but introduces unnecessary complexity — custom code, a Function App, and trigger configuration to maintain. Lifecycle management policies accomplish exactly this without any code.
✗
Enable Blob versioning and set a version retention policy of 365 days
Why it's wrong here
Blob versioning retains deleted or overwritten versions for a retention period. It does not move blobs between tiers based on age, and it does not delete blobs after 365 days based on their creation time.
✗
Configure a Logic App with a Recurrence trigger to enumerate and process blobs weekly
Why it's wrong here
Like the Function approach, this requires external orchestration and custom logic. Lifecycle management is the native, zero-code alternative that runs on the storage service itself.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may overlook the 'no custom code and no recurring jobs' constraint and choose a serverless compute option (Azure Function or Logic App) instead of the built-in lifecycle management policy, which is the only fully managed, no-code solution.

Detailed technical explanation

How to think about this question

Lifecycle management policies in Azure Storage are evaluated once per day and apply to both block blobs and append blobs. The policy uses the `lastModifiedTime` or `creationTime` (for append blobs) to calculate age, and actions like `tierToCool` and `delete` are executed asynchronously. A common real-world scenario is managing audit logs where compliance requires automated tiering and deletion without manual intervention or compute costs.

KKey Concepts to Remember

Blob Storage lifecycle management policy
Cool tier
automatic tiering
cost optimization

TExam Day Tips

Watch for words such as best, first, most likely and least administrative effort.
Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Blob Storage lifecycle management policy

Real-world example

How this comes up in practice

A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.

What to study next

Got this wrong? Here's your next step.

Review blob Storage lifecycle management policy, then practise related AZ-204 questions on the same topic to reinforce the concept.

Related AZ-204 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Develop Azure compute solutions practice questions

Practise AZ-204 questions linked to Develop Azure compute solutions.

Develop for Azure storage practice questions

Practise AZ-204 questions linked to Develop for Azure storage.

Implement Azure security practice questions

Practise AZ-204 questions linked to Implement Azure security.

Connect to and consume Azure services and third-party services practice questions

Practise AZ-204 questions linked to Connect to and consume Azure services and third-party services.

Monitor, troubleshoot, and optimize Azure solutions practice questions

Practise AZ-204 questions linked to Monitor, troubleshoot, and optimize Azure solutions.

AZ-204 fundamentals practice questions

Practise AZ-204 questions linked to AZ-204 fundamentals.

AZ-204 scenario practice questions

Practise AZ-204 questions linked to AZ-204 scenario.

AZ-204 troubleshooting practice questions

Practise AZ-204 questions linked to AZ-204 troubleshooting.

Practice this exam

Start a free AZ-204 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

10 questions 20 questions 30 questions 50 questions Timed 30

AZ-204 practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this AZ-204 question test?

Develop for Azure storage — This question tests Develop for Azure storage — Blob Storage lifecycle management policy.

What is the correct answer to this question?

The correct answer is: Create a lifecycle management policy with two rules: tier to Cool after 90 days and delete after 365 days — Azure Blob Storage lifecycle management policies allow you to automate tier transitions and deletions based on blob age, without any custom code or recurring jobs. By defining a rule to tier blobs to Cool after 90 days and another rule to delete blobs after 365 days, the developer meets all requirements with a fully managed, no-code solution.

What should I do if I get this AZ-204 question wrong?

Review blob Storage lifecycle management policy, then practise related AZ-204 questions on the same topic to reinforce the concept.

What is the key concept behind this question?

Blob Storage lifecycle management policy

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on AZ-204

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. Your company stores backup files in an Azure Blob Storage account. These files are written once and then need to be retained for 7 years. During the first year, the files are accessed weekly. After the first year, they are accessed rarely (once per month). You want to minimize storage costs. Which combination of access tiers and lifecycle management should you apply?

medium

A.Store in Hot tier and move to Cool after 1 year, then to Archive after 7 years.
✓ B.Store in Cool tier and move to Archive after 1 year.
C.Store directly in Archive tier and rehydrate to Cool when needed for access.
D.Store in Hot tier and move to Archive after 90 days.

Why B: Option B is correct because it minimizes costs by storing files in the Cool tier from the start (matching the initial weekly access pattern) and then moving them to the Archive tier after one year when access drops to monthly. The Cool tier offers lower storage cost than Hot for infrequent access, and the Archive tier provides the lowest storage cost for data that is rarely accessed and can tolerate a retrieval latency of up to 15 hours. This lifecycle policy aligns with the 7-year retention requirement without incurring unnecessary early deletion charges or rehydration costs.

Keep practising

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.