AZ-104 Implement and Manage Storage Practice Question
A lifecycle rule moved quarterly audit logs to the Archive tier. An auditor now needs one blob for an urgent investigation and wants it available for download as soon as the rehydration completes. What should the administrator do?
⚠ Common exam trap
Candidates often assume changing the tier to Cool allows immediate download, but they overlook that rehydration from Archive is always required and takes time, regardless of the target tier.
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
✓
Change the blob access tier to Hot and wait for rehydration to finish before downloading it.
Changing the access tier of a blob from Archive to Hot initiates an asynchronous rehydration process that moves the blob data back to an online tier. Once rehydration completes, the blob becomes available for download. This is the standard method to make archived blobs accessible for immediate use.
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 tier to the client's local disk.
Why it's wrong here
Archived blobs are physically stored on offline media, so any direct copy or download to a local disk requires reading the blob data. When you invoke a download or copy operation against a blob still in Archive, Azure immediately returns HTTP 409 (BlobArchived) and transfers zero bytes, regardless of the storage account or tool used. Copying a blob to another online tier first would also require an explicit rehydrate step; there is no implicit data retrieval from archive during a client-side copy.
When this WOULD be correct
If the blob were already in an online tier (e.g., Cool) and the question asked for the fastest way to download it without changing tiers, copying directly to local disk would be correct.
- ✓
Change the blob access tier to Hot and wait for rehydration to finish before downloading it.
Why this is correct
Archive blobs are offline and must be rehydrated to an online tier before they can be read. Moving the blob to Hot is appropriate when rapid access is needed after rehydration completes. The administrator should expect a delay during rehydration, then the blob can be downloaded normally.
- ✗
Assign the blob a shorter retention policy so it becomes accessible automatically.
Why it's wrong here
Retention policies, whether via Immutable Blob Storage or lifecycle management, only specify how long a blob is retained or locked before deletion. Changing the retention period does not modify the blob's access tier, nor does it bring an archived blob back to an online state. You could delete the blob earlier, but the data remains offline and inaccessible until you explicitly set the tier to Hot or Cool and rehydration completes.
When this WOULD be correct
If a question asks how to automatically delete a blob after a specific period (e.g., for compliance or cleanup), setting a retention policy (e.g., via immutability or lifecycle management) would be correct.
- ✗
Move the blob to the Cool tier and attempt the download immediately.
Why it's wrong here
Cool tier is an online tier, but moving an archived blob to Cool triggers an asynchronous rehydration operation, not an instant state change. The Set Blob Tier request returns a 'PENDING' status, and the blob stays archived (and thus inaccessible) until Azure physically moves the data, which can take up to 15 hours with standard priority. Attempting to download before that completes will still produce HTTP 409 (BlobArchived), exactly the same as if the blob had never been moved.
When this WOULD be correct
If the question stated that the blob is currently in the Cool tier and the auditor needs it urgently, moving it to Hot tier and waiting for rehydration would be the correct approach. Alternatively, if the blob were in Archive and the requirement was to minimize cost while still allowing access within a few hours, moving to Cool tier (instead of Hot) could be correct.
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.
✓Change the blob access tier to Hot and wait for rehydration to finish before downloading it.Correct answer▾
Why this is correct
Archive blobs are offline and must be rehydrated to an online tier before they can be read. Moving the blob to Hot is appropriate when rapid access is needed after rehydration completes. The administrator should expect a delay during rehydration, then the blob can be downloaded normally.
✗Copy the blob directly from Archive tier to the client's local disk.Wrong answer — click to see why▾
Why this is wrong here
Blobs in Archive tier are offline and cannot be directly downloaded; they must first be rehydrated to an online tier (Hot, Cool, or Cold) before any download operation.
★ When this WOULD be the correct answer
If the blob were already in an online tier (e.g., Cool) and the question asked for the fastest way to download it without changing tiers, copying directly to local disk would be correct.
Why candidates choose this
Candidates may think that copying triggers rehydration or that Archive blobs are still readable, not realizing they are offline and require an explicit tier change to become accessible.
✗Assign the blob a shorter retention policy so it becomes accessible automatically.Wrong answer — click to see why▾
Why this is wrong here
Assigning a shorter retention policy does not affect the blob's access tier; Archive blobs remain offline until rehydrated, regardless of retention settings.
★ When this WOULD be the correct answer
If a question asks how to automatically delete a blob after a specific period (e.g., for compliance or cleanup), setting a retention policy (e.g., via immutability or lifecycle management) would be correct.
Why candidates choose this
Candidates may confuse retention policies with access tiers, thinking that reducing retention somehow makes data accessible sooner, when retention only controls deletion, not availability.
✗Move the blob to the Cool tier and attempt the download immediately.Wrong answer — click to see why▾
Why this is wrong here
Moving a blob from Archive to Cool tier initiates a rehydration process that can take up to 15 hours, and the blob is not accessible for download until rehydration completes. Attempting to download immediately will fail.
★ When this WOULD be the correct answer
If the question stated that the blob is currently in the Cool tier and the auditor needs it urgently, moving it to Hot tier and waiting for rehydration would be the correct approach. Alternatively, if the blob were in Archive and the requirement was to minimize cost while still allowing access within a few hours, moving to Cool tier (instead of Hot) could be correct.
Why candidates choose this
Candidates may think that Cool tier is a lower-cost tier that still allows immediate access, not realizing that rehydration from Archive to any access tier (Hot, Cool, or Archive itself) takes time.
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?”
Visual reference
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
Access Reviews in Entra ID
Key term
Blob
A blob is a large piece of unstructured data, like a photo or video, stored in the cloud with a unique identifier.
Key term
Archive tier
Archive tier is an ultra-low-cost Azure Blob Storage access tier designed for long-term retention of data that is rarely accessed and can tolerate hours of retrieval latency.
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 →
Same concept, more angles
3 more ways this is tested on AZ-104
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 lifecycle rule moved old audit logs to the Archive tier. A support engineer now needs to read one archived blob, and the download request fails with a message that the blob is archived. The engineer can wait several hours for the data to become available. What should the administrator do?
medium- A.Enable versioning on the storage account so the archived blob can be read immediately.
- ✓ B.Change the blob tier from Archive to Hot or Cool to start rehydration.
- C.Move the blob to a different container in the same storage account.
- D.Switch the storage account replication from LRS to ZRS.
Why B: Archived blobs in Azure Storage are offline and cannot be read directly. To access the data, the blob must first be rehydrated by changing its tier to Hot or Cool, which initiates an asynchronous copy of the blob data to an online tier. This process can take up to 15 hours, matching the engineer's ability to wait several hours.
Variation 2. A legal team stores scanned contracts in Blob Archive. Auditors will need to open several files next week for about five days and then the documents should return to the lowest practical storage cost. Which two actions should the administrator plan? Select two.
hard- A.Download the blobs directly from Archive with a normal read operation.
- ✓ B.Initiate a rehydration to the Cool tier before the review window.
- C.Set the blobs to the Hot tier permanently as soon as the review starts.
- ✓ D.Move the blobs back to Archive after the review window ends.
- E.Change the storage account redundancy to RA-GRS so the files can be read.
Why B: Blobs in the Archive tier are offline and cannot be read directly; they must first be rehydrated to a hot or cool tier. Rehydrating to the Cool tier is appropriate for a five-day access window and avoids the higher cost of the Hot tier. After the review, moving the blobs back to Archive (Option D) ensures the lowest practical storage cost for long-term retention.
Variation 3. A 180-GB blob is in the Archive tier. A legal team needs the file available later today and expects to open it several times during review. Which two actions should the administrator take? Select two.
hard- ✓ A.Initiate rehydration of the blob to the Hot tier.
- B.Leave the blob in Archive and rely on first access to trigger rehydration.
- ✓ C.Choose High priority rehydration.
- D.Copy the blob to a new container and keep it in Archive.
- E.Apply a lifecycle rule that moves the blob to Cool after rehydration completes.
Why A: To make the 180-GB blob available for frequent reads later today, the administrator must explicitly rehydrate it from Archive to an online tier. Hot tier is appropriate because it is optimized for high access rates. Since the blob is needed later today, High priority rehydration should be chosen to speed up availability (approximately 1 hour, versus up to 15 hours for Standard priority). Therefore, the correct actions are A (initiate rehydration to Hot) and C (choose High priority).
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.