Study guide

6.4 Guardrails, Content Filters, Denied Topics, and Sensitive Data

AWS AI Practitioner Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: AIF-C01 Orientation and Official Source Control

1.1 Credential Scope, Code, and Search Language 1.2 Exam Format, Cost, Score, and Delivery 1.3 Official Exam Guide, Skill Builder, and Practice Workflow 1.4 Target Candidate Boundaries and Out-of-Scope Tasks 1.5 Domain Weights and Study Prioritization 1.6 Exam Policy, Retake, Results, and Recertification

2 Chapter 2: AI/ML Foundations and Use-Case Fit

2.1 AI, ML, Deep Learning, and Core Terminology 2.2 Supervised, Unsupervised, and Reinforcement Learning 2.3 Data Types, Labels, Structure, and Quality 2.4 Inference Patterns: Batch, Real-Time, and Embedded AI 2.5 AI Use-Case Fit and No-AI Decisions 2.6 Classification, Regression, Clustering, Forecasting, and Recommendation 2.7 AI/ML Foundations Case Lab

3 Chapter 3: ML Lifecycle, Metrics, and Practitioner MLOps

3.1 Data Collection, EDA, Preprocessing, and Feature Concepts 3.2 Training, Evaluation, Deployment, and Monitoring Lifecycle 3.3 Model Sources: Managed APIs, Open Source, and Custom Models 3.4 Evaluation Metrics and Business Metrics 3.5 Practitioner MLOps: Repeatability, Monitoring, and Retraining 3.6 SageMaker Lifecycle Service Map 3.7 ML Lifecycle Case Lab

4 Chapter 4: Generative AI Foundations and Inference Concepts

4.1 Foundation Models, LLMs, Transformers, and Modalities 4.2 Tokens, Context Windows, Embeddings, and Vector Search 4.3 Inference Parameters: Temperature, Top-p, and Output Controls 4.4 Hallucination, Grounding, and Context Quality 4.5 GenAI Use-Case Fit and Risk Triage 4.6 Prompt Injection, Data Leakage, and User Input Risk 4.7 Generative AI Foundations Case Lab

5 Chapter 5: Prompting, Model Selection, Customization, and Evaluation

5.1 Prompt Engineering Patterns and Business Quality 5.2 Zero-Shot, Few-Shot, Templates, and Instruction Design 5.3 Model Selection: Capability, Latency, Cost, and Risk 5.4 RAG vs Fine-Tuning vs Prompting vs Custom Models 5.5 Model Evaluation, Human Review, and Red-Team Feedback 5.6 Cost, Performance, and Throughput Decision-Making 5.7 Prompting and Model Selection Case Lab

6 Chapter 6: Amazon Bedrock, RAG, Agents, and Guardrails

6.1 Bedrock Core Concepts, Model Access, and Managed FM Choice 6.2 Knowledge Bases, RAG, Data Sources, and Grounding 6.3 AI Agents, Tools, Orchestration, and Business Workflows 6.4 Guardrails, Content Filters, Denied Topics, and Sensitive Data 6.5 Bedrock Model Evaluation, Monitoring, and Human Feedback 6.6 Bedrock Cost, Latency, Throughput, and Operational Fit 6.7 Bedrock, RAG, and Agents Case Lab

7 Chapter 7: AWS Managed AI/ML Services and SageMaker Map

7.1 Managed AI Services vs Foundation Model Apps vs Custom ML 7.2 Text, Language, Search, and Document AI Services 7.3 Vision, Speech, Contact Center, and Personalization Services 7.4 Amazon Quick, Amazon Q Developer, Kiro, and Practitioner Fit 7.5 SageMaker Canvas, Studio, Clarify, Autopilot, and Data Wrangler 7.6 Data Foundation Services: S3, Glue, OpenSearch, and Quick Sight 7.7 AWS AI Service Selection Case Lab

8 Chapter 8: Responsible AI, Human Review, and Safety

8.1 Fairness, Bias, Transparency, and Explainability 8.2 Privacy, Safety, Human Review, and Accountability 8.3 Guardrails, Clarify, Human Review, and Content Safety Controls 8.4 Responsible AI Risk Registers and Governance Workflows 8.5 Monitoring, Feedback, Drift, and Incident Response 8.6 Responsible AI Case Lab

9 Chapter 9: Security, Compliance, Governance, and Cost Controls

9.1 Shared Responsibility, IAM, and Least Privilege for AI 9.2 Encryption, Secrets, Networking, and Data Privacy 9.3 Prompt Injection, Data Exfiltration, and GenAI Threat Modeling 9.4 Logging, Monitoring, CloudTrail, CloudWatch, and Config 9.5 Compliance: Artifact, Config, Macie, and Policy Evidence 9.6 AI Cost Controls, Pricing, Throughput, and Budget Governance 9.7 Security and Governance Case Lab

10 Chapter 10: Integrated AWS AI Business Scenario Labs

10.1 Customer Support GenAI Assistant Lab 10.2 Document Intelligence and Compliance Review Lab 10.3 Personalization, Forecasting, and Fraud Detection Lab 10.4 Enterprise Search, RAG, and Knowledge Management Lab 10.5 Responsible AI and Security Review Board Lab 10.6 Cost, Performance, and Operations Review Lab 10.7 Full AIF-C01 Business Simulation

11 Chapter 11: Final Review, Exam Readiness, and Recertification

