43Defend a high-stakes generation pipeline against jailbreaks and hallucination at the same time.▼hardAnthropicOpenAIScale1 replies◆ premiumTwo failure modes, one architecture. Why no single guardrail holds, the defense-in-depth layers that assume the model will be broken, and the design rule that limits the blast radius when prompt filters inevitably fail.Open full answer →
08Your LLM agent is vulnerable to prompt injection that reveals the system prompt. How do you defend it?▼medium★ EssentialOpenAIAnthropicSalesforce1 repliesunlockedA verbatim AI-security interview question with a built-in trap: candidates who promise to stop extraction fail, and candidates who shrug 'it's unpreventable' also fail. The winning answer is a layered containment design.Open full answer →
13Design safety guardrails into the request flow of an LLM serving system, where do they sit and what does each catch?▼hardAnthropicOpenAISalesforce1 replies○ sign inAn Anthropic-style system design axis: architectural safety. The answer is a pipeline diagram in words, five checkpoints, what each catches, what each costs in latency, and the streaming complication most candidates forget.Open full answer →
31Design defense-in-depth for a support agent that can issue refunds and update customer records.▼hardSalesforceOpenAIStripe1 replies◆ premiumThe agent has real money authority and a write path into the system of record, which is the exact shape attackers want. The strong answer is layered enforcement outside the model, with the spend cap and the chain rule in code, not in the prompt.Open full answer →
