AquaShield Water Solutions is designing a disaster recovery solution for an application that processes real-time telemetry from water treatment facilities. The telemetry logs are written continuously to an Azure Blob Storage account in the East US region. The solution must meet the following requirements:
- During normal operations, the application must read and write data in the primary region.
- If a disaster disables the primary region, the application must be able to read existing telemetry logs immediately from a secondary region.
- The Recovery Point Objective (RPO) for data loss must be less than 15 minutes.
- If the primary region remains unavailable for an extended period, the application must be able to write new logs to the secondary region.
- Storage costs must be minimized.
Which storage configuration and disaster recovery strategy should you recommend?
- AUse Locally Redundant Storage (LRS) in the primary region. Configure Azure Backup to perform cross-region restores of the blobs to a separate storage account in the secondary region every 4 hours.
- BUse Read-Access Geo-Redundant Storage (RA-GRS). Configure the application to write directly to the secondary storage endpoint immediately if the primary region is unavailable.
- Use Read-Access Geo-Redundant Storage (RA-GRS). Configure the application to read from the secondary endpoint during a primary outage, and initiate a customer-managed failover to enable write operations in the secondary region if the outage is prolonged.Cevap
- DUse Geo-Redundant Storage (GRS). Configure a lifecycle management policy to archive all blobs to the Archive tier in the secondary region to minimize costs, and rehydrate them if a primary regional outage occurs.