Question

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

Skyline Freight Systems is designing a disaster recovery strategy for its shipment tracking application. The application writes critical transit logs to Azure Blob Storage. The design must meet the following requirements:
- Data must be replicated to a secondary Azure region.
- In the event of a primary region outage, the application must be able to read data from the secondary region.
- The recovery point objective (RPO) must be less than 15 minutes.
- If a failover is initiated to the secondary region, the application must be able to resume write operations.

Which two of the following configuration options and operational behaviors should you include in the design? (Select TWO)

  1. Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS) or Read-Access Geo-Zone-Redundant Storage (RA-GZRS).Answer
  2. Initiate a customer-managed failover of the storage account, which updates the primary endpoint to point to the secondary region and allows writes to resume.Answer
  3. C
    Configure the application to perform active-active write operations directly to the secondary region storage endpoint prior to failover.
  4. D
    Use Locally Redundant Storage (LRS) combined with custom manual scripts to copy blobs to the secondary region.
  5. E
    Deploy an Azure SQL Database auto-failover group to manage the replication and failover of the Blob Storage containers.

Answer

Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS) or Read-Access Geo-Zone-Redundant Storage (RA-GZRS), and initiate a customer-managed failover of the storage account, which updates the primary endpoint to point to the secondary region and allows writes to resume.
To satisfy the requirements, the storage account must be configured with Read-Access Geo-Redundant Storage (RA-GRS) or Read-Access Geo-Zone-Redundant Storage (RA-GZRS). This ensures that the application can read from the secondary region while the primary is healthy or degraded. To restore write capabilities during a prolonged outage, a customer-managed storage account failover must be initiated. This updates the storage account's DNS records so that the secondary region becomes the new primary region, allowing the application to write to the storage account again.

Step-by-Step Solution

1
Determine the required replication tier to support geo-redundancy and read access in the secondary region.
Identify that RA-GRS or RA-GZRS must be selected to allow reading from the secondary region without initiating a failover.
Standard GRS or GZRS does not allow read access to the secondary region unless a failover is triggered.
2
Analyze how write operations are restored in the event of a permanent primary region failure.
Identify that a customer-managed failover must be initiated, which changes the primary DNS endpoint of the storage account to point to the secondary region.
Before failover, the secondary endpoint is read-only. Performing a failover is required to make the secondary endpoint writeable as the new primary.

Key Concept

Azure Storage replication types (RA-GRS/RA-GZRS) provide read access to the secondary region, but write access to the secondary region is only enabled after initiating a storage account failover.
Estimated Time:1m 30s
Rate this question