Examice

Exam AZ-204 All QuestionsBrowse all questions from this exam

Question 140

HOTSPOT

You provisioned an Azure Cosmos DB for NoSQL account named account1 with the default consistency level.

You plan to configure the consistency level on a per request basis. The level needs to be set for consistent prefix for read and write operations to account1.

You need to identify the resulting consistency level for read and write operations.

Which levels should you configure? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

Correct Answer:

Discussion

adilkhan

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

UzrShkl

Bro you had the contributor access?

Rodikito

of course

[Removed]

useless comment

LucreziaB

Still more useful than yours :)

Ciupaz

Never seen a score so high.

adilkhan

both should be consistent prefix

b1992

could you explain why?

Makonee

Wrong. The Given answer is correct. Only Read Consistency can be set by client. Write stays at server setting which is session by default. https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/how-to-manage-consistency?tabs=portal%2Cdotnetv2%2Capi-async#override-the-default-consistency-level

Vladimir_Gajinov

You are right, the given answer is correct. Microsoft documentation states: Overriding the default consistency level only applies to <b>reads</b> within the SDK client. <b>An account configured for strong consistency by default will still write and replicate data synchronously to every region in the account.</b> When the SDK client instance or request overrides this with Session or weaker consistency, reads will be performed using a single replica.

giuliohome

Still very confusing explanation. The other thing you must consider is that the level can only be relaxed. In conclusion I guess you have to configur prefix for write because it cannot be change while you can configure strong for read because it can be relaxed on a per SDK request basis.

CarlosTheBoldest

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!

LittleBean

Hi, does all question were from exam topic? Did you bought contributor access? And what does it mean by case study city power and light. In free version I haven't came across thus term/ farmer case study

Dianahu

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

[Removed]

Now I get it! Appreciated.

seanzhenxiao

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

1989jay

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

Mark16

stupid question xD

dy0917

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.

giuliohome

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

richardc7

got in 28/09/2023

seanzhenxiao

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