Exam AZ-305 topic 2 question 17 discussion

gpv2 hot tier, container access policy to configure a time-based retention policy for immutable storage. Storage account resource lock does not prevent data editing or deletion, but only the storage account deletion.

Answer is GPv2 HOT to have frequent access : https://docs.microsoft.com/en-us/azure/storage/blobs/access-tiers-overview Answer is container access (immutable) policy at least at the container scope. https://docs.microsoft.com/en-us/azure/storage/blobs/immutable-storage-overview

General purpose v2 with Cool access tier for blobs -The Cool tier is optimized for data that is infrequently accessed, but still needs to be available for reading. It offers lower access costs than the Hot tier and is more suitable than Archive for daily access. Archive tier is not appropriate because it has high latency and is meant for rarely accessed data. Container access policy - You can use immutability policies (via container access policy) to enforce write-once-read-many (WORM) behavior. This ensures that data cannot be modified or deleted for a specified retention period (e.g., 5 years). Resource locks only prevent deletion of the storage account or configuration changes, not individual blob modifications.

Got this on may. 02, 2025 , Score 925, the second box :container access policy

2. Container access policy the second select should be container access policy, because with access policy you're not only preventing data from deletion/modification (like what you could've done using locks) but you also can set a retention policy which is a requirement in this question

i would go for gpv2 hot tier and container access policy

1 Hot tier 2 should be access policy. PS Locking a storage account does not protect containers or blobs within that account from being deleted or overwritten!!!

I think the right choice for second question is "Container Access Level" we can adjust access level to read only

Immutability policies can be scoped to a blob version or to a container. How an object behaves under an immutability policy depends on the scope of the policy. For more information about policy scope for each type of immutability policy, see the following sections: Time-based retention policy scope Legal hold scope Depending on the scope, you can configure both a time-based retention policy and a legal hold for a resource (container or blob version).

Got this on Nov. 17, 2023

1. "Hot tier". Lower access transaction costs, meats requirement "Data access charges must be minimized" 2. "Container access policy" seems to be the best one. I still struggle to find it in the documentation (only found immutable storage references)

This question appeared on my Exam today 10/22/2023 Total of 48 questions

General purpose v2 with Hot access tier and Storage resource lock.

its general puprose v2 with hot tier container access policy

1. Storage Account type: c. GP v2 Hot. Considering the data will be accessed daily, the Hot access tier is the most cost-effective for storing frequently accessed data. 2. Configuration to prevent the modification and deletions: Container access policy. The Container access policy is indeed the place to configure Azure's Immutable Blob Storage to ensure data is retained without modifications or deletions for a specified amount of time, which suits your needs. The Azure Blob Storage's Immutable Blob Storage feature provides a WORM (Write Once, Read Many) capability which aligns with your requirements perfectly.

Moderator/Admins: could you please update the answer. We have a lot of consense here that the answers are General Purpose v2 Blobs + hot tier AND Container Access Policy are needed to get the desired outcome.

General Purpose V2 Hot tier Container access policy I would recommend using Azure hot Blob Storage with a WORM (Write Once Read Many) policy. WORM policies prevent data from being modified or deleted after it has been written, and they can be applied to individual blobs or entire containers.