Your team has deployed a generative agent for internal HR use, including summarizing candidate resumes...

The selected option specifically D states “Implement guardrails to prevent outputs referencing protected attributes”, which matches the operational requirement rather than a superficial wording match. At production scale, Option D preserves separability between reasoning, state, tools, and runtime operations. The high-value engineering move is responsible AI controls that are part of the runtime path, not just model-card language or prompt reminders. Bias tied to names or gender requires guardrails that block protected-attribute reasoning in outputs. Prompt reminders are weaker and less enforceable. That is why the other options are traps: authentication tells you who used the system; it does not prove the generated content stayed compliant. For a production build, NeMo Guardrails adds programmable controls around LLM applications, can wrap LangChain flows, and supports policy checks before and after model/tool execution. Anything less would make the agent fragile when traffic, schemas, policies, or user behavior shift. Regulated workloads also need logged policy decisions so teams can prove which rail acted and why.