Question 150 of 999

Design data storage solutions →mediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to move to Cool tier after 1 day and then to Archive after 30 days. This policy directly aligns with the access pattern of IoT data, which is written frequently but rarely accessed after the first 24 hours, so moving it to Cool immediately after that window reduces costs without incurring unnecessary write penalties. The subsequent move to Archive after 30 days satisfies the 90-day retention requirement while minimizing long-term storage expenses. On the AZ-305 exam, this scenario tests your understanding of Azure Blob Storage lifecycle management for IoT data lifecycle optimization, often appearing as a trap where candidates choose to move data to Archive too early, violating compliance. A common memory tip is to think of the "1-30-90 rule": one day to Cool, 30 days to Archive, and 90 days total retention—never move to Archive before the compliance window ends.

AZ-305 Design data storage solutions Practice Question

This AZ-305 practice question tests your understanding of design data storage solutions. 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. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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.

A company ingests IoT sensor data into Azure Blob Storage. Data is written frequently and accessed rarely after the first 24 hours. The company must retain the data for exactly 90 days for compliance. They want to minimize storage costs by automatically moving data to cheaper tiers as soon as possible. Which lifecycle management policy should they implement?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

Clue: "first"
Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
Clue: "minimum / minimize"
Why it matters: Asks for the least resource use — fewest addresses, smallest subnet, lowest overhead. Eliminate over-provisioned options even if they would technically work.

Question 1mediummultiple choice

Full question →

A
Move to Cool tier immediately (0 days) and then to Archive after 30 days
Why wrong: Lifecycle management cannot be triggered at 0 days; the minimum is 1 day. You must also satisfy the 90-day retention, which the Archive tier supports, but the immediate move to Cool is not possible.
B
Move to Cool tier after 1 day and then to Archive after 30 days
This policy moves data to Cool after 1 day (when access frequency drops) and then to Archive after 30 days, minimizing costs while meeting the 90-day retention requirement. Archive is the cheapest tier for long-term storage.
C
Move to Archive tier after 1 day
Why wrong: While the Archive tier is cheap, moving directly to Archive after 1 day is not optimal because data might still be accessed occasionally during the first 30 days, and early deletion or unnecessary retrieval costs could apply. The recommended practice is to use Cool as an intermediate tier.
D
Move to Cool tier after 30 days and to Archive after 90 days
Why wrong: This policy would keep data in the Hot tier for 30 days, incurring higher costs for the first month, and then move to Cool for the remaining 60 days. It does not leverage the low cost of Archive for the bulk of the retention period.

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

✓

Move to Cool tier after 1 day and then to Archive after 30 days

Option B is correct because it aligns with the access pattern: data is frequently accessed only in the first 24 hours, so moving to Cool tier after 1 day (when access drops) saves costs, then moving to Archive after 30 days meets the 90-day retention requirement while minimizing storage costs. The lifecycle policy must ensure data is not moved to Archive before the compliance period ends, and moving to Cool immediately (0 days) would incur unnecessary write costs for frequently written data.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

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

✗
Move to Cool tier immediately (0 days) and then to Archive after 30 days
Why it's wrong here
Lifecycle management cannot be triggered at 0 days; the minimum is 1 day. You must also satisfy the 90-day retention, which the Archive tier supports, but the immediate move to Cool is not possible.
✓
Move to Cool tier after 1 day and then to Archive after 30 days
Why this is correct
This policy moves data to Cool after 1 day (when access frequency drops) and then to Archive after 30 days, minimizing costs while meeting the 90-day retention requirement. Archive is the cheapest tier for long-term storage.
Clue confirmation
The clue words "first", "minimum / minimize" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Move to Archive tier after 1 day
Why it's wrong here
While the Archive tier is cheap, moving directly to Archive after 1 day is not optimal because data might still be accessed occasionally during the first 30 days, and early deletion or unnecessary retrieval costs could apply. The recommended practice is to use Cool as an intermediate tier.
✗
Move to Cool tier after 30 days and to Archive after 90 days
Why it's wrong here
This policy would keep data in the Hot tier for 30 days, incurring higher costs for the first month, and then move to Cool for the remaining 60 days. It does not leverage the low cost of Archive for the bulk of the retention period.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often choose Option A (move to Cool immediately) thinking it saves the most money, but they overlook the frequent write pattern and the fact that Cool tier has higher write costs, making a 1-day delay more cost-effective.

