VeloStream Telematics is designing a disaster recovery solution for its vehicle telemetry platform. The platform continuously writes unstructured metrics to a General Purpose v2 storage account in the East US region.
The architecture team defines the following disaster recovery requirements:
- During an outage in East US, the telemetry data must remain available for read-only analytical queries in a secondary region with a Recovery Time Objective (RTO) of less than minutes.
- To avoid unnecessary data loss due to replication lag, a write failover to the secondary region must only be initiated if the primary region outage is expected to exceed hours.
- The solution must minimize overall storage costs.
Which configuration and failover strategy should you recommend?
- Configure the storage account with Read-Access Geo-Redundant Storage (RA-GRS). In the event of a primary region outage, immediately configure the analytics applications to read from the secondary endpoint. If the outage is confirmed to exceed hours, initiate a customer-managed failover to make the secondary region the primary write endpoint.Answer
- BConfigure the storage account with Geo-Redundant Storage (GRS). In the event of a primary region outage, configure the analytics applications to read from the secondary endpoint. If the outage exceeds hours, contact Microsoft Support to trigger a forced failover to the secondary region.
- CConfigure the storage account with Read-Access Geo-Redundant Storage (RA-GRS). In the event of a primary region outage, immediately configure the ingestion client to write to the secondary endpoint to prevent write failures, without initiating a customer-managed failover.
- DConfigure the storage account with Zone-Redundant Storage (ZRS). In the event of a primary region outage, Azure will automatically redirect both read and write requests to a secondary region within the same geography within minutes.