Security wants proof that new multi-agent guardrails block prompt injection and disallowed tool combinations before production. Production traffic is sparse and cannot supply enough attack variety. Which testing approach should they use?
Select an answer to reveal the explanation.
Short Explanation
Correct answer: B. Sparse production traffic will not stress guardrails. Build synthetic adversarial datasets—injection, exfil attempts, bad tool sequences—and run them automatically pre-release. Waiting for live attacks (A), happy-path demos (C), or annual casual tries (D) leave huge gaps. Refresh the synthetic set as tools and policies evolve, and track block-rate regressions in CI.
Full Explanation
Guardrail testing and validation, including synthetic data, is a core secure/govern skill. Option B creates diverse adversarial coverage independent of production volume and integrates with automated pipelines. Options A, C, and D provide insufficient, biased, or infrequent coverage. Combine synthetic tests with red-teaming results, measure false positives that harm usability, and gate releases on minimum block rates for critical categories.