Study guide
10.3 Personalization, Forecasting, and Fraud Detection 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.3 Personalization, Forecasting, and Fraud Detection Lab
Key Takeaways Explain This Topic AI
Personalization, forecasting, and fraud detection are separate use cases that share data-readiness, metric, monitoring, and governance concerns.
Amazon Personalize can support managed recommendations when interaction, user, and item data are available and privacy controls are understood.
Forecasting should be judged by time-series data quality, seasonality, business horizon, cost of errors, and whether no-code SageMaker Canvas or a custom SageMaker AI path is appropriate.
Fraud detection designs must be current with AWS service availability, because Amazon Fraud Detector is no longer open to new customers (since November 7, 2025).
A good decision log records data sources, labels, evaluation metrics, human review, false-positive cost, drift monitoring, and fallback rules.
Last updated: October 2026
Lab scenario: digital commerce growth and risk review
A subscription retail company wants three improvements in one quarterly initiative. Marketing wants personalized product recommendations in the web app. Operations wants a weekly demand forecast by product category and region. Risk wants better screening for suspicious account creation and checkout behavior. The executive sponsor asks whether one AI project can solve all three. The practitioner answer is that these are related by data and governance, but they need different designs, metrics, and risk controls.
Begin with use-case fit. Personalization predicts what a user may prefer next. Forecasting predicts future demand over time. Fraud detection estimates whether an event or account looks suspicious. All three can use machine learning, but none should be approved just because AI sounds modern. If the company lacks interaction data, stable item metadata, historical demand, or labeled fraud examples, the first project may be data collection and reporting rather than model deployment.
Use case Candidate AWS path Data readiness question Primary business metric
Recommendations Amazon Personalize Are user interactions, item metadata, and user metadata available with consent and quality controls? Click-through, conversion, revenue per session, or retention lift.
Forecasting SageMaker Canvas for no-code time-series forecasting, or SageMaker AI for custom ML Is there enough historical data by item, region, and time interval to capture seasonality? Forecast error, stockout reduction, waste reduction, or staffing accuracy.
Fraud screening AWS WAF Fraud Control for account creation or login abuse, existing Amazon Fraud Detector where already approved, or SageMaker AI for custom models Are labels, outcomes, device or event features, and human review decisions captured? Fraud loss reduction balanced against false-positive friction.
Reporting baseline Quick Sight, S3, Glue, Redshift, or existing BI Can stakeholders see current trends before adding predictions? Decision speed, data trust, and adoption.
For personalization, Amazon Personalize is a managed service for creating individualized recommendations. A practical lab uses an interactions dataset with user ID, item ID, timestamp, and event type, plus item metadata such as category, price band, and availability. The team defines what good means: more relevant products, higher engagement, or lower churn. It also defines what is not allowed: using sensitive attributes without approval, recommending unavailable products, or creating a filter bubble that hides important required content.
Personalization failure modes are common. Cold-start users and new items may lack enough interaction history. Biased historical behavior may over-promote already popular products. Missing inventory data may recommend items that cannot ship. Privacy rules may restrict the use of age, location, or health-related attributes. A responsible pilot includes exploration settings where supported, filters for inventory or eligibility, opt-out handling, and monitoring for unexpected recommendation patterns.
For forecasting, the question is not whether the model is clever. It is whether the time-series signal supports the planning decision. Weekly demand by product category may need two or more years of history if seasonality matters. Promotions, price changes, holidays, supply disruptions, and regional launches can make raw history misleading. SageMaker Canvas can be a good practitioner-level path when analysts need no-code forecasting experiments. SageMaker AI can fit custom forecasting work when builders need more control.
Quick Sight can help stakeholders review forecasts and actuals, but dashboards do not fix poor history.
Forecasting failure modes include data leakage from future fields, confusing orders with shipped units, ignoring stockouts, using too short a history window, and optimizing a technical metric that does not match business cost. A 10 percent error may be acceptable for a low-margin accessory but costly for staffing a support center. The decision log should state forecast horizon, refresh cadence, level of aggregation, acceptable error, and who can override the forecast.
For fraud screening, service selection requires current availability awareness. Amazon Fraud Detector has historically been an AWS managed service for online fraud use cases, but it is no longer open to new customers as of November 7, 2025; for similar capabilities, AWS points to Amazon SageMaker, AutoGluon, and AWS WAF. If an organization already uses it, the decision log should reference current account access and migration planning. New account-creation or login abuse may fit AWS WAF Fraud Control.
Custom transaction fraud may require SageMaker AI, AutoGluon, rules, human review, or a partner solution depending on labels and risk.
Fraud failure modes are high impact. False positives can block good customers and create support cost. False negatives create financial loss. Biased training data can unfairly challenge certain users. Attackers adapt after controls are deployed. The workflow should combine model scores, deterministic rules, step-up verification, human review for borderline cases, CloudWatch monitoring, and clear appeal paths. Never treat a fraud score as a final moral judgment about a customer.
Decision log prompts:
Which data fields are used, who owns them, and what privacy basis permits their use?
Which metric proves value for each use case, and what is the cost of being wrong?
Which predictions are automatic, which require human review, and which only inform a dashboard?
How will the team detect data drift, model drift, seasonal change, and degraded business outcomes?
What fallback rule applies if the prediction service is unavailable or produces low confidence output?
Review prompts before the quiz:
Which of the three use cases has the strongest data today?
Which use case has the highest customer harm if the model is wrong?
Where is a rules-based or reporting-only solution enough for the first release?
Which AWS service choice must be verified against current availability before approval?
What dashboard would show that predictions are improving decisions rather than adding complexity?