Exam AZ-204 topic 3 question 68 discussion

Actual exam question from Microsoft's AZ-204

Question #: 68
Topic #: 3

DRAG DROP
-

You manage an Azure Cosmos DB for a NoSQL API account named account1. You configure account1 with the default consistency level.

An application named app1 must access containers in account1 to perform read and write operations. The connections from app1 to account1 must be established by using the direct mode.

You plan to configure app1 to override the default consistency level by using the Azure Cosmos DB SDK client.

You need to set the maximum consistency level for app1 to use for read and write operations.

Which consistency level should you set? To answer, move the appropriate maximum consistency levels to the correct operation types. You may use each maximum consistency level once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.

Show Suggested Answer

Suggested Answer:

by 21c5438 at Jan. 22, 2025, 8:31 p.m.

Comments

Submit Cancel

21c5438

Highly Voted 4 months, 3 weeks ago

The default consistency level is session. Only reads consistency level can be overridden, but it can not be stronger than the consistency level set for the account. Therefore: session session

upvoted 10 times

c75e123

1 month, 2 weeks ago

Agree, here is the source: https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/how-to-manage-consistency?tabs=portal%2Cdotnetv2%2Capi-async#configure-the-default-consistency-level

upvoted 1 times

...

florianwicher

4 months, 1 week ago

Agree, for the exact same reason

upvoted 1 times

...

vizay

Most Recent 1 month, 1 week ago

Writes are always done with full consistency within the write region(s), regardless of the consistency level you choose. so the given answer is correct

upvoted 1 times

vizay

1 month, 1 week ago

By setting the consistency level in app1 to Session, you ensure that the application operates at a consistency level that is supported by the underlying account configuration. If you tried to set it to a stronger consistency level like Strong, the Azure Cosmos DB service would enforce the account's default consistency (Session). session and session

upvoted 1 times

vizay

1 month, 1 week ago

Account-level consistency is set to Session. app1 tries to override the consistency level using the SDK. For reads: app1 can set the consistency to Session, Eventual, or Consistent Prefix, but not Strong. For writes: app1 cannot set a stronger consistency than Session either, because the account default restricts it to Session for both reads and writes.

upvoted 1 times

...