A company needs to store large amounts of unstructured data (log files) for analytics. The data is accessed frequently for the first 30 days, then occasionally for the next 90 days, and rarely after that but must be retained for 7 years for compliance. The data must not be modified or deleted during the retention period, and administrative access must not be able to bypass this restriction. They want to minimize storage costs. Which combination of Azure Blob Storage features should they configure?

Enable soft delete and versioning on the storage account, and use a custom script to delete blobs after 7 years. Manually move blobs to Cool and Archive tiers using Azure PowerShell.

Soft delete and versioning do not prevent all modifications and can be bypassed by administrators with proper permissions. Manual tier changes are not automated and may fail sporadically.

Set each blob's access tier to Cool on upload, then manually change to Archive after 30 days. Enable Azure Backup on the storage account for retention.

Manual tier management is not scalable and prone to human error. Azure Backup does not enforce immutability or automatically transition tiers. It only provides recovery points.

Apply a legal hold on the container to prevent deletion, and configure a lifecycle policy to move blobs to Archive after 30 days.

Legal hold does not prevent modifications, only deletion. Also, it must be removed manually after 7 years. The scenario requires both deletion and modification protection for the full period.

What does this AZ-305 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Configure a lifecycle management policy to move blobs to Cool tier after 30 days and to Archive tier after 120 days. Apply a time-based retention policy with a retention period of 2,555 days and lock it. — To meet the requirements, you need to automatically transition blobs between access tiers based on age using a lifecycle management policy, and apply a time-based retention policy to protect blobs from deletion/modification. The time-based retention policy with the 'Locked' option prevents administrators from using elevated permissions to bypass the immutability, because once locked, the policy cannot be removed or shortened. Cool and Archive tiers minimize costs.

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

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