Examkin

Soru

Zorluk: ZorData Redundancy and High Availability

A logistics enterprise is designing the storage architecture for a high-performance inventory tracking system. The system requires Azure Premium Block Blob storage to handle high-frequency write operations with sub-millisecond latency. The architecture must meet the following requirements:

- The storage must survive the loss of an entire datacenter (Availability Zone) within the primary region with zero data loss (RPO=0RPO = 0).
- A replica of the data must be maintained in a secondary region to support disaster recovery.
- A reporting application in the secondary region must have continuous read access to the replicated data.
- The system must support writing test data directly to the secondary region's storage endpoint during simulated disaster recovery drills without initiating a failover of the primary storage account.

Which storage design should you recommend?

  1. Create a Premium Block Blob storage account configured with Zone-Redundant Storage (ZRS) in the primary region, and use Azure Blob Storage Object Replication to replicate data to a separate Premium Block Blob storage account in the secondary region.Cevap
  2. B
    Create a single Premium Block Blob storage account configured with Read-Access Geo-Zone-Redundant Storage (RA-GZRS) to handle regional replication and secondary read access natively.
  3. C
    Create a single General Purpose v2 (GPv2) storage account configured with Read-Access Geo-Zone-Redundant Storage (RA-GZRS), and write directly to the secondary endpoint during testing.
  4. D
    Create a Premium Block Blob storage account configured with Locally-Redundant Storage (LRS) in the primary region, and use Azure Site Recovery to replicate the storage account to the secondary region.

Cevap

Create a Premium Block Blob storage account configured with Zone-Redundant Storage (ZRS) in the primary region, and use Azure Blob Storage Object Replication to replicate data to a separate Premium Block Blob storage account in the secondary region.
The correct design uses a Premium Block Blob storage account with Zone-Redundant Storage (ZRS) to meet the sub-millisecond latency and zone-redundancy requirements. Since Premium Block Blobs do not natively support geo-redundancy (GRS/GZRS), Azure Blob Storage Object Replication is configured to copy the data asynchronously to a separate Premium storage account in the secondary region. Because the destination is a distinct, independent storage account, it supports continuous read operations for reporting and allows direct write access for test data without requiring a storage account failover.

Adım Adım Çözüm

1
Determine the performance and primary redundancy requirements.
Premium Block Blob storage configured with Zone-Redundant Storage (ZRS) is selected.
Sub-millisecond latency requires the Premium Block Blob performance tier. Surviving a zone failure with zero data loss (RPO=0RPO = 0) in the primary region requires ZRS, which replicates data synchronously across three availability zones.
2
Evaluate native geo-redundancy options for Premium Block Blobs.
Native GRS, GZRS, and their read-access variants are ruled out.
Azure Premium Block Blob accounts (blockBlobStorage) do not support native geo-redundancy options; they are restricted to LRS and ZRS.
3
Identify a replication mechanism that allows writes to the secondary target without failover.
Use Azure Blob Storage Object Replication between the primary ZRS account and a destination Premium account in the secondary region.
Object Replication replicates data block blobs asynchronously between two distinct storage accounts. Because the destination is a standalone storage account, the reporting application can continuously read from it, and test data can be written directly to it during drills without impacting the primary account or requiring a failover.

Anahtar Kavram

Azure Storage replication and service limits for Premium Block Blobs.
Bu soruyu puanla

Konular

Data Redundancy and High Availability

Bu konudan daha fazla soru