AZ-200 Azure Cosmos DB 2

Question 1

How does Azure Cosmos DB multi-region write (multi-master) benefit applications?

Accepted Answer

Allows writes to any configured region, reducing write latency globally

Answer

Multi-region writes allow applications to write to the nearest configured region, drastically reducing write latency for globally distributed users.

Question 2

Which Cosmos DB feature streams all insert, update, and delete operations to downstream consumers in real time?

Accepted Answer

Change Feed

Answer

Change Feed provides a sorted, persistent log of all changes (inserts and updates) in a Cosmos DB container, enabling real-time event-driven processing.

Question 3

What happens if a Cosmos DB operation exceeds the provisioned RU/s limit on a container?

Accepted Answer

Cosmos DB returns a 429 Too Many Requests response and the SDK retries automatically

Answer

Exceeding provisioned throughput causes Cosmos DB to return HTTP 429, and the SDK's built-in retry policies handle automatic back-off and retry.

Question 4

Which Cosmos DB indexing mode indexes every item and property by default?

Accepted Answer

Consistent

Answer

The Consistent indexing mode synchronously updates the index after every write, ensuring queries always reflect the latest data by default.

Question 5

What is the purpose of using a synthetic partition key in Azure Cosmos DB?

Accepted Answer

To combine multiple properties into a single high-cardinality partition key

Answer

A synthetic partition key concatenates or hashes multiple fields to create a high-cardinality key, ensuring even data distribution across partitions.

AZ-200 - Microsoft Azure Developer Practice Test

AZ-200 - Microsoft Azure Developer Practice Test

AZ-200 Azure Cosmos DB 2