A batch job fails with a blob read error after the administrator moved a 200-GB blob to the archive tier. The file must be available again within a few hours, and the administrator wants the least disruptive recovery. What should be done?

Delete the archived blob and upload a new copy from backup.

Deleting and reuploading is more disruptive than necessary and depends on having another copy available immediately.

Enable soft delete on the storage account and retry the read operation.

Soft delete protects against deletion, but it does not bring an archived blob back online for reading.

Convert the storage account to premium performance.

Changing the account performance type does not automatically rehydrate archived data or resolve the read failure.

What does this AZ-104 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Change the blob tier to Hot or Cool and wait for the rehydration process to finish. — When a blob is moved to the Archive tier, it becomes offline and cannot be read until rehydration finishes. The correct remediation is to initiate a tier change back to Hot or Cool, optionally with a rehydration priority if speed matters. That restores access without deleting the blob or relying on a secondary copy. For a file needed within hours, this is the proper operational recovery step. Why others are wrong: Deleting and reuploading is risky and unnecessary if the archived blob still exists. Soft delete only helps after deletion, not for archive access. Changing account performance does not alter the blob's archive state, so the read error would remain until rehydration is explicitly requested.

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.