Option C introduces a deterministic validation boundary between probabilistic model output and downstream execution. Structured validation can reject missing fields, invalid types, unauthorized actions, malformed arguments, and values outside approved enumerations before any tool or business process acts on the response. Anthropic recommends Structured Outputs when guaranteed schema conformance is required. Increase Output Consistency
Option D implements defense in depth. Prompt-level instructions establish intended behavior, while runtime classifiers, content filters, policy engines, output validators, tool permissions, and human confirmation gates provide controls outside the model. Anthropic’s guardrail guidance recommends combining safeguards rather than depending on one mechanism. Mitigate Jailbreaks and Prompt Injections
Option A creates a bypass mechanism that adversaries may discover or imitate. Option B may alter output variability but is not a security boundary and cannot guarantee policy compliance. Option E places complete reliance on a system prompt, which remains vulnerable to ambiguity, conflicting inputs, model errors, and indirect prompt injection.
Guardrails should be risk-based, independently enforceable where possible, observable, tested against adversarial cases, and proportional to the consequences of downstream actions.
Study Guide references/topics: Layered guardrails; structured validation; runtime content checks; prompt injection; deterministic enforcement; defense in depth.
===============
