What should you implement to identify hateful responses returned by a generative Al solution?

When using generative AI models such as those in Azure OpenAI, it’s critical to monitor and control the model’s outputs to prevent the generation of harmful, hateful, or unsafe content. According to Microsoft’s Responsible AI guidelines and Azure OpenAI safety systems, this is achieved through content filtering mechanisms.

Content filtering automatically analyzes generated text and blocks or flags responses containing hate speech, harassment, sexual content, or violent language. Azure OpenAI applies these filters by default through its built-in content moderation system, which categorizes responses into safety levels (safe, review, block).

Option review:

A. Prompt engineering: Helps guide responses but does not detect hate content automatically.

B. Abuse monitoring: Refers to manual or post-processing review, not real-time automated filtering.

C. Content filtering: ✅ Correct — actively detects and prevents hateful or unsafe responses.

D. Fine-tuning: Adjusts model behavior using additional training data but doesn’t ensure safety monitoring.