A logistics company, Zenith-Fleet, uses an Azure Storage v2 account to store critical telemetry logs. The system has the following requirements:
- Maximum read availability: Reads must be highly available even during a primary region outage.
- Recovery Point Objective (RPO) for writes: Less than minutes.
- Recovery Time Objective (RTO) for writes: Less than hour.
- Cost: Must minimize cross-region data transfer costs and redundancy costs.
To meet these requirements, the architect configured the account with Read-Access Geo-Redundant Storage (RA-GRS). The primary region (East US) experiences a catastrophic outage. The operations team observes that the storage account's `Last Sync Time` is minutes behind the current time. To restore write access within the RTO, the team plans to initiate a customer-managed failover to the secondary region (West US).
Which of the following correctly describes the write availability, DNS resolution, and redundancy behavior during and after the failover process?
- Write operations to the storage account are unavailable until the failover completes; once completed, the primary endpoint DNS record updates to resolve to the secondary region, write access is restored, and the storage account replication changes to Locally Redundant Storage (LRS).Cevap
- BThe application can immediately resume write operations by targeting the secondary endpoint (with the -secondary suffix) while the failover is in progress, and the storage account automatically maintains its RA-GRS configuration.
- CThe Azure Storage client library automatically redirects write requests to the secondary endpoint using a dual-write configuration, maintaining the RA-GRS status without converting the storage account to LRS.
- DWrite operations are routed to the secondary region through a storage failover group listener endpoint, which automatically fails over with zero data loss and preserves the geo-redundancy settings of the storage account.