You have an application named App1. App1 generates log files that must be archived for five years. The log files must be readable by App1 but must not be modified.
Which storage solution should you recommend for archiving?
You have an application named App1. App1 generates log files that must be archived for five years. The log files must be readable by App1 but must not be modified.
Which storage solution should you recommend for archiving?
To meet the requirement that log files must be archived for five years, readable by App1, and not modified, the best solution is to use an Azure Blob storage account with a time-based retention policy. This setup ensures that the data is stored in a Write Once, Read Many (WORM) state, allowing the log files to be read but not altered during the retention period. After the retention period expires, the blobs can be deleted but not overwritten. Azure Blob storage also supports different access tiers, providing flexibility in managing storage costs.
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-immutable-storage
A is ok
In case anybody else is wondering about the 5 years duration and if this is even possible with immutable blob storage: "The following limits apply to retention policies: The minimum retention interval is 1 day. The maximum is 146,000 days (400 years)."
A is correct answer.
Support for all blob tiers: WORM policies are independent of the Azure Blob storage tier and apply to all the tiers: hot, cool, and archive. Users can transition data to the most cost-optimized tier for their workloads while maintaining data immutability