Exam AZ-305 topic 2 question 38 discussion

I believe the given answer is correct. The key here is that File1.txt is changed every hour. Theoretically, you can do this with B as well but you need to configure a given time when the snapshot is taken. With blob versioning, you have access to 24 versions, and you can restore for example a version that took place 6 hours ago as opposed to when the blob snapshot took place (you will only have a single version, the one that the snapshot captured at the moment it was taken). For this reason I would go with D.

Couldn't be more obvious to me. Versioning. File is uploaded every hour and we need to make sure we can restore the last upload. Snapshots are daily, a restore after 11pm would mean you'd miss out on the last 23 uploads. Question is pants but the answer is still clear.

Blob versioning will use more storage space than Snapshots. Log file is cumulative, so with versioning will be storing larger and larger versions every hour. Daily snapshot taken at appropriate time will only have the final file of the day. Whether keep data Hot or move to Cool, there will be less data with snapshot approach. No requirement to restore each version; only the final file of the day. Log file 1h to 23h is of no interest. LifeCycle Policy can only delete versions created n days ago; it can't skip versions. If rule is to delete versions older than a day, you'll end up deleting all versions of the file1.txt including the one we want to keep for 30 days.

Because blob snapshot is for backing up, so blob versioning will be a good choice for roll back to a previous version of File1.txt

D is correct

What happens after midnight when file1 gets deleted in order to be reset to empty in order to store transaction data for the current day only? There is not indication that policies will be created to store a snaphot in cheaper tier after the last change of the day. It seems like it would be a hassle to dig through the changes to get the last version of the file for a particular day.

I believe option D. Also, spoke to chat about it in comparison of minimize storage space: Why Blob Versioning Minimizes Storage: Versioning only stores a copy when the blob is modified, unlike snapshots which can be more space-intensive due to frequent captures. Retention policies can be configured with versioning to automatically delete older versions (e.g., after 30 days), helping to control storage space over time. Conclusion: Blob Versioning is the better choice for minimizing storage space, as it optimizes storage by only keeping changes between versions and can automatically prune older versions according to a defined retention period. This makes it more storage-efficient compared to snapshots. So, blob versioning remains the best solution for this scenario, as it balances the need for version recovery and storage efficiency.

with blob snapshot we can fulfill the requirement of keeping the last version of the file of a particular day while minimizing storage space.

D. Blob Versioning Justification: Blob Versioning: Automatically keeps previous versions of an object when it is overwritten, enabling you to restore any version within the retention period. Storage Efficiency: Only stores the changes, minimizing the additional storage required.

Solution must minimize storage space... Versioning for sure. Snapshots every hour would cause a lot of administrative load to manage storage space consumption.

It says "cumulative transaction log file named File1.txt " means last file updated will have all the changes happened every hour. Taking snapshot of the last updated file at midnight will suffice the requirement. Answer B

I feel B is thr right answer. Reasons: We need only the last updated version for each day, so taking snapshot of a day at midnight would be sufficient. Secondly, we need to minimise storage space. versioning will make 24 versions for each day. Lifecycle mgmt rules can easily delete the snapshot after 30 days.

I will go with blob-versioning for the reason that version optimizes storage by additionally storing the delta and not the entire data as in case of snapshots

Storage space: Blob versioning and daily snapshots both consume storage space, but blob versioning might consume more space if there are frequent changes to the blob. Daily snapshots only create one copy of the blob per day, while blob versioning creates a new version every time the blob is modified or deleted. Therefore, blob versioning might be more suitable for blobs that are rarely changed, while daily snapshots might be more suitable for blobs that are frequently changed. It is a very circumstantial question, I do not feel that enough information is provided. Copilot suggests Versioning would be the best option, but it is a terrible question.

I will vote for B here, as the requirement is to minimize storage costs and also states it is only needed to archive the *last uploaded version* of the day. I am not aware of a native solution to schedule those snapshots, but worst case we could use scheduled Azure Functions for that.

Versioning will store all 24 cumulative files daily. Instead we can do daily snapshots at the end of a day as it has cumulative data for the whole day. It will add administrative overhead, but reduce storage usage.