Detailed technical explanation

How to think about this question

Azure Blob Storage lifecycle management policies evaluate rules based on 'days after creation' or 'days after last modification'. The Cool tier offers lower storage costs but higher access costs, making it ideal for data accessed less than once per month, while Archive tier has the lowest storage cost but a 180-day early deletion penalty and requires rehydration (up to 15 hours) for access. In this scenario, moving to Cool after 1 day and to Archive after 30 days ensures data is in Archive for 60 days (days 31-90), maximizing cost savings while avoiding early deletion fees.

KKey Concepts to Remember

Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.

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

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related AZ-305 practice-question pages

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

Design identity, governance, and monitoring solutions practice questions

Practise AZ-305 questions linked to Design identity, governance, and monitoring solutions.

Design data storage solutions practice questions

Practise AZ-305 questions linked to Design data storage solutions.

Design business continuity solutions practice questions

Practise AZ-305 questions linked to Design business continuity solutions.

Design infrastructure solutions practice questions

Practise AZ-305 questions linked to Design infrastructure solutions.

SAA-C03 VPC practice questions

Practise AZ-305 questions linked to SAA-C03 VPC.

SAA-C03 S3 lifecycle policy questions

Practise AZ-305 questions linked to SAA-C03 S3 lifecycle policy questions.

SAA-C03 RDS Multi-AZ questions

Practise AZ-305 questions linked to SAA-C03 RDS Multi-AZ questions.

SAA-C03 IAM policy practice questions

Practise AZ-305 questions linked to SAA-C03 IAM policy.

SAA-C03 Route 53 failover questions

Practise AZ-305 questions linked to SAA-C03 Route 53 failover questions.

SAA-C03 CloudFront practice questions

Practise AZ-305 questions linked to SAA-C03 CloudFront.

SAA-C03 NAT gateway questions

Practise AZ-305 questions linked to SAA-C03 NAT gateway questions.

SAA-C03 VPC endpoint questions

Practise AZ-305 questions linked to SAA-C03 VPC endpoint questions.

Practice this exam

Start a free AZ-305 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-305 practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this AZ-305 question test?

Design data storage solutions — This question tests Design data storage solutions — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Move to Cool tier after 1 day and then to Archive after 30 days — Option B is correct because it aligns with the access pattern: data is frequently accessed only in the first 24 hours, so moving to Cool tier after 1 day (when access drops) saves costs, then moving to Archive after 30 days meets the 90-day retention requirement while minimizing storage costs. The lifecycle policy must ensure data is not moved to Archive before the compliance period ends, and moving to Cool immediately (0 days) would incur unnecessary write costs for frequently written data.

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

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Are there clue words in this question I should notice?

Yes — watch for: "first", "minimum / minimize". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

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-305

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. A company ingests IoT sensor data into Azure Blob Storage. Data is written frequently and is accessed rarely after the first 24 hours. The company must retain the data for exactly 90 days for compliance. They want to minimize storage costs by automatically moving data to the cheapest possible storage tier as soon as possible. Which Azure Blob Storage lifecycle management policy should they implement?

medium

✓ A.Move to Cool tier after 1 day, delete after 90 days
B.Move to Archive tier after 1 day, delete after 90 days
C.Move to Cool tier after 30 days, delete after 90 days
D.Move to Archive tier after 30 days, delete after 90 days

Why A: Option A is correct because the data is rarely accessed after 24 hours, so moving it to Cool tier after 1 day minimizes cost while still allowing low-latency access. The 90-day deletion aligns with the compliance retention requirement. Cool tier is the cheapest online tier, and moving data there as soon as possible (after 1 day) reduces costs without incurring the early deletion penalty or retrieval latency of Archive tier.

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-305 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-305 exam.