Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.
exam questions

Exam AZ-204 All Questions

View all questions & answers for the AZ-204 exam

Exam AZ-204 topic 3 question 58 discussion

Actual exam question from Microsoft's AZ-204
Question #: 58
Topic #: 3
[All AZ-204 Questions]

You are developing a Cosmos DB solution that will be deployed to multiple Azure regions.

Your solution must meet the following requirements:

• Read operations will never receive write operations that are out of order.
• Maximize concurrency of read operations in all regions.

You need to choose the consistency level for the solution.

Which consistency level should you use?

  • A. session
  • B. eventual
  • C. bounded staleness
  • D. consistent prefix
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
de55d65
1 day, 4 hours ago
Selected Answer: D
What we can rule out is B eventual, since there can be out-of-order reads, and C, since the question does not contain any information about a boundary. If the wording of the question was "consistency" instead of "concurrency", I would go for A "session". Therefore I'd expect the lower the consistency, the higher the concurrency. I would go for D Consistent prefix. Reference: https://learn.microsoft.com/en-us/azure/cosmos-db/consistency-levels No words about concurrency there.
upvoted 1 times
...
Vichu_1607
2 weeks, 1 day ago
Selected Answer: C
C. bounded staleness: Bounded staleness consistency ensures that reads never see out-of-order writes and provides a lag window within which the data might be stale. This consistency level guarantees that reads are consistent within a specified staleness window, which meets the requirement of never receiving out-of-order writes. It also allows for high concurrency of read operations across multiple regions.
upvoted 2 times
...
Mattt
3 weeks, 6 days ago
Selected Answer: C
C is the correct answer Bounded staleness guarantees that read operations will never see writes out of order, which directly addresses your requirement for ensuring that read operations never receive write operations that are out of order. It also maximizes the concurrency of read operations in multiple regions while providing a guarantee that reads lag behind writes by a certain staleness window (defined in terms of time or number of versions). This balance between consistency and availability fits your scenario well.
upvoted 3 times
...
passme847
1 month ago
Selected Answer: D
"Consistent prefix consistency, the reads never see out of order writes for a transactional batch of writes" https://learn.microsoft.com/en-us/azure/cosmos-db/consistency-levels
upvoted 1 times
Mattt
3 weeks, 6 days ago
But it doesn’t maximize the concurrency
upvoted 1 times
...
...
ns4098
1 month ago
Selected Answer: C
Why not C?
upvoted 2 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...