Question 25 of 179 from exam AZ-204: Developing Solutions for Microsoft Azure

Question 25 of 179 from exam AZ-204: Developing Solutions for Microsoft Azure

Prev Question Next Question

Question

DRAG DROP - You are developing a solution for a hospital to support the following use cases: -> The most recent patient status details must be retrieved even if multiple users in different locations have updated the patient record.

-> Patient health monitoring data retrieved must be the current version or the prior version.

-> After a patient is discharged and all charges have been assessed, the patient billing record contains the final charges.

You provision a Cosmos DB NoSQL database and set the default consistency level for the database account to Strong.

You set the value for Indexing Mode to Consistent.

You need to minimize latency and any impact to the availability of the solution.

You must override the default consistency level at the query level to meet the required consistency guarantees for the scenarios.

Which consistency levels should you implement? To answer, drag the appropriate consistency levels to the correct requirements.

Each consistency level may be used once, more than once, or not at all.

You may need to drag the split bar between panes or scroll to view content.

NOTE: Each correct selection is worth one point.

Select and Place:

Consistency levels ‘Strong Bounded Staleness Consistent Prefix Eventual Answer Area Return the most recent patient status. Return health monitoring data that is no less than one version behind. After patient is discharged and all charges are assessed, retrieve the — correct billing data with the final charges. r

Explanations

Consistency levels ‘Strong Bounded Staleness Consistent Prefix Eventual Answer Area Return the most recent patient status. Return health monitoring data that is no less than one version behind. After patient is discharged and all charges are assessed, retrieve the correct billing data with the final charges. Strong Bounded Staleness Eventual

Box 1: Strong - Strong: Strong consistency offers a linearizability guarantee.

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.

Box 2: Bounded staleness - Bounded staleness: The reads are guaranteed to honor the consistent-prefix guarantee.

The reads might lag behind writes by at most "K" versions (that is "updates") of an item or by "t" time interval.

When you choose bounded staleness, the "staleness" can be configured in two ways: The number of versions (K) of the item The time interval (t) by which the reads might lag behind the writes Box 3: Eventual - Eventual: There's no ordering guarantee for reads.

In the absence of any further writes, the replicas eventually converge.

Incorrect Answers: Consistent prefix: Updates that are returned contain some prefix of all the updates, with no gaps.

Consistent prefix guarantees that reads never see out-of-order writes.

https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels
Prev Question Next Question