Archiving Log Files for App1 | Recommended Storage Solution

Recommended Storage Solution for Archiving Log Files

Question

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?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

A

Immutable storage for Azure Blob storage enables users to store business-critical data objects in a WORM (Write Once, Read Many) state.

Immutable storage supports:

Time-based retention policy support: Users can set policies to store data for a specified interval. When a time-based retention policy is set, blobs can be created and read, but not modified or deleted. After the retention period has expired, blobs can be deleted but not overwritten.

https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-immutable-storage

Design a Business Continuity Strategy

To archive the log files generated by App1, we need a storage solution that can store data for a long period, provide read access to the files, and ensure that the files are not modified during storage.

Option A: Use an Azure Blob storage account and a time-based retention policy Azure Blob storage is a highly scalable and durable storage service for unstructured data such as text or binary data, including log files. We can configure a Blob storage account to store the log files and use a time-based retention policy to ensure that the files are not deleted for at least five years. This option also provides read access to the files.

Option B: Ingest the log files into an Azure Log Analytics workspace Azure Log Analytics is a service that collects and analyzes log data from various sources, including applications. We can ingest the log files generated by App1 into a Log Analytics workspace and query them using the Log Analytics query language. However, this option does not provide long-term storage for the log files, and we cannot ensure that the files are not modified.

Option C: Use an Azure Blob Storage account configured to use the Archive access tier Azure Blob Storage provides an Archive access tier that is designed for long-term data retention at a lower storage cost. We can configure a Blob storage account to use the Archive access tier to store the log files and set a retention policy to ensure that the files are not deleted for at least five years. However, this option has some limitations, such as higher data access costs and a longer data retrieval time. Additionally, we need to move the files to the Hot or Cool access tier before reading them.

Option D: Use an Azure file share that has access control enabled Azure File storage provides a fully managed file share service that can be accessed from anywhere using the Server Message Block (SMB) protocol. We can create an Azure file share and configure access control to ensure that only App1 has read access to the log files. However, this option does not provide long-term data retention or ensure that the files are not modified.

Conclusion: Option A (Use an Azure Blob storage account and a time-based retention policy) is the best solution for archiving the log files generated by App1. This option provides long-term data retention, read access to the files, and ensures that the files are not modified during storage.