A parks FAQ generative workload hits Cosmos DB 429 responses during seasonal tourism spikes. What should the team do?
Select an answer to reveal the explanation.
Short Explanation
A 429 is Cosmos saying the ticket line is full—watch the counters, bump RU (or ease the client), and the parks FAQ line keeps moving through tourist season.
Full Explanation
Azure Cosmos DB returns HTTP 429 when request-unit capacity is exhausted. A parks FAQ generative workload that spikes during seasonal tourism should monitor 429 throttling and adjust Cosmos throughput (manual or autoscale) while ensuring clients implement bounded retry with backoff. That combination restores capacity headroom and protects the FAQ experience for residents and visitors without abandoning the RU-managed data service.
Ignoring 429 responses and retrying forever without adjusting throughput or client backoff amplifies storms, delays answers, and never fixes the capacity root cause. Deleting the parks FAQ container whenever tourism season begins destroys the knowledge store and is operationally reckless. Switching the FAQ store to anonymous public blob folders with no RU accounting abandons Cosmos consistency, indexing, and access controls that municipal AI backends rely on.
Exam caveat: 429 indicates throttling against provisioned or autoscale RU limits—not necessarily a permanent outage; the correct response is capacity and client-policy tuning, not data deletion. Operational check: chart 429 rates and normalized RU consumption against tourism calendars, raise throughput or enable autoscale before peak weekends, validate SDK retry/backoff settings, and retest FAQ p95 latency under a synthetic seasonal load profile.