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

Unlimited Access

Get Unlimited Contributor Access to the all ExamTopics Exams!
Take advantage of PDF Files for 1000+ Exams along with community discussions and pass IT Certification Exams Easily.

Exam DP-201 topic 20 question 4 discussion

Actual exam question from Microsoft's DP-201
Question #: 4
Topic #: 20
[All DP-201 Questions]

Which consistency level should you use for Health Interface?

  • A. Consistent Prefix
  • B. Session
  • C. Bounded Staleness
  • D. Strong
Show Suggested Answer Hide Answer
Suggested Answer: D 🗳️
Scenario: ADatum identifies the following requirements for the Health Interface application:
✑ ..reads must display be the most recent committed version of an item.
Azure Cosmos DB consistency levels include:
Strong: 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. A client never sees an uncommitted or partial write. Users are always guaranteed to read the latest committed write.
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
watata
Highly Voted 3 years ago
"and reads must display be the most recent committed version of an item" --> Strong
upvoted 13 times
...
savin
Most Recent 2 years, 9 months ago
surely strong should be the consistency level
upvoted 1 times
...
maynard13x8
2 years, 11 months ago
I think answer is correct if we assume all data is written only to Los Angeles (where are located all its apps) and the other regions only read from it. In this case (single writer/multiple readers), it may be. The problem is that is unclear.
upvoted 2 times
...
axelwest36
3 years, 1 month ago
The following requirements make sure that the answer must be Session: "reads must display be the most recent committed version of an item." and "reduce the amount of time it takes to add data from new hospitals to Health Interface" With Session consistency, reads will never be out of order and it minimizes the latency
upvoted 3 times
...
awitick
3 years, 2 months ago
We cant use Strong on Dallas, New York and Los Angeles at the same time so D is wrong. A is obviously wrong cause it doesn't talk about low write latency and we only have to choose between B and C. Although C gives higher write latency, the read operation is not exactly 15 minutes and depends upon the number of updates which can change from 5 minutes to 1 day where Session gives us the RPO of less than 15 minutes guarantee which is reliable accordingly to the requirements. So the answer is C.
upvoted 2 times
...
ACSC
3 years, 2 months ago
Definitely Strong
upvoted 2 times
...
syu31svc
3 years, 3 months ago
I would pick Bounded staleness https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels For multiple write regions, Bounded staleness is recommended; you can find the table towards the end
upvoted 1 times
syu31svc
3 years, 3 months ago
My bad please disregard; Strong is the answer
upvoted 3 times
...
...
Bonzai
3 years, 3 months ago
You can't have multi region writes and Strong Consistancy
upvoted 4 times
maynard13x8
2 years, 11 months ago
Never was said all region were writers. If you replicate data to all regions (one writer - multiple readers) you can use strong consistency.
upvoted 1 times
maynard13x8
2 years, 11 months ago
... but “increased throughput for writing data” may suggest multiple writers. In this case, I’ll get session consistency because is better than Bounded staleness.
upvoted 1 times
...
...
...
M0e
3 years, 5 months ago
And "reduce the amount of time it takes to add data from new hospitals to Health Interface" by configuring multiple write-regions.
upvoted 2 times
datachamp
3 years, 4 months ago
The given answer for this question is correct as the most recent committed version of an item so it is Strong Consistency. But the reason you are providing is not. This sentence "reduce the amount of time it takes to add data from new hospitals to Health Interface" is a sign to use Cosmo DB as a database solution. This means that new hospital can be with variant columns and format and so we need to provide a flexible schema solution (JSON Document etc) and so Cosmo DB with SQL API is the answer. Don't confuse it with multiple write-region.
upvoted 4 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 ...