Azure Cosmos DB – Consistency, Partitioning and SDK · AZ-204: Developing Solutions for Microsoft Azure Develop for Azure Storage
A globally distributed Azure Cosmos DB account must allow reads from any region, but each read may lag behind the latest write by no more than 5 seco…
Practice question from Azure Cosmos DB – Consistency, Partitioning and SDK (AZ-204: Developing Solutions for Microsoft Azure Develop for Azure Storage), with the correct answer and a step-by-step solution.
easy · MCQ · Q-E43C77
A globally distributed Azure Cosmos DB account must allow reads from any region, but each read may lag behind the latest write by no more than 5 seconds or 100,000 updates, whichever limit is reached first. Which consistency level should be configured?
- A.Eventual consistency
- B.Consistent prefix consistency
- C.Bounded staleness consistencyCorrect answer
- D.Strong consistency
Solution
Bounded staleness consistency guarantees that reads lag behind writes by no more than a configured time interval or number of versions. Eventual and consistent prefix consistency do not provide this explicit staleness bound, while strong consistency provides a stricter guarantee than required.
More from Azure Cosmos DB – Consistency, Partitioning and SDK
- An application uses Azure Cosmos DB to update a user's profile and then immediately read the profile during the same user session. The read…
- A Cosmos DB container stores telemetry for many tenants. Its current partition key is /tenantId, but one tenant produces most of the teleme…
- A .NET application uses the Azure Cosmos DB SDK v3. The container's partition key path is /customerId, and the application must retrieve th…
- An Azure Cosmos DB container stores orders for 10,000 retail stores. Most queries retrieve orders for a specific store, and writes are dist…
Practise more Develop for Azure Storage
Sign up free for adaptive practice on this chapter, with instant feedback and hints on every question.
Start practising freeFree to start · No credit card needed