Microsoft Azure Solutions Architect Expert AZ-305 Practice Question

Azure Cosmos DB for NoSQL guarantees single-digit millisecond reads and writes and is schema-agnostic, making it well-suited for high-velocity, flexible JSON telemetry. Enabling autoscale throughput lets the service automatically adjust RU/s based on load, reducing cost when traffic is low. Azure Blob Storage is the most economical option for large binary objects such as JPEGs. A lifecycle management policy that moves blobs from the Hot tier to Cool after 30 days and to Archive after 180 days keeps frequently accessed images performant while minimizing long-term storage costs, and requires no manual administration.

Azure SQL Database Hyperscale offers strong relational capabilities but incurs higher costs and imposes rigid schemas, making it less appropriate for rapidly changing JSON telemetry; Azure Files and managed disks are costlier than object storage for large, infrequently accessed images. Azure Data Lake Storage Gen2 can store both data types but would not provide the required millisecond read latency without additional compute (for example, Azure Synapse or Data Explorer) and may raise overall cost and complexity. Redis is an in-memory cache, not a durable store for long-term telemetry or images. Therefore, using Cosmos DB with autoscale for telemetry plus tiered Azure Blob Storage for images best balances features, performance, and cost.