A consumer electronics company is preparing to launch a public-facing Foundry-hosted chatbot on its retail website. Before launch, the team wants the chatbot protected against both the standard categories of unsafe content, such as hate speech and violence, and against company-specific terms that generic safety categories would never catch, such as the names of banned competitor products the company does not want mentioned. (Select TWO.) Which two configurations should they enable?
Select all correct answers, then click Submit.
Short Explanation
You need two protections here: content filters with severity thresholds for standard harm categories, plus custom blocklist for company-specific terms. The filters catch broadly recognized unsafe content, while the blocklist catches competitor names and brand-sensitive language generic categories won't. Longer responses don't help, and removing the system message weakens control.
Full Explanation
The two configurations to enable are content filters with configured severity thresholds for standard harm categories such as hate, violence, sexual, and self-harm content, and custom blocklist containing company-specific terms, such as competitor names and brand-sensitive language, that standard categories would not catch. Content filters with configured severity thresholds address the standard, well-known categories of unsafe content like hate speech, violence, sexual content, and self-harm, which covers the general safety requirement. Custom blocklist separately covers terms that are specific to this company, such as competitor product names or other brand-sensitive language, which generic harm categories were never designed to catch, so both configurations are needed together to satisfy the full requirement described. Increasing the model's maximum output token limit is incorrect because it only controls how long the response can be; it has no bearing on filtering unsafe or brand-sensitive content and does not address either stated need. Removing the system message is incorrect because it would strip away the instructions that help keep the chatbot's behavior on-topic and constrained, which weakens safety and control rather than strengthening it, especially wrong for public-facing launch.