You have a line-of-business (LOB) app that reads files from and writes files to Azure Blob storage in an Azure Storage account.
You need to recommend changes to the storage account to meet the following requirements:
Provide the highest possible availability.
Minimize potential data loss.
Which three changes should you recommend? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
A . From the app, query the LastSyncTime of the storage account.
B . From the storage account, enable soft deletes.
C . From the storage account, enable read-access geo-redundancy storage (RA-GRS).
D . From the app, add retry logic to the storage account interactions.
E . From the storage account, enable a time-based retention policy.
Answer: BCE
Explanation:
Soft delete protects blob data from being accidentally or erroneously modified or deleted. When soft delete is enabled for a storage account, blobs, blob versions (preview), and snapshots in that storage account may be recovered after they are deleted, within a retention period that you specify.
Geo-redundant storage (with GRS or GZRS) replicates your data to another physical location in the secondary region to protect against regional outages.
However, that data is available to be read only if the customer or Microsoft initiates a failover from the primary to secondary region. When you enable read access to the secondary region, your data is available to be read if the primary region becomes unavailable. For read access to the secondary region, enable read-access geo-redundant storage (RAGRS) or read-access geo-zone-redundant storage (RA-GZRS).
Reference:
https://docs.microsoft.com/en-us/azure/storage/blobs/soft-delete-overview
https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy#read-access-to-data-in-thesecondary-region