Challenge · intermediate · 25 min · Premium
Pause writes, keep lookups
A bad release is proposing wrong replacements at Calder and it must stop shipping now, without stopping customers from getting answers. Pick the stop that blocks effects and not lookups, apply it, and prove both halves live.
Brief
- Customer
- Calder Equipment (synthetic customer from the Production AI Agents course; every metric and log on this box is made up for the exercise)
- Situation
- 10:15. This morning's release proposes replacements for pumps still under a loaner, and two have reached the operator queue. The product lead says stop everything. Support says customers are mid-conversation and a full stop means silence for them. The runtime has a stop control with three modes.
- Your role
- You are the FDE who owns the runtime's stop. You have the console and the stop config (bound to the live runtime). The queue holds approved actions from before the bad release.
- Goal
- Choose the stop that halts new effects and keeps lookups and clarifications running, apply it, prove that the action rate is zero while the gateway still serves, and say what a full stop would have cost.
Objectives
- 1.Choose the stop mode (you commit to an answer)
- 2.Apply it to the live runtime
- 3.Prove both halves: no new actions, gateway still serving
- 4.Say what a full stop would have cost (you commit to an answer)
Mission workspace
This mission is part of premium, with every challenge and incident in the lab. The brief above is the whole problem; the box, the hints and the debrief are what you unlock.
Get full Premium access · ₹2,000 / $25
Every answer, concept and course, plus Premium PDF guides, companion files, the full practice-test bank and work-sample downloads. Referral Premium excludes guide PDFs and their companion files.
6 months · One payment · No auto-renewal
Study alongside free video lessons.