A consumer forum's moderation team is configuring content filtering for a Foundry-hosted chat model. They want casual profanity to pass through unfiltered, since their community tolerates it, but they still need hate speech and self-harm content blocked, and they also know a handful of coded slurs specific to their community that the default categories do not reliably catch. (Select TWO.) Which two configuration steps should the team take?

The right configuration is to lower the severity threshold for the profanity-related filtering behavior while leaving the hate speech and self-harm categories at their protective default levels, because that lets casual swearing pass through without loosening protection against more harmful content. Adding the community-specific coded terms to a custom blocklist directly addresses the gap the team identified, since default categories are trained on broad patterns and will not reliably catch slang unique to one community; a blocklist lets the team filter those exact terms regardless of what the general categories detect. Turning off content filtering for the entire deployment is incorrect because it removes protection against hate speech and self-harm as well, which contradicts the requirement to keep those blocked, and after-the-fact manual review does not prevent harmful content from reaching users first. Relying only on the model's built-in training to avoid the coded slurs is incorrect because the model's training behavior is not something the moderation team can adjust through configuration, and depending on it alone ignores the deliberate tooling, threshold controls and blocklists, that Foundry provides specifically for this kind of fine-grained control.