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 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.)
- Enable multi-region writes and replicate the database across the target regions.Answer
- Use a composite partition key combining the SensorID and the hourly timestamp.Answer
- CConfigure a single write region and rely on Locally Redundant Storage (LRS) replication.
- DSelect CountryCode as the partition key to group metrics by geographical area.
Answer
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.
Step-by-Step Solution
Key Concept
Azure Cosmos DB global distribution, multi-region writes, and high-cardinality partition keys.