Soru

Zorluk: Çok zorData Redundancy and High Availability

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?

  1. Configure the storage account to use read-access geo-zone-redundant storage (RA-GZRS).Cevap
  2. 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.Cevap
  3. C
    Configure 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.
  4. D
    Ensure that the application writes directly to the secondary region endpoint during a primary region outage, without initiating a storage account failover.

Cevap

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.

Adım Adım Çözüm

1
Analyze the primary region redundancy requirement.
Synchronous replication across three availability zones requires zone-redundant storage (ZRS) or geo-zone-redundant storage (GZRS). Locally redundant storage (LRS) and geo-redundant storage (GRS) do not satisfy this as they replicate within a single facility.
This filters out options like RA-GRS which only provide local redundancy in the primary region.
2
Analyze the secondary region read access requirement.
Immediate read-only access to the secondary region without initiating a failover requires read-access enabled on the geo-redundancy option (RA-GZRS).
This ensures the application can query the secondary endpoint directly during normal operations or primary outages.
3
Evaluate write capabilities during a primary region outage.
The secondary endpoint is read-only. Writes are not allowed directly to the secondary endpoint. Resuming write operations requires executing a customer-managed failover to promote the secondary region to the new primary region.
This identifies that writing directly to the secondary endpoint without failover is impossible.
4
Determine the state of the storage account post-failover.
After failover is completed, the storage account's redundancy type in the new primary region automatically becomes LRS, and the secondary endpoint is removed.
This defines the correct post-failover lifecycle and the need to manually reconfigure geo-redundancy if required.

Anahtar Kavram

Azure Storage Account Redundancy and Customer-Managed Failover Mechanics
Tahmini Süre:3m 0s
Bu soruyu puanla