A company is designing a storage solution for storing critical transaction records in Azure Blob Storage. The solution must meet the following requirements:
- Data must be replicated synchronously across three availability zones in the primary region.
- In the event of a regional outage in the primary region, the application must have immediate read-only access to the replicated data in the secondary region without waiting for a failover to be initiated.
- In the event of a prolonged primary region outage, the application must be able to resume write operations to the same primary endpoint URI after a failover is executed.
Which two options should you include in the storage design to meet the requirements?
- Configure the storage account to use read-access geo-zone-redundant storage (RA-GZRS).Answer
- Ensure that after a customer-managed failover is executed, the storage account's redundancy type is converted to locally redundant storage (LRS) and the secondary read-only endpoint is removed.Answer
- CConfigure the storage account to use read-access geo-redundant storage (RA-GRS) to satisfy the requirement for synchronous replication across availability zones in the primary region.
- DEnsure that the application writes directly to the secondary region endpoint during a primary region outage, without initiating a storage account failover.
Answer
Configure the storage account to use read-access geo-zone-redundant storage (RA-GZRS) and ensure that after a customer-managed failover is executed, the storage account's redundancy type is converted to locally redundant storage (LRS) and the secondary read-only endpoint is removed.
To meet the requirements, the storage account must be configured for read-access geo-zone-redundant storage (RA-GZRS). This option replicates data synchronously across three availability zones in the primary region (meeting the zone-redundancy requirement) and asynchronously replicates to a secondary region, where the read-access feature allows the application to query the secondary endpoint immediately. When a customer-managed failover is executed to resume write operations on the primary endpoint URI, the secondary region is promoted to the new primary region, the storage redundancy type is automatically converted to locally redundant storage (LRS), and the secondary endpoint is removed.
Step-by-Step Solution
Key Concept
Azure Storage Account Redundancy and Customer-Managed Failover Mechanics
Estimated Time:3m 0s