A marine logistics company is designing a storage solution for real-time cargo container tracking data. The data is stored in an Azure General Purpose v2 (GPv2) storage account. The design must satisfy the following requirements:
- The data must survive a regional disaster and remain available for read-only reporting in the secondary region without initiating a failover.
- The storage system in the primary region must tolerate the loss of an entire datacenter zone without data loss or service disruption.
- Tracking reports must be generated instantly, requiring sub-second retrieval times for all data stored in the account.
Which storage configuration should you recommend?
- ARead-access geo-redundant storage (RA-GRS) using the Hot access tier, with applications configured to write tracking data directly to both the primary and secondary endpoints
- Read-access geo-zone-redundant storage (RA-GZRS) using the Hot access tierAnswer
- CLocally redundant storage (LRS) using the Cool access tier
- DRead-access geo-zone-redundant storage (RA-GZRS) using the Archive access tier
Answer
Read-access geo-zone-redundant storage (RA-GZRS) using the Hot access tier
Read-access geo-zone-redundant storage (RA-GZRS) replicates data synchronously across three availability zones in the primary region, ensuring protection against zone outages. It also replicates data asynchronously to a secondary region and enables read access to the secondary endpoint. Using the Hot access tier ensures that tracking reports can be generated instantly with sub-second retrieval latency.
Step-by-Step Solution
Key Concept
Selecting the optimal Azure Storage redundancy tier (RA-GZRS) and access tier (Hot) based on zonal/regional availability and performance requirements.