An emergency FAQ agent is mid-stream answering a routine question when a higher-priority alert banner must take over. How should streaming be developed?
Select an answer to reveal the explanation.
Short Explanation
If the tornado siren goes off mid-sentence, you stop the small talk. Streaming for emergency FAQ agents needs an interrupt so the alert wins. Finishing a routine answer first is the wrong priority.
Full Explanation
An emergency FAQ agent mid-stream on a routine question must yield when a higher-priority municipal alert banner needs the channel. Streaming should be developed as preemptible: the runtime can interrupt routine generation and surface the alert before finishing the lower-priority answer. Life-safety and emergency communications outrank courtesy completion of a FAQ; preemption encodes that priority in the conversation control plane so residents see critical banners immediately.
Finishing every routine answer completely before any emergency alert can appear inverts priority and can delay life-safety messaging by many seconds of irrelevant prose. Deleting the emergency alert system so streaming never has to interrupt removes the civic capability the stem requires rather than solving preemption. Muting all resident sessions for one hour whenever any alert exists is a blunt denial of service to ordinary inquiries and is not a surgical stream-preemption design.
Exam caveat: preemption policy should define which alert classes interrupt which routine streams, and how interrupted sessions resume or redirect after the banner. Operational check: start a routine FAQ stream, inject a higher-priority alert event, confirm the routine stream stops and the alert surfaces first, verify residents are not forced to wait for FAQ completion, and confirm non-alert sessions are not globally muted for an arbitrary hour.