Study guide

2.7 AI/ML Foundations Case 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

2.7 AI/ML Foundations Case Lab

Key Takeaways Explain This Topic AI

Case analysis should identify the business decision, data type, learning pattern, inference pattern, AWS service fit, and no-AI fallback.

A strong practitioner recommendation includes governance, human review, monitoring, and cost implications, not only a service name.

Different parts of one workflow may use different approaches, such as rules for policy enforcement and AI for ambiguous triage.

Official study practice should use AWS Skill Builder, official practice resources, and hands-on console review rather than unauthorized memorization sources.

Last updated: October 2026

Case Method for Practitioner Decisions

A case question rarely rewards naming the most advanced service. It rewards matching the business problem to the simplest controlled approach. Start by writing the decision the business wants to improve. Then identify the input data, desired output, timing, risk, and user. Finally compare AWS service paths with a no-AI option. This habit prevents overbuilding and keeps governance visible.

Use the same case worksheet each time. What is the business action? What data type is involved? Is there a label, no label, or reward signal? Is the output a category, number, group, forecast, ranked list, extraction, or generated response? Does the decision need batch, real-time, or embedded inference? What happens when the model is wrong? Which AWS service is the smallest fit?

  • Case dimension What to capture Why it matters
  • Decision The action changed by the output Proves the use case is not vague
  • Data Type, source, quality, permissions Drives service choice and governance
  • Learning pattern Supervised, unsupervised, reinforcement, or not ML Clarifies labels and validation
  • Inference pattern Batch, real-time, asynchronous, or embedded Drives cost, latency, and fallback design
  • AWS path Managed AI, Bedrock, Amazon Quick, SageMaker, analytics, rules Prevents tool-first reasoning
  • Control Human review, IAM, logging, monitoring, retention Makes approval defensible

Case 1: a regional insurer receives thousands of emailed claim documents each week. Staff manually read forms, extract claim numbers and dates, and route incomplete packets for follow-up. The data is document and text. The output is extracted fields plus a completeness decision. Amazon Textract is a strong first service for extraction, with human review for low-confidence or high-value cases. A deterministic checklist can enforce required fields.

The same insurer asks whether a model should approve claims automatically. That is a different and higher-risk decision. The team would need labels, policy clarity, fairness review, auditability, and a human escalation path. The correct recommendation may split the workflow: use AI to extract and prioritize information, but keep claim approval under deterministic policy and trained human review until evidence supports further automation.

Case 2: a retail site wants to improve product discovery. Search logs, purchases, views, carts, and product metadata are available. A recommendation pattern may fit, and Amazon Personalize is relevant if interaction data is sufficient and permitted. For new users or sparse data, popular products, merchandising rules, and search tuning may be needed. The service decision should include privacy, cold start behavior, and business metrics such as conversion and returns.

Case 3: an internal IT team wants a helper for employees who ask cloud support questions. The input is internal documentation and user questions. The output is generated guidance with links or citations. Amazon Quick or an Amazon Bedrock retrieval workflow may fit, but only if the knowledge source is curated, current, and access-controlled. If the question requires an exact account-specific fact, the assistant should retrieve from an authorized system rather than invent an answer.

Case 4: a warehouse manager wants to know how many workers are needed next Friday. Historical volume, staffing, promotions, holidays, and seasonality may support forecasting or regression. If the location has only a few weeks of data, a spreadsheet baseline may beat a model. If many locations have years of history, SageMaker Canvas or a governed SageMaker AI approach may help. The metric should be scheduling accuracy and overtime reduction, not model novelty.

Case 5: a finance leader wants every report to include a written summary. If the report is a stable Amazon Quick Sight dashboard with a few metrics, a templated narrative may be more reliable than free-form generation. If analysts need natural language drafts across many changing datasets, a generative workflow may help. The team should define source data, review responsibility, allowed tone, and how to prevent unsupported conclusions.

Case 6: a security team wants to detect abnormal sign-in behavior. This may involve anomaly detection, supervised classification if labels exist, or rules for known high-risk conditions. It also involves security services and governance beyond ML. A practitioner should ask whether the output informs analysts, blocks access, or starts an incident workflow. The more direct the action, the stronger the need for explainability, logging, and human override.

Practice drill:

Pick one case above and write the business decision in one sentence.

List the data type and whether labels exist.

Choose the task pattern and inference pattern.

Pick the first AWS service or non-AI path to evaluate.

Name one governance risk and one human review point.

Define one business metric and one model or output quality metric.

Compare your answer with AWS Skill Builder lessons and official practice resources, not unauthorized memorization sources.

When using AWS Skill Builder or the AWS console for reinforcement, focus on recognition and judgment. Open service pages for Amazon Bedrock, Amazon Quick, SageMaker AI, SageMaker Canvas, Textract, Comprehend, Rekognition, Transcribe, Translate, Polly, Lex, and Personalize. For each service, write one use case it fits, one use case it does not fit, one data requirement, and one governance question.

A good final case answer has a clear shape: recommend a path, explain why it fits the data and decision, name the risk, and state the fallback. For example, use Textract to extract invoice fields, route uncertain fields to human review, apply deterministic approval thresholds, and monitor error rates. That answer is stronger than simply saying use AI because it separates extraction, policy, review, and monitoring.