11.1 Final 30-Day AIF-C01 Study Plan 11.2 Official Practice Resources and Weak-Domain Remediation 11.3 90-Minute Exam Timing, Flagging, and Guessing Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Results, Retake, and Recertification Plan 11.6 AWS AI Practitioner Final Mixed Review

6.4 Guardrails, Content Filters, Denied Topics, and Sensitive Data

Key Takeaways Explain This Topic AI

Amazon Bedrock Guardrails evaluate user inputs and model responses to help enforce application-specific safety and policy controls.

Guardrail policies can include content filters, denied topics, word filters, sensitive information filters, contextual grounding checks, and other controls where supported.

Sensitive information filters can block or mask recognized PII and custom regex entities, but data privacy still requires application and logging design.

Guardrails are defense-in-depth, not a replacement for IAM, data classification, human review, prompt design, or business policy.

The safest rollout uses detect or test behavior first, reviews false positives and false negatives, then tunes policies before production enforcement.

Last updated: October 2026

Guardrails as application safety controls

Generative AI applications need boundaries. A customer assistant should not produce hateful content, reveal personal data, provide disallowed advice, or ignore a prompt injection that asks it to bypass policy. Amazon Bedrock Guardrails helps evaluate both user inputs and model responses. You can configure policies and then attach or reference guardrails in supported Bedrock inference and Knowledge Bases workflows. The goal is consistent safety behavior for a specific use case.

A guardrail is not a generic promise that an AI application is safe. It is a configured set of policies, messages, and handling behavior. It must match the application. A retail product assistant, an internal code helper, a benefits FAQ bot, and a financial services workflow may need different denied topics, sensitive data rules, and response messages. Practitioners should ask what policy the guardrail is enforcing, not merely whether a guardrail exists.

Guardrail policy area What it helps control Example practitioner use

Content filters Harmful categories such as hate, insults, sexual content, violence, misconduct, and prompt attacks where supported Reduce unsafe inputs or outputs in customer-facing chat.

Denied topics Topics the application should avoid Stop a banking assistant from giving prohibited investment advice.

Word filters Exact words or phrases to block Block profanity, restricted product terms, or custom phrases.

Sensitive information filters PII and custom regex entities Mask or block email, phone, account, or policy identifiers where appropriate.

Contextual grounding checks Whether responses are supported by provided context Flag or block ungrounded RAG answers.

Automated reasoning checks Logical rule or policy adherence where configured Validate that generated recommendations follow defined constraints.

Content filters are useful when the problem is unsafe or unwanted content. They can evaluate prompts and responses and can be configured by category and strength. Prompt attack detection is especially relevant for applications that use instructions, tools, or retrieved context. A prompt injection might tell the assistant to ignore previous instructions, reveal hidden prompts, or call an action outside policy. Guardrails can help detect these attempts, while the application should also use strict tool schemas and least privilege.

Denied topics are for business policy boundaries. If a health insurance assistant is approved only to explain enrollment deadlines and plan terms, a denied topic might block individualized medical advice. If a tax software assistant is approved only for product navigation, it may need to avoid legal tax advice. The denied topic description should be specific enough to guide detection, and the blocked response should tell users what the assistant can help with instead.

Sensitive information filters help detect standard PII patterns and custom regex entities in prompts or responses. Depending on configuration, sensitive data can be blocked or masked. This is valuable for transcript summarization, customer chat, and internal support tools. But masking is not a complete privacy program. If model invocation logging is enabled, teams must understand what inputs and blocked content may be written to CloudWatch Logs or S3 and protect those destinations with encryption, retention, and access controls.

Contextual grounding checks matter for RAG. They can help detect responses that are not supported by retrieved passages or that are irrelevant to the user's query. This is especially useful when a generated answer could be treated as policy or procedure. A good design combines citations, grounding checks, prompt instructions, source-quality controls, and human review for high-impact decisions. Do not use grounding checks to hide the fact that the corpus is outdated or poorly curated.

Guardrail rollout workflow:

Classify the application risk: public, internal, regulated, advisory, transactional, or creative.

Define unacceptable inputs, unacceptable outputs, sensitive entities, denied topics, and required refusal messages.

Test the guardrail with normal questions, edge cases, adversarial prompts, and false-positive examples.

Use detect or evaluation modes where available to understand behavior before strict blocking.

Tune category strengths, denied topic language, custom word lists, and sensitive data entities.

Review logging and retention because safety events can include sensitive text.

Monitor blocked rates, user complaints, missed policy violations, and business impact after launch.

Scenario: a customer support assistant summarizes chat transcripts. Sensitive information filters can mask PII in generated summaries, while content filters reduce harmful output. The application should still restrict which agents can view transcripts, store logs securely, and avoid sending unnecessary fields to the model. Guardrails reduce risk, but privacy-by-design starts before the prompt is built.

Scenario: an internal engineering assistant helps explain code. A prompt attack could be embedded in a README or issue description. Guardrails with prompt attack detection can help, but the tool should not have broad repository write access unless the workflow is explicitly designed for it. The safest pattern separates code explanation, code generation, and code-changing actions with different permissions and review steps.

For AWS Skill Builder practice, look for labs or demos that show guardrail testing. Change one policy at a time and observe which prompts are blocked, masked, or allowed. The learning goal is policy reasoning: identify the risk, choose the guardrail control, and explain what additional security or review control is still needed.