Study guide

5.5 Model Evaluation, Human Review, and Red-Team Feedback

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

5.5 Model Evaluation, Human Review, and Red-Team Feedback

Key Takeaways Explain This Topic AI

Model evaluation compares candidate outputs against business quality, safety, cost, latency, and reliability criteria before production approval.

Human review is essential when model outputs affect customers, regulated decisions, safety, financial outcomes, or brand risk.

Red-team testing probes misuse, prompt injection, data leakage, unsafe content, hallucination, and policy bypass attempts.

Evaluation is continuous because model versions, prompts, retrieval sources, user behavior, and business policies change over time.

Last updated: October 2026

Evaluation Is A Lifecycle, Not A One-Time Score

A foundation model application should not be approved because one demo looks impressive. Evaluation asks whether the system performs well enough for the intended audience, data, risk, cost, and workflow. It compares model outputs to a defined rubric and gathers evidence before broader rollout.

For AWS AI Practitioner study, evaluation should be understood at a practical level. Amazon Bedrock includes model evaluation capabilities that can help compare models for supported tasks. Teams may also create their own evaluation sets, use human reviewers, review CloudWatch metrics, and collect user feedback. The point is to create a repeatable decision process.

Evaluation area Example question Evidence source

Task quality Did the output answer the user need? Human rubric, labeled examples, acceptance tests.

Grounding Did the answer use approved context only? Source review, RAG logs, citation checks.

Safety Did it avoid harmful, biased, or restricted content? Guardrail tests, red-team prompts, policy review.

Reliability Does it behave consistently across cases? Regression test set and repeated runs.

Latency Is response time acceptable for the workflow? Application metrics and user testing.

Cost Is token and retrieval cost sustainable? Usage reports, budgets, cost allocation tags.

Evaluation starts with a test set. A support assistant might need common questions, rare issues, angry customer messages, missing data, restricted policy cases, and prompt injection attempts. A document summarizer might need short, long, messy, and sensitive documents. A sales drafting tool might need multiple customer segments and compliance language.

A rubric makes review less subjective. Instead of asking whether the answer is good, ask whether it is accurate, complete, grounded, concise, policy-compliant, and actionable. Each category can be scored by human reviewers. The team should also define automatic failure conditions, such as exposing personal data, inventing policy, giving unsafe advice, or taking an action without approval.

Human review is not only for training data. It is a production control. Amazon Bedrock model evaluation jobs can use human workers to rate outputs, and organizations can build approval steps into their applications (Amazon Augmented AI, AWS's older human-review service, is no longer open to new customers). Human review is especially important when outputs affect customers, regulated processes, safety, finance, employment, medical, legal, or security decisions.

Human review checklist:

Define which outputs require review before use.

Train reviewers on the rubric and escalation rules.

Capture reviewer feedback in a structured way.

Separate harmless edits from serious safety or grounding failures.

Use feedback to update prompts, retrieval sources, guardrails, or workflow limits.

Monitor reviewer workload so review does not become a hidden bottleneck.

Red-team testing is adversarial testing. It tries to make the system fail before real users or attackers do. For a generative AI application, red-team prompts may request secrets, ask the model to ignore instructions, inject malicious instructions through retrieved documents, demand restricted content, or try to manipulate an agent into taking unauthorized actions.

Prompt injection is a key risk. A user or document may contain instructions such as ignore the previous rules or reveal hidden system instructions. The practitioner does not need to implement security controls, but should recognize that prompt injection is a governance and design issue. The response may include strict instruction hierarchy, input filtering, retrieval controls, guardrails, least privilege, and human approval for sensitive actions.

Bias and fairness also belong in evaluation. If an AI workflow influences recommendations, triage, prioritization, or customer treatment, the team should test whether outputs differ unfairly across groups. SageMaker Clarify is the AWS capability associated with bias detection and explainability in ML workflows; it is no longer open to new customers, although the AIF-C01 version 1.1 revision table still names it under objective 4.2.2. At practitioner level, know when fairness review is needed and when a business owner should be involved.

Production feedback closes the loop. Users should be able to flag poor responses. Logs and metrics should show failure patterns, latency spikes, cost changes, and safety events. CloudWatch can help monitor operational metrics, while CloudTrail can support audit visibility for AWS API activity. Evaluation should be repeated after prompt, model, retrieval, guardrail, or policy changes.

A strong approval packet is practical: use case, audience, model choice, data sources, prompt template, guardrails, evaluation results, known limitations, human review path, cost estimate, monitoring plan, and rollback plan. This is the kind of evidence a non-builder stakeholder should ask for before approving production AI.