Examkin

Soru

Zorluk: ZorAzure Cosmos DB and NoSQL Solutions

You are designing a globally distributed package delivery tracking application. The solution has the following requirements:
- Save package telemetry (JSON documents) in an Azure Cosmos DB for NoSQL database. The data must be partitioned to prevent hot partitions and scale horizontally. Telemetry contains PackageIdPackageId (GUID), LogisticsHubIdLogisticsHubId (10 unique values), and DestinationCountryDestinationCountry (190 unique values).
- Replicate the database to three regions (East US, West Europe, and East Asia) with multi-region writes enabled to ensure sub-10 ms10\text{ ms} read/write latency.
- Store high-resolution photos of delivered packages (up to 5 MB5\text{ MB} each) in an Azure Blob Storage account. The photo storage must survive regional outages and allow read access from a secondary region if the primary region fails.

Which two configurations should you include in the design?

  1. Partition the Azure Cosmos DB container using PackageId.Cevap
  2. Configure the Azure Blob Storage account to use Read-Access Geo-Redundant Storage (RA-GRS).Cevap
  3. C
    Partition the Azure Cosmos DB container using LogisticsHubId.
  4. D
    Configure the Azure Blob Storage account to use Locally Redundant Storage (LRS).

Cevap

The correct design configurations are partitioning the Azure Cosmos DB container using PackageId and configuring the Azure Blob Storage account to use Read-Access Geo-Redundant Storage (RA-GRS).
Partitioning by PackageId ensures that Cosmos DB workloads are distributed evenly across physical partitions because PackageId has high cardinality. Selecting Read-Access Geo-Redundant Storage (RA-GRS) for the Blob Storage account ensures that files are replicated across regions and remain readable even if the primary region goes offline.

Adım Adım Çözüm

1
Analyze the Cosmos DB partitioning requirements.
Determine that PackageId (GUID) has high cardinality, whereas LogisticsHubId (10 values) has extremely low cardinality.
Using a high-cardinality partition key distributes requests evenly and prevents hot partitions.
2
Analyze the Blob Storage replication and availability requirements.
Determine that the storage account must survive a regional outage and allow read access from a secondary region.
Read-Access Geo-Redundant Storage (RA-GRS) provides geo-redundancy and exposes a read-only endpoint in the secondary region.

Anahtar Kavram

Azure Cosmos DB partition key selection for scalability and Azure Storage redundancy configuration for regional disaster recovery.
Bu soruyu puanla

Konular

Azure Cosmos DB and NoSQL Solutions

Bu konudan daha fazla soru