AZ-104 Implement and Manage Storage Practice Question
A blob was moved to the Archive tier last month. A project team now needs the file available later today, and they expect to read it several times during review. What should the administrator do first?
⚠ Common exam trap
Candidates often assume changing the tier directly (e.g., to Cool) makes the blob instantly accessible, but in reality, any tier change from Archive triggers a rehydration process with significant latency, and only high-priority rehydration guarantees availability within an hour.
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
✓
Start a rehydration request and move the blob to the Hot tier with high priority.
A blob in the Archive tier is offline and must be rehydrated (changed to Hot or Cool) before it can be accessed. Using high-priority rehydration ensures the blob becomes available within 1 hour, which meets the requirement for later today. The Hot tier is appropriate since the team expects to read the blob several times, providing low-latency access without incurring read costs from Cool tier.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Copy the blob directly from Archive to a local machine and reopen it there.
Why it's wrong here
A blob in the Archive tier is stored in an offline state and cannot be read, downloaded, or copied directly until it has been rehydrated to an online tier (Hot, Cool, or Cold). Any attempt to copy the archived blob to a local machine using AzCopy, the Azure portal, or the REST API will fail with an error (such as 409 or an archive-related exception) because the underlying data is not available online. Even if a copy operation were technically initiated, it would trigger the same asynchronous rehydration process internally, so this approach does not bypass the inherent retrieval latency and cannot deliver the file later today.
When this WOULD be correct
If the blob were already in a hot or cool tier (i.e., online), copying it to a local machine would be a valid first step for local access.
- ✓
Start a rehydration request and move the blob to the Hot tier with high priority.
Why this is correct
Archive data must be rehydrated before it can be read. If the team needs the file later today and will access it repeatedly, rehydrating it to Hot with high priority is the fastest practical choice.
- ✗
Change the blob to the Cool tier immediately and expect it to become available within minutes.
Why it's wrong here
Changing an archived blob's access tier to Cool is not an instantaneous operation; the Set Blob Tier request actually initiates a rehydration job, and the blob remains in the Archive state (offline) until that job completes. The rehydration process can take anywhere from one hour (high-priority) to fifteen hours (standard priority), so expecting availability 'within minutes' is fundamentally incorrect. Additionally, even if you specify Cool as the destination tier, the rehydration must first materialize the data in an online tier, and the blob's metadata will reflect a rehydrate-pending status until the operation succeeds.
When this WOULD be correct
This option would be correct if the blob were already in the Cool tier and needed to be accessed quickly, or if the question specified that the blob was in the Cool tier and the goal was to reduce costs while still maintaining reasonable access times.
- ✗
Create a lifecycle rule to move the blob back to Hot automatically on the next day.
Why it's wrong here
Lifecycle management policies in Azure Storage execute asynchronously, typically evaluating rules once per day, so a rule set to trigger 'next day' could cause a delay of up to 24 hours or more and would not satisfy an immediate retrieval need. More importantly, a lifecycle rule cannot rehydrate a blob from Archive to Hot on its own; rehydration requires an explicit Set Blob Tier operation or a copy operation with rehydration priority, and Archive blobs are offline until that job completes. Therefore, even if the rule fired, the blob would not be readable until the rehydration process finishes, making this option useless for same-day access.
When this WOULD be correct
This option would be correct if the question stated that the blob needs to be available starting tomorrow and no immediate access is required. For example: 'A blob is in the Archive tier and will be needed for a project starting next week. The administrator wants to automate the transition back to Hot tier without manual intervention.'
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.
✓Start a rehydration request and move the blob to the Hot tier with high priority.Correct answer▾
Why this is correct
Archive data must be rehydrated before it can be read. If the team needs the file later today and will access it repeatedly, rehydrating it to Hot with high priority is the fastest practical choice.
✗Copy the blob directly from Archive to a local machine and reopen it there.Wrong answer — click to see why▾
Why this is wrong here
Copying a blob directly from the Archive tier to a local machine is not possible because the blob is offline and must first be rehydrated (moved to a hot or cool tier) before it can be accessed or copied.
★ When this WOULD be the correct answer
If the blob were already in a hot or cool tier (i.e., online), copying it to a local machine would be a valid first step for local access.
Why candidates choose this
Candidates may think that copying from Archive is as straightforward as copying from any other tier, not realizing that Archive blobs are offline and require rehydration first.
✗Change the blob to the Cool tier immediately and expect it to become available within minutes.Wrong answer — click to see why▾
Why this is wrong here
Changing a blob to the Cool tier does not immediately make it available; Archive blobs must be rehydrated first, which can take hours. The Cool tier also has a higher latency than Hot, and the question requires availability later today with multiple reads, making Hot with high priority rehydration the correct choice.
★ When this WOULD be the correct answer
This option would be correct if the blob were already in the Cool tier and needed to be accessed quickly, or if the question specified that the blob was in the Cool tier and the goal was to reduce costs while still maintaining reasonable access times.
Why candidates choose this
Candidates may think that changing the access tier directly is sufficient, not realizing that Archive blobs require an explicit rehydration step before they can be read. They might also underestimate the time needed for rehydration and assume Cool tier access is fast enough.
✗Create a lifecycle rule to move the blob back to Hot automatically on the next day.Wrong answer — click to see why▾
Why this is wrong here
Creating a lifecycle rule to move the blob back to Hot automatically on the next day does not meet the immediate need for the file to be available later today. Lifecycle rules run once per day, so the blob would not be available until the next day at the earliest.
★ When this WOULD be the correct answer
This option would be correct if the question stated that the blob needs to be available starting tomorrow and no immediate access is required. For example: 'A blob is in the Archive tier and will be needed for a project starting next week. The administrator wants to automate the transition back to Hot tier without manual intervention.'
Why candidates choose this
Candidates may think that lifecycle rules can be used to schedule the rehydration, but they overlook that lifecycle rules run only once per day and cannot provide immediate access.
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
| Tier | Storage Cost | Retrieval Cost | Latency | Use Case |
|---|---|---|---|---|
| Hot | Highest | Lowest | Immediate | Active data, frequent reads |
| Cool | Lower | Higher | Immediate | Data accessed < once / month |
| Cold | Lower still | Higher | Immediate | Data accessed < once / quarter |
| Archive | Lowest | Highest + rehydration delay | Hours | Long-term compliance retention |
Go deeper
Related to this question
Learn chapter
Azure Files and Azure File Sync
Key term
Hot tier
Hot tier is a storage category used for data that is accessed frequently and needs fast retrieval, typically stored on high-performance hardware like SSDs.
Key term
Cool tier
Cool tier is a low-cost, online-only storage access tier in Microsoft Azure Blob Storage designed for data that is infrequently accessed and stored for at least 30 days.
About these practice questions
This AZ-104 question is part of Courseiva's 1,049-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
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.