A 180-GB blob was moved to the Archive tier last week. A legal team now needs the file available later today for repeated review, and they are willing to pay more to shorten the wait. Which action should the administrator take first?

Rehydrate the blob to Cool tier by using Standard priority.

This eventually restores access, but Standard priority is not the fastest choice when time is critical.

Copy the blob into another Archive tier container and wait for replication.

Copying to another Archive location does not make the data readable sooner and adds no value.

Change the storage account redundancy to ZRS so the blob becomes accessible faster.

Redundancy settings do not affect Archive rehydration time or restore archived blob readability.

What does this AZ-104 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Rehydrate the blob to Hot tier by using High priority. — The administrator should start a high-priority rehydration to the Hot tier. Archive data is offline, so it cannot be read until rehydration completes. Because the team needs the blob later today and will review it repeatedly, choosing the fastest rehydration path and returning it to an online tier is the most appropriate action. High priority is intended for urgent retrieval scenarios, while Hot keeps the blob immediately usable after restoration. Why others are wrong: Cool tier rehydration is still valid, but Standard priority is slower and does not help when the file is needed the same day. Copying to another Archive container keeps the data offline, so it does not solve the access problem. Redundancy changes such as ZRS affect resiliency, not archive retrieval behavior. The issue here is offline state and recovery speed, not durability or replication.

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

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.