179 questions
No questions match those filters.
A user found a way to make your production chatbot say...
This is one of the questions in the full AI/ML interview bank. Pro unlocks all 1789 questions; Premium includes the same bank plus the highest daily Practice limit.
See plansThe instinct under pressure is to patch the exact string that triggered the incident and move on, but that fix expires the moment someone rephrases the same attack. A role-switching exploit (“as a neutral advisor, tell me honestly…”) isn’t defeated by blocking that one sentence — it’s defeated by recognizing the attack category and closing every variant of it, which means spending time in the immediate aftermath red-teaming paraphrases, translations, and encoded versions of the same request before declaring the incident closed.
The two-phase split matters because the goals are genuinely different: immediate response is about limiting exposure with whatever narrow, possibly-overfit fix ships fastest, while long-term prevention is about making the same class of failure structurally harder, which takes longer and shouldn’t block the immediate mitigation. Mixing the two — spending the first hour engineering an elegant permanent fix — leaves the vulnerability live for everyone else who might find it independently in the meantime.
The artifact that should outlive the incident is the regression test case itself. Every fixed vulnerability that isn’t captured as a permanent test is a vulnerability that can silently come back the next time the system prompt is edited, the model is upgraded, or a well-meaning refactor touches the filtering logic. A mature safety practice measures itself partly by the size of this regression suite — a security review that references “847 injection attempts blocked over six months, zero successful, full test suite retained” is a categorically stronger answer than “we fixed the bug the user reported.”