Exam AZ-204 topic 3 question 61 discussion

Actual exam question from Microsoft's AZ-204

Question #: 61
Topic #: 3

HOTSPOT
-

A company has an Azure Cosmos DB for NoSQL account. The account is configured for session consistency. Data is written to a single Azure region and data can be read from three Azure regions.

An application that will access the Azure Cosmos DB for NoSQL container data using an SDK has the following requirements:

• Reads from the application must return the most recent committed version of an item from any Azure region.
• The container items should not automatically be deleted.

You need to implement the changes to the Azure Cosmos DB for NoSQL account.

What should you do? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

Show Suggested Answer

Suggested Answer:

by alvingeo at Oct. 30, 2024, 1:25 p.m.

Comments

Submit Cancel

Jay456

Highly Voted 6 months, 3 weeks ago

* The most recent committed version from any region - strong consistency. This cannot be changed by de SDK so should be done on the account level. * TTL = -1

upvoted 8 times

...

brexamtopics

Most Recent 6 months, 3 weeks ago

Reads must return the most recent committed version: Change the default consistency level on the account; because, Consistency can only be relaxed at the SDK instance or request level. To move from weaker to stronger consistency, update the default consistency for the Azure Cosmos DB account. And, Strong consistency offers a linearizability guarantee. Linearizability refers to serving requests concurrently. The reads are guaranteed to return the most recent committed version of an item.

upvoted 2 times

...

alvingeo

7 months, 2 weeks ago

For the requirement to always return the most recent committed version of an item, you should change the consistency level using the SDK to ensure strong consistency as needed. For preventing automatic deletion of items, set the Time to Live (TTL) property to 0. This will keep the items from expiring automatically. So answer will be: 1 box. change the consistency level using the SDK* 2 box : set the Time to Live (TTL) property to 0

upvoted 2 times

examtopicsLogin123

6 months ago

You can't set stronger consistency level via SDK. "Consistency can only be relaxed at the SDK instance or request level. 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

upvoted 1 times

...

NetoZee

7 months, 1 week ago

2 box is Time to live -1, because when it's -1 never expired. https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/time-to-live

upvoted 2 times

...