Study guide
10.5 Responsible AI and Security Review Board Lab
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
10.5 Responsible AI and Security Review Board Lab
Key Takeaways Explain This Topic AI
A review board should ask practical questions about fairness, explainability, privacy, safety, transparency, accountability, and human oversight without pretending every project needs the same control set.
Security review must cover IAM least privilege, encryption, data classification, prompt injection, logging, retention, monitoring, and shared responsibility.
AWS services such as Amazon Bedrock Guardrails, bias and explainability analysis, human review, Macie, CloudTrail, CloudWatch, AWS Config, Artifact, KMS, and Secrets Manager support different review needs.
AIF-C01 practitioners should know what evidence to request and when to escalate, not implement full governance frameworks or custom security protocols.
The board decision should be documented as approve, approve with conditions, defer, or reject, with owners and review dates.
Last updated: October 2026
Lab scenario: review board for AI launch approval
A company has three AI proposals ready for review: a support assistant, a document summarizer, and a churn-risk dashboard. The review board includes product, security, privacy, legal, compliance, operations, and customer support leaders. The board is not there to write code or tune models. Its job is to decide whether each use case has enough evidence, control, ownership, and monitoring to move forward responsibly.
At the practitioner level, responsible AI is a set of concrete questions. Is the use case appropriate for AI? Could the output harm a person, customer, employee, or regulated decision? Is the data permitted for this use? Can users tell when AI is involved? Is there a human review path? Are errors monitored? Who owns remediation? The board should avoid both extremes: approving everything because a managed service is used, or blocking every project because AI has risk.
Review area Evidence to request AWS-related control examples
Use-case fit Business goal, non-AI baseline, risk tier, user impact Well-Architected review questions and documented architecture.
Fairness and bias Affected user groups, labels, evaluation slices, complaint path Bias metrics and subgroup analysis (SageMaker Clarify for existing customers), business review of model outcomes.
Explainability Reason codes, citations, feature importance, reviewer notes RAG citations, model evaluation records, SHAP feature attributions where relevant.
Privacy Data inventory, consent or lawful basis, retention, redaction Macie, KMS, S3 bucket policies, IAM, log retention controls.
Safety Unsafe content, prompt attacks, denied topics, human handoff Amazon Bedrock Guardrails and application escalation rules.
Accountability Decision owner, approval owner, incident owner, review cadence Ticketing records, CloudTrail, CloudWatch, AWS Config evidence.
Security Least privilege, secrets, encryption, network path, monitoring IAM, KMS, Secrets Manager, CloudTrail, AWS Config, Inspector, Trusted Advisor.
The board should classify each proposal by impact. A low-risk internal summarizer of public release notes may need light review. A model that recommends account closure, credit denial, medical advice, or employee discipline needs deeper review, legal analysis, human oversight, and likely should not be automated casually. The AIF-C01 candidate is not expected to build a governance framework, but should recognize that risk level drives controls.
Responsible AI evidence should be specific. For the support assistant, ask for the prompt template, source corpus, retrieval tests, guardrail settings, sample bad-answer review, and human approval workflow. For the document summarizer, ask for extraction confidence thresholds, reviewer authority, sensitive data handling, and audit evidence. For the churn dashboard, ask which features are used, whether protected or proxy attributes are present, how false positives are handled, and whether customers or employees are affected by the prediction.
Security review starts with identity and data. Use IAM least privilege for application roles and service roles. Store secrets in AWS Secrets Manager, not in prompts or code. Encrypt data at rest with KMS where appropriate and protect data in transit. Decide whether prompt and response logs are stored, what they may contain, who can read them, and how long they are retained. Use CloudTrail for API activity, CloudWatch for operational metrics, and AWS Config and AWS Artifact where the organization needs configuration or compliance evidence.
Prompt injection belongs on the board agenda. A malicious user or a document inside a RAG corpus can tell a model to ignore instructions, reveal hidden prompts, call tools, or leak data. Controls include Guardrails, strong prompt boundaries, retrieval source governance, narrow action schemas, least-privilege tool roles, and human approval for sensitive actions. The board should ask for adversarial test examples, not only positive demos.
Decision log template:
Proposal name and business owner.
AI function: classify, recommend, generate, summarize, retrieve, forecast, or automate.
Risk tier and reason.
Data sources, data classes, retention, and access boundaries.
Human review point and escalation owner.
Evaluation evidence, including normal cases, edge cases, and unacceptable outputs.
Security controls, logging, monitoring, and incident response path.
Board decision: approve, approve with conditions, defer, or reject.
Re-review trigger: new data source, new model, new audience, new action capability, or incident.
Failure modes should change the decision. If nobody owns source content, defer the RAG assistant. If customer data appears in unprotected logs, reject production use until logging is corrected. If a churn model uses a proxy for a sensitive attribute, require fairness review before launch. If a document summarizer cannot show source evidence for generated conclusions, keep it in assistive review mode. If an agent can call broad administrative APIs, narrow its tool list before approval.
Review prompts before the quiz:
Which proposal has the highest user harm if the AI is wrong?
What proof shows that human reviewers can override the AI?
Which logs or prompts might contain sensitive data?
Which data source, model, or audience change should force re-review?
What condition would make the board reject rather than approve with conditions?