You are designing the disaster recovery strategy for an application.
The application uses a private blob container in a storage account named storage1. The application needs to read and write blobs in storage1 even if a disaster impacting a whole Azure region occurs.
You need to configure storage1 to maximize availability and indicate an action to perform in case of an outage.
Which redundancy option and action should you use?
You should configure Geo-redundant storage (GRS) for storage1. This redundancy option replicates the storage account to a geographically isolated region if there is a disaster that impacts an Azure region.
You should initiate a storage account failover if an outage occurs. An account failover promotes the secondary endpoint of the storage account to become the primary endpoint. Once failover is completed, the application can read and write to the new primary region and maintain high availability.
You should not configure Read-access geo-redundant storage (RA-GRS) and use the storage account secondary endpoint. Using RA-GRS and redirecting the application to use the secondary storage account endpoint solves the read availability problem. However, the secondary endpoint does not allow the application to write on the replicated blobs.
You should not configure Locally redundant storage (LRS) or Zone-redundant storage (ZRS) for storage1. These redundancy options do not replicate the storage account to a geographically isolated region.
You should not copy the files to a new storage account. If the primary region is not available, you may not be able to copy the original blobs from the storage account.