For a globally distributed app that needs single-digit-millisecond reads and the ability to write in multiple regions, which Azure Cosmos DB configuration is appropriate?
Azure Developer Associate
MS_AZ_204Ready to test yourself?
A timed, blueprint-proportional exam drawn fresh from this bank โ with a per-domain score report.
๐ Free preview: showing 10 of 100 questions. Unlock the full bank โ every question, explanation, and reference.
Unlock all 100 questions โ10 questions across 5 topics. Choose an answer for each question, then check it to see the correct answer and explanation.
Filter by topic
10 questions in Develop for Azure storage
Develop for Azure storage
10 questions in topicBlob storage SDK operations and Azure Cosmos DB development.
You must choose a Cosmos DB consistency level that guarantees reads never see out-of-order writes and always return data no older than a defined number of versions or time interval. Which level is this?
A Cosmos DB container storing millions of orders queries most often by CustomerId. To distribute data and avoid hot partitions, what should CustomerId be chosen as?
Using the Azure Blob Storage SDK, you must upload a local file to a container, creating the blob if it doesn't exist and overwriting if it does. Which client type performs the upload?
An app must react in code when a blob is created, running processing logic. Using the SDK you want change notifications rather than polling the container. Which Azure feature delivers blob-created events?
You need to read a subset of Cosmos DB items efficiently and be billed by throughput. Which unit measures the cost of database operations in Cosmos DB?
A downstream process must handle every change (insert/update) to a Cosmos DB container in order, at scale, using a built-in mechanism. Which feature should you consume?
You must generate a time-limited, read-only link to a single blob for a client, revocable if needed, using a policy stored on the container. Which combination provides revocation?
Which Cosmos DB API should you choose to migrate an existing MongoDB application with minimal code changes while gaining Azure's global distribution and SLAs?
To reduce read latency and RU cost for repeated point reads of the same items in Cosmos DB, which built-in caching feature can you enable?