Azure CosmosDB Flashcards Preview

DP-201 Designing an Azure Data Solution Certification > Azure CosmosDB > Flashcards

Flashcards in Azure CosmosDB Deck (9)
Loading flashcards...
1
Q

Eventual Consistency Level

A

Eventual consistency does not provide any ordering guarantee on reads, but it provides highest throughput.
The replicas eventually converge

2
Q

Strong Consistency Level

A

Strong consistency guarantees to always return the most recent committed version of an item.

3
Q

Bounded staleness Consistency Level

A

The reads might lag behind by at most K versions or by T time interval. You can configure these parameters.
Bounded staleness offers total global order except within the “staleness window.”

4
Q

Session

A

Within a single client session reads are guaranteed to honor the consistent-prefix (assuming a single “writer” session), monotonic reads, monotonic writes, read-your-writes, and write-follows-reads guarantees. Clients outside of the session performing writes will see eventual consistency.

5
Q

Consistent Prefix

A

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

6
Q

RTO (Recovery Time Objective) Single Master Any Consistency Level

A

< 15 minutes

7
Q

RTO (Recovery Time Objective) Multi Master (Except eventual)

A

0

8
Q

Azure Tables partition key

A

In Azure Tables partition keys separate data into different servers. The same server can store multiple partitions.

9
Q

Optimize reports with CosmosDB

A

Use indexes to optimize query performance for on-demand reporting.
Do not use Cosmos DB change feed which is used to trigger Azure Functions based on events.