Top resident questions in Cosmos DB should warm an Azure Managed Redis cache used by the 311 assistant. What integration pattern fits?
Select an answer to reveal the explanation.
Short Explanation
When popular 311 questions shift in Cosmos, change feed is the relay that warms Redis—so the assistant’s hot answers stay fresh without a once-a-decade clipboard copy.
Full Explanation
Top resident questions stored in Cosmos DB can warm an Azure Managed Redis cache for the 311 assistant when Cosmos change detection (such as change feed) fans out updates into Redis. As popular-question documents change, the processor refreshes cache entries so hot answers stay aligned with the system of record without decade-scale manual copies. That event-driven integration is a standard municipal pattern linking durable stores to low-latency caches used by citizen assistants.
Manually copying popular questions into Redis once a decade with no change detection guarantees staleness. Deleting Redis whenever Cosmos DB accepts any write destroys useful cache state on unrelated writes and causes constant cold starts. Running Redis and Cosmos DB in separate clouds with no event path between them leaves no reliable warming mechanism.
Exam caveat: change feed processors must handle at-least-once delivery idempotently when upserting Redis keys for top questions, and warming should target normalized FAQ keys—not every Cosmos write indiscriminately. Operational check: update a top-question document in Cosmos, verify the change feed handler writes the corresponding Redis entry, confirm the 311 assistant serves the warmed value on the next hit, and monitor processor lag during intake spikes.