AeroSpire Aviation is designing a business continuity solution for an aviation telemetry ingestion system. The system writes flight data to an Azure Storage account configured with Read-Access Geo-Redundant Storage (RA-GRS). The primary region is East US, and the secondary region is West US.
During a simulated disaster recovery drill, the primary region experiences a complete service outage. The design team is evaluating the system's behavior during the outage and during a subsequent customer-managed failover.
Which of the following statements regarding the behavior of the storage account and the application are true? (Select TWO.)
- Before the failover is initiated, the application can continue to read telemetry data using the secondary endpoint, but cannot write new data.Cevap
- When the customer-managed failover is initiated, the storage account type is automatically converted to Locally Redundant Storage (LRS) in the new primary region.Cevap
- CBefore the failover is initiated, the application can maintain write availability by redirecting write operations directly to the secondary region's endpoint.
- DAfter the customer-managed failover completes, the storage account automatically re-enables geo-redundancy to replicate data back to the original primary region.
Cevap
Prior to failover, the application can only read from the secondary endpoint and cannot write to it. Once a customer-managed failover is initiated, the storage account is converted to Locally Redundant Storage (LRS) in the new primary region.
The correct options state that the secondary endpoint is read-only prior to failover, and that the account changes to Locally Redundant Storage (LRS) in the new primary region upon failover. This accurately reflects the design and operational behavior of Read-Access Geo-Redundant Storage (RA-GRS) accounts under failure scenarios.
Adım Adım Çözüm
Anahtar Kavram
Azure Storage account customer-managed failover behavior and replication tiers