A compliance team wants newly uploaded monthly reports to remain in the Hot tier for 90 days and then move automatically to a cheaper online tier without becoming offline. Which two configurations should the administrator use? Select two.

Transition the blobs to Archive after 90 days so they cost less than Cool.

Archive would make the reports offline and introduce rehydration delay, which the requirement explicitly rejects.

Use file share snapshots because lifecycle rules do not apply to blobs.

File share snapshots are for Azure Files, not Blob Storage, and they do not manage blob access tiers.

Enable soft delete on the container to change access tiers automatically.

Soft delete protects against deletion, but it does not automate tier transitions or storage-cost optimization.

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: Create a blob lifecycle management rule. — The requirement is an online, cost-optimized lifecycle for reports. Blob lifecycle management is the right feature because it applies automatic rules based on age and other conditions. Transitioning from Hot to Cool after 90 days keeps the reports immediately accessible while lowering storage costs. This meets the compliance team’s retention pattern without moving the data into an offline tier like Archive. Why others are wrong: Archive is the wrong destination because it makes objects offline and slows future access. Azure Files snapshots do not control blob tiering. Soft delete is a safety feature for accidental deletion, not a tier-management mechanism. The solution must automate online tier transitions, not just protect data from removal.

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.