Courseiva
Implement and Manage StorageeasyMultiple ChoiceObjective-mapped

AZ-104 Implement and Manage Storage Practice Question

A monthly report file must automatically move to a cheaper online tier after 90 days in Azure Blob Storage. Which feature should the administrator configure?

⚠ Common exam trap

A common mix-up: candidates confuse 'archive rehydration' (which moves data from Archive to a cheaper tier? No, it moves to an online tier) with lifecycle management, or think snapshot retention can handle tiering, but snapshots are only for versioning and recovery, not cost-based tier transitions.

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

Blob lifecycle management

Blob lifecycle management is the correct feature because it allows administrators to define rules that automatically transition blobs to a cheaper access tier (e.g., from Hot to Cool) after a specified number of days. This policy operates at the storage account or container level and can move data to the Cool or Archive tier based on age, meeting the requirement of moving the report file after 90 days without manual intervention.

Answer analysis

Option-by-option breakdown

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

  • Blob lifecycle management

    Why this is correct

    Blob lifecycle management is the correct answer because a lifecycle management policy can automatically transition blobs from hot to cool or cool to archive based on the last modification date, with rules filtered by prefix or blob index tags. This minimizes manual administrative effort and operational cost by enforcing tier changes on a schedule without requiring operator intervention.

  • Archive rehydration policy

    Why it's wrong here

    Archive rehydration policy is incorrect for this scenario because rehydration is the process of moving an archived blob back to an online hot or cool tier before it can be read; it is used after data already costs the least possible amount. Auto-rehydration only affects retrieval speed and cost, not progression to cheaper storage, and it would increase rather than decrease storage cost if applied to a monthly report.

    When this WOULD be correct

    An administrator needs to retrieve archived data for immediate access and must configure the priority and duration of the rehydration process.

  • Snapshot retention

    Why it's wrong here

    Snapshot retention is incorrect for this requirement because blob snapshots are immutable point-in-time versions of a blob, primarily used for data protection against overwrites or corruption. Retaining snapshots may incrementally increase storage consumption and cost, but it never changes the access tier of the underlying blob or of the snapshot itself.

    When this WOULD be correct

    A question asking how to automatically delete old snapshots of blobs after a specified number of days to reduce storage costs would have snapshot retention as the correct answer.

  • Storage account failover

    Why it's wrong here

    Storage account failover is incorrect because failover is an account-level disaster recovery action that redirects the entire storage endpoint from the primary to a secondary region during a regional outage. It does not evaluate individual blob metadata or change access tiers, so it cannot automatically move a monthly report to cheaper storage.

    When this WOULD be correct

    An administrator needs to ensure that if the primary region becomes unavailable, the storage account automatically switches to a paired secondary region to maintain availability. In that scenario, configuring storage account failover would be the correct answer.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.

Blob lifecycle managementCorrect answer

Why this is correct

Blob lifecycle management is the correct answer because a lifecycle management policy can automatically transition blobs from hot to cool or cool to archive based on the last modification date, with rules filtered by prefix or blob index tags. This minimizes manual administrative effort and operational cost by enforcing tier changes on a schedule without requiring operator intervention.

Archive rehydration policyWrong answer — click to see why

Why this is wrong here

Archive rehydration policy is used to change the access tier of a blob from Archive to a hot or cool tier, not to automatically move blobs to a cheaper tier after a set period.

★ When this WOULD be the correct answer

An administrator needs to retrieve archived data for immediate access and must configure the priority and duration of the rehydration process.

Why candidates choose this

Candidates may confuse 'rehydration' (changing from archive to hot/cool) with 'lifecycle management' (moving between tiers over time), as both involve tier changes.

Snapshot retentionWrong answer — click to see why

Why this is wrong here

Snapshot retention manages the lifecycle of blob snapshots, not the tiering of the base blob itself. The question requires moving the base blob to a cheaper tier after 90 days, which is not controlled by snapshot retention.

★ When this WOULD be the correct answer

A question asking how to automatically delete old snapshots of blobs after a specified number of days to reduce storage costs would have snapshot retention as the correct answer.

Why candidates choose this

Candidates may confuse snapshot retention with lifecycle management because both involve time-based policies, but snapshot retention specifically targets snapshots, not the base blob's tier.

Storage account failoverWrong answer — click to see why

Why this is wrong here

Storage account failover is a disaster recovery feature that switches the primary region to a secondary region, not a data tiering or cost optimization feature. It does not move blobs to cheaper tiers based on age.

★ When this WOULD be the correct answer

An administrator needs to ensure that if the primary region becomes unavailable, the storage account automatically switches to a paired secondary region to maintain availability. In that scenario, configuring storage account failover would be the correct answer.

Why candidates choose this

Candidates may confuse failover with lifecycle management because both involve automatic actions on storage accounts, but failover is about regional redundancy, not cost-efficient data movement.

Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Quick reference

Azure Blob Storage Tier Comparison

TierStorage CostRetrieval CostLatencyUse Case
HotHighestLowestImmediateActive data, frequent reads
CoolLowerHigherImmediateData accessed < once / month
ColdLower stillHigherImmediateData accessed < once / quarter
ArchiveLowestHighest + rehydration delayHoursLong-term compliance retention

About these practice questions

One of 1,049 original AZ-104 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This AZ-104 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-104 exam.