Plan and manage an Azure AI solution 1.4 Implement responsible AI across generative AI and agentic systems

A custom blocklist with competitor names, using exact-match and regex terms, is applied…

Study guide skill: Configure safety filters, guardrails, risk detection, and content moderation

Question B8-009

A custom blocklist with competitor names, using exact-match and regex terms, is applied to the content filter of two deployments in a Foundry resource. It blocks the names for a GPT deployment from Azure OpenAI but has no effect for a Llama deployment. What explains this?

Select one answer.

  • A The built-in harm categories already cover competitor names, so the blocklist is ignored
  • B Regex terms aren't supported, so only the exact-match terms work
  • C Blocklist support is limited to Azure OpenAI models ✓ Correct answer
  • D Blocklists created through the Azure OpenAI API don't apply; they must be created in the Foundry portal

Answer: C

Custom blocklists filter terms specific to your use case, such as competitor names, but blocklist support is limited to Azure OpenAI models. Terms can use exact match or regex patterns, and blocklists can be created through the Azure OpenAI API. The configurable guardrails handle most moderation needs, and blocklists exist precisely for use-case-specific terms they don't cover.

Deep dive

How it works

Foundry's configurable guardrails are enough for most content moderation needs. Custom blocklists cover the gap: terms specific to your use case, such as competitor names, internal project names or domain-specific sensitive terms. You add terms using exact match or regex patterns and apply the blocklist to a content filter.

The catch is in a note on the page: blocklist support is limited to Azure OpenAI models. The GPT deployment is an Azure OpenAI model, so the blocklist works there. The Llama deployment isn't, so the same blocklist has no effect on it, even in the same Foundry resource.

Blocklists can be created with the Azure OpenAI API. The page's troubleshooting tip for regex terms is to check the pattern syntax and test the pattern separately before adding it.

The other options, and when you'd use them

  • Harm categories already cover competitor names: Competitor names are given as the example of a use-case-specific term that blocklists exist for, beyond what the guardrails handle.
  • Regex isn't supported: It is. Each term is specified as regex or exact match.
  • API-created blocklists don't apply: You can create blocklists with the Azure OpenAI API. And the blocklist does work for the GPT deployment.

Exam tip

Blocklist works on GPT but not on Llama = blocklists are limited to Azure OpenAI models.

References

Last reviewed:

Ready to test yourself? The quiz asks this and every other AI-103 question, with instant feedback. Practice this in a quiz →

All Plan and manage questions · AI-103 study guide

Thanks for your feedback!