Soru

Zorluk: OrtaAzure Cosmos DB and NoSQL Solutions

An environmental organization is designing a global weather monitoring system that collects data from thousands of atmospheric sensors. The sensors upload temperature and pressure metrics every 1010 seconds. The solution must meet the following requirements:
- Provide regional disaster resilience to ensure the system remains online if an Azure region experiences an outage.
- Minimize write latency for sensors located across North America, Europe, and Asia.
- Avoid hot partitions and ensure even distribution of write requests across logical partitions.

Which two configurations should you include in the design of the Azure Cosmos DB for NoSQL account? (Select TWO.)

  1. Enable multi-region writes and replicate the database across the target regions.Cevap
  2. Use a composite partition key combining the SensorID and the hourly timestamp.Cevap
  3. C
    Configure a single write region and rely on Locally Redundant Storage (LRS) replication.
  4. D
    Select CountryCode as the partition key to group metrics by geographical area.

Cevap

To meet the requirements, you should enable multi-region writes with replication across target regions and use a high-cardinality partition key such as a composite key of SensorID and an hourly timestamp.
Enabling multi-region writes and replicating the database across the target regions minimizes write latency for globally distributed sensors and provides high availability during a regional outage. Using a composite partition key like SensorID combined with a timestamp provides high cardinality, distributing requests evenly across logical partitions and preventing hot partitions.

Adım Adım Çözüm

1
Identify the geographical distribution and resilience requirements.
Since sensors are distributed across North America, Europe, and Asia, and the system must survive regional outages, multi-region writes must be enabled and the database replicated to the target regions.
This configuration provides local write endpoints to minimize write latency and ensures data availability if a single region fails.
2
Determine the optimal partition key design.
A high-cardinality key must be used to distribute writes evenly. A composite key combining SensorID and an hourly timestamp satisfies this requirement.
Using a low-cardinality key like country code would create hot partitions due to the high frequency of telemetry uploads from a single location.

Anahtar Kavram

Azure Cosmos DB global distribution, multi-region writes, and high-cardinality partition keys.
Bu soruyu puanla