A logistics company, SwiftRoute Deliveries, is designing a disaster recovery plan for its package tracking data stored in Azure Blob Storage. The solution must meet the following requirements:
- The tracking data must remain readable even if the primary Azure region experiences a complete regional outage.
- Users must be able to read data from the secondary region at any time without initiating a storage account failover.
- Storage costs must be minimized.
Which two configuration steps should you recommend? (Select TWO)
- Configure the storage account to use Read-access geo-redundant storage (RA-GRS).Answer
- Configure the client application to direct read operations to the secondary endpoint if the primary endpoint is unavailable.Answer
- CConfigure the client application to write tracking data directly to the secondary storage endpoint to achieve active-active write capabilities.
- DConfigure the storage account to use Locally redundant storage (LRS) to minimize storage costs.
- EConfigure the storage account to use Geo-redundant storage (GRS) to allow read access to the secondary endpoint at all times.
Answer
Configure the storage account to use Read-access geo-redundant storage (RA-GRS) and configure the client application to direct read operations to the secondary endpoint if the primary endpoint is unavailable.
To meet the requirements, you must configure the storage account to use Read-access geo-redundant storage (RA-GRS) because it replicates data across regions and provides a read-only endpoint in the secondary region. Additionally, the client application must be configured to handle read failures by targeting the secondary read endpoint. This allows users to read tracking data even during a primary region outage without requiring a storage account failover.
Step-by-Step Solution
Key Concept
Read-access geo-redundant storage (RA-GRS) replication and client-side read routing to the secondary storage endpoint.