Azure Cosmos DB – Consistency, Partitioning and SDK · AZ-204: Developing Solutions for Microsoft Azure Develop for Azure Storage
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 must refl…
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-1BC9F8
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 must reflect the user's preceding write, while the application should avoid the stronger global coordination of strong consistency. Which consistency level is most appropriate?
- A.Eventual
- B.SessionCorrect answer
- C.Consistent prefix
- D.Strong
Solution
Session consistency provides read-your-writes and monotonic-read guarantees within a client session without requiring the global coordination of strong consistency. Eventual and consistent-prefix consistency do not guarantee that the immediate read observes the preceding write.
More from Azure Cosmos DB – Consistency, Partitioning and SDK
- 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…
- 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 t…
- 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