Quick Answer
The answer is autoscale provisioned throughput. This configuration is correct because it enables Cosmos DB to automatically scale up to a maximum of ten times the base request units per second during sudden write spikes, preventing HTTP 429 throttling errors while maintaining performance. For the AZ-305 exam, this scenario tests your understanding of how autoscale handles unpredictable traffic patterns without manual intervention, often appearing alongside multi-region write requirements for global low-latency reads. A common trap is confusing autoscale with manual throughput—autoscale is ideal for variable workloads, not steady-state traffic. Remember the memory tip: “Auto for spikes, manual for steady.”
This AZ-305 practice question tests your understanding of design data storage solutions. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A gaming company stores player session data in Azure Cosmos DB. They need to handle sudden spikes in write traffic without throttling and ensure low-latency reads globally. Which configuration should they use?
Autoscale provisioned throughput
Autoscale automatically scales RU/s to handle spikes without throttling.
Serverless capacity mode
Why wrong: Serverless is for intermittent traffic, not sustained spikes.
Multi-region writes
Why wrong: Multi-region writes improve write throughput but do not automatically handle spikes.
Manual provisioned throughput
Why wrong: Manual throughput can cause throttling during spikes.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Autoscale provisioned throughput
Autoscale provisioned throughput (A) is correct because it allows Cosmos DB to automatically scale up to the maximum throughput (up to 10x the base RU/s) during sudden write spikes, preventing throttling (HTTP 429 errors). Combined with multi-region writes (which is a separate configuration), it ensures low-latency global reads by enabling writes to be accepted in any region and replicated asynchronously. This meets both the spike-handling and global read latency requirements.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Autoscale provisioned throughput
Why this is correct
Autoscale automatically scales RU/s to handle spikes without throttling.
Related concept
Read the scenario before looking for a memorised answer.
Serverless capacity mode
Why it's wrong here
Serverless is for intermittent traffic, not sustained spikes.
Multi-region writes
Why it's wrong here
Multi-region writes improve write throughput but do not automatically handle spikes.
Manual provisioned throughput
Why it's wrong here
Manual throughput can cause throttling during spikes.
Common exam traps
The trap here is confusing 'multi-region writes' (which handles global write availability) with 'autoscale' (which handles traffic spikes), leading candidates to pick C because they think global writes are needed for low-latency reads, when in fact reads can be served from any region without multi-region writes.
Detailed technical explanation
Autoscale in Cosmos DB uses a 'scaling factor' of 10x the base RU/s (e.g., setting a max of 10,000 RU/s allows scaling from 1,000 to 10,000 RU/s). The scaling is reactive based on the 'consumed RU/s' metric over a 5-second window, so extremely rapid spikes may still experience brief throttling before scaling completes. For global low-latency reads, multi-region writes are not required; instead, enabling Cosmos DB's multi-region reads (with a single write region) suffices, as reads are served from the nearest region using the same throughput pool.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Design data storage solutions — study guide chapter
Learn the concepts, then practise the questions
Design data storage solutions practice questions
Targeted practice on this topic area only
All AZ-305 questions
999 questions across all exam domains
Microsoft Azure Solutions Architect Expert AZ-305 study guide
Full concept coverage aligned to exam objectives
AZ-305 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise AZ-305 questions linked to Design identity, governance, and monitoring solutions.
Practise AZ-305 questions linked to Design data storage solutions.
Practise AZ-305 questions linked to Design business continuity solutions.
Practise AZ-305 questions linked to Design infrastructure solutions.
Practise AZ-305 questions linked to SAA-C03 VPC.
Practise AZ-305 questions linked to SAA-C03 S3 lifecycle policy questions.
Practise AZ-305 questions linked to SAA-C03 RDS Multi-AZ questions.
Practise AZ-305 questions linked to SAA-C03 IAM policy.
Practise AZ-305 questions linked to SAA-C03 Route 53 failover questions.
Practise AZ-305 questions linked to SAA-C03 CloudFront.
Practise AZ-305 questions linked to SAA-C03 NAT gateway questions.
Practise AZ-305 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Design data storage solutions — This question tests Design data storage solutions — Read the scenario before looking for a memorised answer..
The correct answer is: Autoscale provisioned throughput — Autoscale provisioned throughput (A) is correct because it allows Cosmos DB to automatically scale up to the maximum throughput (up to 10x the base RU/s) during sudden write spikes, preventing throttling (HTTP 429 errors). Combined with multi-region writes (which is a separate configuration), it ensures low-latency global reads by enabling writes to be accepted in any region and replicated asynchronously. This meets both the spike-handling and global read latency requirements.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 24, 2026
This AZ-305 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-305 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.