Examkin

Question

Difficulty: MediumDesign Storage and Non-Relational Data HA and DR

EcoSphere Energy is designing a disaster recovery strategy for its energy consumption reporting application. The application stores monthly PDF reports in a general-purpose v2 Azure Storage account configured with Read-Access Geo-Redundant Storage (RA-GRS). During normal operations, the application writes reports to the primary region and reads them from both the primary and secondary regions.

During a prolonged outage in the primary region, the engineering team decides to initiate a customer-managed failover to the secondary region.

Which of the following describes the write capabilities and redundancy state of the storage account immediately after the customer-managed failover is completed?

  1. A
    The storage account remains configured as geo-redundant storage, enabling write operations to be processed directly at the secondary endpoint while the primary region is offline without changing the redundancy configuration.
  2. B
    The storage account allows write operations to the secondary region's endpoint while it is in a read-access geo-redundant (RA-GRS) state before the customer-managed failover is initiated.
  3. The storage account configuration is converted to locally redundant storage (LRS) in the new primary region, and write operations are supported at the new primary endpoint.Answer
  4. D
    The storage account is automatically configured with Geo-Zone-Redundant Storage (GZRS) to maintain regional resilience, allowing read and write operations across both regions.

Answer

The storage account configuration is converted to locally redundant storage (LRS) in the new primary region, and write operations are supported at the new primary endpoint.
When a customer-managed failover is initiated for an Azure Storage account configured with Read-Access Geo-Redundant Storage (RA-GRS), the secondary region is promoted to become the new primary region. Immediately after the failover is completed, the storage account's redundancy type is automatically converted to locally redundant storage (LRS), and write operations are enabled on the new primary endpoint. To restore geo-redundancy, the account must be manually reconfigured to GRS or RA-GRS.

Step-by-Step Solution

1
Determine the write behavior of a geo-redundant storage account (GRS/RA-GRS) during normal operation versus outage situations.
Write operations are only allowed on the primary endpoint. The secondary endpoint is read-only (in RA-GRS) or inaccessible (in GRS) before failover.
Azure Storage accounts with geo-redundancy do not support active-active write configurations across primary and secondary endpoints.
2
Evaluate the state of the storage account immediately after a customer-managed failover is completed.
The secondary region's endpoint is promoted to become the new primary endpoint, enabling write operations, and the redundancy level changes to Locally Redundant Storage (LRS).
Initiating a failover updates the DNS records so that the secondary region acts as the primary, but replication to the old primary is stopped, making the storage account locally redundant in the new region.
3
Match the observed behavior with the correct system design options.
The correct option is the one stating the storage account transitions to LRS and supports write operations at the new primary endpoint.
This matches standard Azure Storage failover architecture mechanics.

Key Concept

Azure Storage Account Customer-Managed Failover Behavior
Rate this question

Topics

Design Storage and Non-Relational Data HA and DR

More questions from this topic