Develop for Azure storage
Free Microsoft Certified: Azure Developer Associate practice — 6 questions on Develop for Azure storage, with explanations. No sign-up. Full 12-question mixed test →
A global e-commerce company uses Cosmos DB with multi-region writes across three regions. They require that reads within a single client session never return data older than what that same client already wrote or read (monotonic reads, read-your-own-writes), while keeping RU consumption as low as possible. Which consistency level should they configure?
Session consistency guarantees read-your-own-writes and monotonic reads within the client's session token scope, and it is the lowest-RU consistency level that still provides these guarantees, making it the default and recommended level for most globally distributed apps.
A company stores telemetry from 5 million IoT devices in Cosmos DB, each sending roughly one event per second continuously. Queries are almost always scoped to a single device over a time range. Which partition key design avoids exceeding the logical partition storage limit while still supporting efficient per-device time-range queries?
A synthetic key like /deviceId_date bounds the amount of data per logical partition (one bucket per device per day) so no single logical partition ever approaches the 20 GB storage limit, while still allowing efficient queries filtered by device and date range.
Your application performs point reads using the container's partition key and id, averaging 5 RUs per read. A developer proposes replacing these with a SQL query filtered on a non-partition-key property, which forces Cosmos DB to fan out across all 20 physical partitions. What is the most accurate description of the RU cost impact of this change?
A cross-partition query without a partition key filter is executed independently against every physical partition and the gateway merges results, and each partition's execution is billed in RUs — so total RU consumption scales with the number of partitions fanned out to, typically far exceeding a targeted point read.
You need to process new documents inserted into a Cosmos DB container in near real time, invoking a function per document, with automatic checkpointing and load balancing across multiple compute instances handled for you. Which approach should you use?
The Azure Functions Cosmos DB trigger is built on the Change Feed Processor library, automatically managing lease containers, checkpointing, and dynamic load balancing across multiple function instances — exactly matching the stated requirements with minimal custom code.
Using the Azure Storage SDK's AcquireLeaseAsync method on a blob, what is the maximum lease duration, in seconds, you can request for a fixed-duration lease (excluding an infinite lease)?
A fixed-duration blob lease can be requested between 15 and 60 seconds; to hold a lease longer than 60 seconds you must request an infinite lease (duration of -1) and release it explicitly or renew it before expiry.
A media company archived 50 TB of video files to the Archive access tier. For a compliance audit, they must retrieve one specific 2 GB file within 1 hour, and cost is not a primary concern. What should they do?
Setting the rehydrate priority to High on the tier-change or copy operation typically completes rehydration of objects under 10 GB in under 1 hour, meeting the compliance deadline; Standard priority can take up to 15 hours.
Ready for the real thing?
The full course has two full-length practice tests, video lessons for every exam domain, hands-on labs and detailed answer explanations.
Start my full course on Udemy →