DP-420 · Question #81
You have an Azure Cosmos DB for NoSQL account named account1 that has a single read-write region and one additional read region. Account1 uses the strong default consistency level. You have an…
The correct answer is C. Writes will use the strong consistency level. Overriding the default consistency level only applies to reads within the SDK client. An account configured for strong consistency by default will still write and replicate data synchronously to every region in the account. When the SDK client instance or request overrides this…
Question
You have an Azure Cosmos DB for NoSQL account named account1 that has a single read-write region and one additional read region. Account1 uses the strong default consistency level. You have an application that uses the eventual consistency level when submitting requests to account1. How will writes from the application be handled?
Options
- AWrites will use the eventual consistency level.
- BAzure Cosmos DB will reject writes from the application.
- CWrites will use the strong consistency level.
- DThe write order is not guaranteed during replication.
How the community answered
(40 responses)- A5% (2)
- B3% (1)
- C90% (36)
- D3% (1)
Explanation
Overriding the default consistency level only applies to reads within the SDK client. An account configured for strong consistency by default will still write and replicate data synchronously to every region in the account. When the SDK client instance or request overrides this with Session or weaker consistency, reads will be performed using a single replica. https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels
Topics
Community Discussion
No community discussion yet for this question.