Home › Azure AZ-305 › cloudcomputing › az305datastorage › Which Cosmos DB feature should an architect reco…
Which Cosmos DB feature should an architect recommend to handle a sudden burst from 100 to 10,000 RPS without pre-provisioning fixed capacity?
AProvisioned reserved capacity with no autoscale
BManually doubling the throughput each morning by hand
CDisabling indexing
DAutoscale provisioned throughput (or serverless mode for spiky low-volume workloads)
Answer & Solution
Correct answer: D. Autoscale provisioned throughput (or serverless mode for spiky low-volume workloads)
Cosmos autoscale + serverless absorb bursty workloads (per AZ-305 §2 scalability). Manual changes don't fit bursts; reserved is for steady load; disabling indexing degrades queries.
Related questions
Which Azure data-platform service should an architect recommend for streaming ingestion + Which Cosmos DB consistency level should an architect recommend for a globally-deployed apWhich Azure SQL Database feature should an architect recommend to recover from a regional Which Azure storage replication option should an architect recommend for data that must suWhich Azure storage capability should an architect recommend to provide a hierarchical-namWhich Azure service should an architect recommend to ingest, transform, and orchestrate ETWhich Azure service should an architect recommend for petabyte-scale columnar analytics + Which Azure SQL Database feature should an architect recommend to scale a transactional da