GridPulse Analytics is designing a storage architecture for a smart-meter telemetry ingestion system. The system writes telemetry data to a general-purpose v2 storage account in the East US region. The storage architecture must meet the following requirements:
- Protect against a local availability zone failure in East US with zero downtime and zero data loss.
- In the event of a complete outage of the East US region, read access to the historical telemetry data must remain available with a Recovery Time Objective (RTO) of minutes.
- In the event of a complete outage of the East US region, write operations must be restored in the West US region with an RTO of less than hour and a Recovery Point Objective (RPO) of less than minutes.
- Cost must be minimized by avoiding redundant active-active compute environments for writes.
Which storage configuration and recovery strategy should you recommend?
- Configure the storage account to use Read-Access Geo-Zone-Redundant Storage (RA-GZRS). Direct read operations to the secondary endpoint, and initiate a customer-managed account failover to restore write capabilities.Cevap
- BConfigure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). Direct read operations to the secondary endpoint, and initiate a customer-managed account failover to restore write capabilities.
- CConfigure the storage account to use Read-Access Geo-Zone-Redundant Storage (RA-GZRS). Direct read operations to the secondary endpoint, and redirect write operations to the secondary endpoint without initiating a failover.
- DConfigure the storage account to use Geo-Zone-Redundant Storage (GZRS). Initiate a customer-managed account failover during a regional outage to restore both read and write capabilities.