Handling Bursts Cost-Effectively with Azure Queue Storage & Throttling
You are architecting an Azure AI solution that uses Azure AI Language to analyze text for sentiment and key phrases. The solution must handle bursts of up to 500 requests per second but average only 50 requests per second. You need to ensure cost efficiency while meeting performance requirements. Which THREE actions should you take?
Quick Answer
The cost-efficiency problem here is that provisioning Azure AI Language to sustain 500 requests per second around the clock, to cover a burst that only actually happens occasionally against a 50-per-second average, means paying for capacity that sits mostly idle. Azure Queue Storage solves this by decoupling ingestion from processing: incoming requests land in the queue the moment they arrive, absorbing the full burst instantly and cheaply since queue storage is inexpensive compared to AI service compute, while the Language service itself keeps consuming from that queue at a steady, lower rate it can sustain without needing burst-level capacity provisioned. This is the general pattern for reconciling a spiky arrival rate with a service that's expensive to over-provision — insert a low-cost buffer between the spike and the processing tier so the processing tier only ever needs to be sized for sustained throughput, not peak throughput. Client-side throttling and retry logic complements this by handling the case where the queue itself is catching up, gracefully backing off rather than hammering the service with duplicate requests. Any scenario describing a mismatch between burst capacity and average load, where over-provisioning for the peak would be wasteful, is describing this decouple-with-a-queue pattern.
⚠ Common exam trap
Candidates often assume a higher pricing tier (like S0) alone can handle bursts, but without queuing and retry logic, the service will still throttle requests, leading to failures or the need for costly over-provisioning.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Azure Queue Storage to buffer requests during spikes
Azure Queue Storage can decouple the ingestion of requests from processing, allowing the solution to buffer bursts of up to 500 requests per second while the Azure AI Language service processes at a lower sustained rate. This prevents request throttling and enables cost-efficient scaling by using a lower-cost queue to absorb spikes rather than over-provisioning the AI service tier.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use Azure Queue Storage to buffer requests during spikes
Why this is correct
Decouples ingestion and processing, smoothing out bursts.
- ✗
Select the Free tier and implement queuing
Why it's wrong here
Free tier limited to 20 requests per minute, cannot handle 500 RPS.
- ✓
Use the S0 pricing tier
Why this is correct
S0 tier supports up to 1000 requests per second, sufficient for bursts.
- ✓
Implement client-side throttling and retry logic
Why this is correct
Helps manage rate limits gracefully.
- ✗
Deploy the service in multiple regions
Why it's wrong here
Not needed for burst handling; increases cost.
Go deeper
Related to this question
About these practice questions
Courseiva writes every AI-102 question from scratch — 945 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on AI-102
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A developer is configuring an Azure AI Language resource for sentiment analysis. The solution must process social media posts in real-time with a throughput of 1000 requests per minute. After testing, the developer notices that the API returns a 429 (Too Many Requests) error when the load exceeds 500 requests per minute. What is the most likely cause and solution?
easy- A.Scale out the resource by creating multiple Azure AI Language instances and load balancing requests.
- ✓ B.Upgrade the Azure AI Language resource to a higher tier (e.g., Standard S) to increase the rate limit.
- C.Implement retry logic with exponential backoff to handle 429 errors.
- D.Use Azure API Management to cache responses and reduce calls.
Why B: The 429 error indicates the request rate exceeds the resource's allocated tier limit. Azure AI Language resources have predefined rate limits per pricing tier; the Standard S tier offers higher throughput (e.g., 1,000 requests per minute) compared to lower tiers. Upgrading to Standard S directly increases the rate limit to match the required 1,000 requests per minute, making it the correct solution.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AI-102 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 AI-102 exam.