A smart-home IoT company is designing a data storage architecture for device telemetry logs stored in Azure Blob Storage. The system must meet the following requirements:
- Survive a complete regional outage of the primary Azure region.
- Support active-active write operations in both the primary and secondary regions simultaneously.
- Minimize storage costs.
An architect recommends using Read-Access Geo-Redundant Storage (RA-GRS) to allow telemetry ingestion services in both regions to write directly to the storage account.
Why does the recommended solution fail to meet the requirements?
- Read-Access Geo-Redundant Storage (RA-GRS) does not support write operations to the secondary region; the secondary endpoint is read-only unless a failover is initiated.Answer
- BRead-Access Geo-Redundant Storage (RA-GRS) only replicates data within a single availability zone in the primary region and does not support regional recovery.
- CRead-Access Geo-Redundant Storage (RA-GRS) requires configuring an Azure SQL Database auto-failover group to enable read access in the secondary region.
- DRead-Access Geo-Redundant Storage (RA-GRS) requires configuring Azure Site Recovery (ASR) to replicate data, which exceeds the low-cost constraint.
Answer
Read-Access Geo-Redundant Storage (RA-GRS) does not support write operations to the secondary region; the secondary endpoint is read-only unless a failover is initiated.
The correct option is correct because Read-Access Geo-Redundant Storage (RA-GRS) replicates data to a secondary region but only allows read access to the secondary endpoint. It does not support write operations in the secondary region, failing the active-active write requirement.
Step-by-Step Solution
Key Concept
Azure Storage replication redundancy options and write limitations of read-access secondary endpoints.
Estimated Time:45s