Azure Cosmos DB Flashcards
6 cards from real AZ-200 practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 Azure Cosmos DB flashcards as text
How does Azure Cosmos DB multi-region write (multi-master) benefit applications?
Answer: Allows writes to any configured region, reducing write latency globally
Multi-region writes allow applications to write to the nearest configured region, drastically reducing write latency for globally distributed users.
Which Cosmos DB feature streams all insert, update, and delete operations to downstream consumers in real time?
Answer: Change Feed
Change Feed provides a sorted, persistent log of all changes (inserts and updates) in a Cosmos DB container, enabling real-time event-driven processing.
What happens if a Cosmos DB operation exceeds the provisioned RU/s limit on a container?
Answer: Cosmos DB returns a 429 Too Many Requests response and the SDK retries automatically
Exceeding provisioned throughput causes Cosmos DB to return HTTP 429, and the SDK's built-in retry policies handle automatic back-off and retry.
Which Cosmos DB indexing mode indexes every item and property by default?
Answer: Consistent
The Consistent indexing mode synchronously updates the index after every write, ensuring queries always reflect the latest data by default.
What is the purpose of using a synthetic partition key in Azure Cosmos DB?
Answer: To combine multiple properties into a single high-cardinality partition key
A synthetic partition key concatenates or hashes multiple fields to create a high-cardinality key, ensuring even data distribution across partitions.
Which Cosmos DB SDK method is used to perform an efficient point read by specifying both the item ID and partition key?
Answer: container.ReadItemAsync(id, partitionKey)
ReadItemAsync performs a single-partition lookup using both the item ID and partition key, consuming the minimum possible RUs for a read.