Study guide
4.5 GenAI Use-Case Fit and Risk Triage
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
4.5 GenAI Use-Case Fit and Risk Triage
Key Takeaways Explain This Topic AI
Generative AI is strongest when the task benefits from language, summarization, drafting, explanation, transformation, retrieval, or creative variation.
Generative AI is weaker when the outcome must be fully deterministic, the data is poor, the risk is high without review, or a simpler service already solves the problem.
Use-case triage should examine business value, data readiness, user impact, governance needs, cost, latency, and measurable success.
AWS service selection should compare Amazon Bedrock, Amazon Quick, managed AI services, SageMaker AI, and non-AI alternatives before committing.
Last updated: October 2026
Start with the job to be done
Generative AI is a good candidate when the work involves natural language, unstructured content, synthesis, explanation, or creative variation. Examples include summarizing call transcripts, drafting support replies, helping employees search internal documents, producing first-pass marketing copy, generating product description variants, translating tone, or extracting a structured summary from a long report. The common thread is that a useful answer may be expressed in natural language and may benefit from flexible reasoning over context.
Generative AI is not automatically the right answer for every automation request. If the business needs a fixed calculation, a rule engine or normal application code may be better. If the data is missing, stale, restricted, or poorly owned, a model will not fix the governance problem. If the output can cause harm without review, the workflow needs human oversight or may be inappropriate. If an AWS managed AI service solves the task directly, such as Amazon Comprehend for language insights or Amazon Rekognition for image analysis, a general foundation model may be unnecessary.
Use-case fit also depends on the user experience. A draft-assist tool that keeps a human in control has a different risk profile than a fully automated customer-facing assistant. A search helper that cites policy pages is different from a model that gives final approval on a claim. A creative ideation tool can tolerate some variation. A compliance workflow needs traceability, consistency, and escalation.
Triage matrix
Dimension Low-risk signal Higher-risk signal Question to ask
Business value Clear time savings or better access to information Vague innovation goal What metric will prove value?
Data readiness Approved, current, searchable content Unknown owners, duplicates, sensitive data Who owns the source of truth?
User impact Human reviews output before action Automated decision affects customers or rights What happens if the answer is wrong?
Service fit Managed service or Bedrock app fits Custom build chosen without reason Is there a simpler AWS service or non-AI approach?
Governance IAM, logging, review, and retention planned No policy for prompts, outputs, or data use Who approves launch and monitors drift?
Cost and latency Token use and model choice are tested Large prompts and slow answers assumed acceptable What is the operating cost per workflow?
This matrix helps a non-builder candidate sound practical. It is not enough to say a use case is cool or that a model is powerful. A sponsor should ask whether the model's strengths match the work and whether the organization can operate the solution responsibly. The exam guide targets candidates who understand business applications of AI on AWS, not candidates who implement model algorithms. That makes triage questions central.
AWS service-choice patterns
Amazon Bedrock is a natural fit when a team needs managed access to foundation models and wants to build a generative AI application with prompts, retrieval, agents, or guardrails. Amazon Quick (for business users) or Amazon Q Developer and Kiro (for builders) are better to investigate when the desired outcome is an AWS-managed assistant experience. SageMaker AI is relevant when a builder team needs deeper ML development, model training, customization, deployment, or lifecycle control.
AWS managed AI services such as Amazon Translate, Transcribe, Polly, Textract, Comprehend, Rekognition, and Personalize may fit narrow tasks without a custom foundation-model application.
The option of not using AI should stay on the table. A deterministic approval rule, a database query, a search filter, or a dashboard in Amazon Quick Sight may solve the business problem with less risk. Generative AI adds value when flexibility, language understanding, or synthesis matters enough to justify model cost and controls. It adds noise when the task is already precise, governed by fixed rules, or better served by existing software.
A practical triage workflow looks like this:
Write the user story in one sentence, including who uses the output and what decision follows.
Classify the output as draft, recommendation, search result, transformation, or automated action.
Identify the source of truth and whether it is ready for retrieval or prompting.
Rate potential harm from an incorrect, biased, unsafe, or leaked response.
Compare AWS service choices and a non-AI baseline.
Define success metrics such as time saved, answer acceptance, escalation rate, cost per request, and user feedback.
Plan review and monitoring before broad rollout.
This workflow keeps teams from overbuilding. It also keeps them from rejecting useful generative AI too early. A well-scoped draft assistant, internal knowledge assistant, or summarization workflow can be valuable when the data is governed and users know the output is an aid. The same model pattern can be inappropriate if it makes final decisions without accountability.