Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You have an Azure Storage v2 account named storage1.
You plan to archive data to storage1.
You need to ensure that the archived data cannot be deleted for five years. The solution must prevent administrators from deleting the data.
Solution: You create a file share and snapshots.
Does this meet the goal?
Click on the arrows to vote for the correct answer
A. B.B
Instead you could create an Azure Blob storage container, and you configure a legal hold access policy.
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-immutable-storageThe proposed solution of creating a file share and snapshots does not meet the goal of ensuring that archived data cannot be deleted for five years and prevent administrators from deleting the data.
Snapshots are point-in-time copies of files that can be used to restore the file to a previous state. However, snapshots do not prevent the file from being deleted, and they can be deleted themselves. Therefore, relying on snapshots alone does not ensure that data cannot be deleted.
Additionally, file shares in Azure Storage are not designed to provide write-once-read-many (WORM) functionality, which is typically required for compliance and regulatory purposes. File shares can be deleted by administrators, and they do not have built-in protection against accidental or intentional deletion.
To meet the goal of ensuring that archived data cannot be deleted for five years and prevent administrators from deleting the data, a better solution would be to use Azure Blob Storage with a retention policy. The retention policy can be configured to prevent data from being deleted for a specified period of time, and it cannot be changed or removed by anyone, including administrators. This provides the required WORM functionality to comply with regulations and prevent data loss.