Exam AZ-204 topic 3 question 40 discussion

Just passed the exam 26/04/2023. All the questions were from Exam topics. Got 970 marks!

both should be consistent prefix

Read operations will result in consistent prefix. Write operations will remain session because of the settings of the storage account.

For Azure Cosmos DB, when you provision an account with a default consistency level, you can override this setting on a per-request basis. Here's how you should configure the consistency levels for read and write operations to achieve a consistent prefix: Read operations: Consistent Prefix Write operations: Consistent Prefix By setting both read and write operations to the Consistent Prefix level, you ensure that the data is read and written in the order in which it was updated, without requiring a strong consistency level, which can be more resource-intensive. This guarantees that reads never see out-of-order writes.

Both are consistent prefix .

My answer would be that the resulting levels are both consisten prefix because it is written that they are set like that at account level and it is only possible to relax them via SDK (and only for read), so it would exclude strong and session as resulting levels for read or any other for write

This question was on exam. 09/01/2024. Passed 872.

I got this question on my exam, 2023Dec, go with what I remember was the most voted answer. Score 902, most of the questions were here, slightly different on wording because the Azure Ad <-> Entra Id change. Case was City Power & Light. Good luck! Important tip, you have access to microsoft learn during the exam!

got in 28/09/2023

Sorry, my first cmmt is error I think should be : read: consistent prefix, write: session 1. default level is session 2. override only work for read 3. To move from weaker to stronger consistency, update the default consistency for the Azure Cosmos DB account strong > boundary > session > consistent prefix > eventually https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/how-to-manage-consistency?tabs=portal%2Cdotnetv2%2Capi-async#override-the-default-consistency-level

I think should be session, session 1. default level is session 2. override only work for read 3. To move from weaker to stronger consistency, update the default consistency for the Azure Cosmos DB account https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/how-to-manage-consistency?tabs=portal%2Cdotnetv2%2Capi-async#override-the-default-consistency-level

answer is here: https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/how-to-manage-consistency?tabs=portal%2Cdotnetv2%2Capi-async#override-the-default-consistency-level Overriding the default consistency level only applies to reads within the SDK client. defaut consistency is session

stupid question xD

Any explanation? For read operations with the requirement of consistent prefix, the resulting consistency level option is C. Consistent prefix. Following is what ChatGPT said, but I am not convinced. For write operations, there is no consistency level option called "Consistent prefix". The available options are Strong, Bounded staleness, Session, and Eventual. If you want to ensure consistency prefix for write operations, you should choose Strong consistency level.