Study guide

2.6 Classification, Regression, Clustering, Forecasting, and Recommendation

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.6 Classification, Regression, Clustering, Forecasting, and Recommendation

Key Takeaways Explain This Topic AI

Classification predicts a category, regression predicts a number, clustering discovers groups, forecasting predicts future values over time, and recommendation ranks items or actions.

The correct pattern depends on the output the business will consume, not on the tool name alone.

Metrics should connect model performance to business value, cost, risk, and user feedback.

AWS service selection ranges from managed AI services and Amazon Personalize to SageMaker Canvas, SageMaker AI, analytics tools, and no-AI rules.

Last updated: May 2026

Name the Output First

Classification predicts a category. The output might be fraud or not fraud, urgent or routine, approved or rejected, positive or negative sentiment, or document type. Classification is often easy to explain to business users because the result is a label. The risk is that a label can hide uncertainty. A low-confidence classification may need review, especially when it affects money, access, safety, or customer treatment.

Regression predicts a number. The output might be expected demand, claim amount, delivery duration, churn probability, or risk score. Some scores are technically numeric but are used like classifications when a threshold triggers action. Practitioners should ask how thresholds are chosen, who can override them, and whether the numeric output is calibrated well enough for the decision.

Clustering discovers groups in data without a known target label. A marketing team might find behavior segments, or an operations team might group similar incidents. Clustering can reveal structure, but it does not automatically produce a decision. The team needs analysts and domain experts to name clusters, check for fairness issues, and decide whether action based on clusters is useful.

Forecasting predicts future values over time. The time dimension is essential. A forecast might estimate next month's demand, next week's call volume, or future infrastructure usage. Good forecasting needs historical data, seasonality awareness, event context, and validation that respects the timeline. A forecast should be compared with a simple baseline, because complex models do not always beat a well-understood planning rule.

Recommendation ranks items, content, products, offers, or next actions. The goal is usually to personalize or prioritize. Amazon Personalize is the managed service to consider for recommendation scenarios when user-item interaction data exists. A recommendation system can improve engagement, but it can also create stale suggestions, popularity bias, privacy concerns, or unfair exposure for new items.

Pattern Output Example question Possible AWS path Common metric lens

Classification Category Which queue should handle this ticket? Comprehend, Rekognition, SageMaker Canvas, SageMaker AI Accuracy, precision, recall, F1, review rate

Regression Number What will this claim cost? SageMaker Canvas or SageMaker AI Error size, business cost of over or under estimate

Clustering Group Which customers behave similarly? SageMaker AI, analytics, embeddings and search Stability, interpretability, action value

Forecasting Future value How much demand next week? SageMaker options and analytics workflows Forecast error versus baseline

Recommendation Ranked list Which product should appear next? Amazon Personalize or custom ML Clicks, conversion, relevance, diversity

Metrics must match the business risk. Accuracy may be misleading when the important class is rare, such as fraud. Precision asks how many flagged items are truly relevant. Recall asks how many relevant items were found. F1 balances precision and recall. AUC can help compare ranking ability. For a practitioner, the key is not memorizing formulas but knowing that the wrong metric can approve the wrong solution.

Business metrics matter too. A fraud model should reduce losses without creating unacceptable false declines. A recommendation model should improve conversion without damaging trust. A forecast should improve inventory decisions, not just produce a lower mathematical error. A document classifier should reduce handling time while maintaining quality. User feedback can reveal whether model outputs are helpful inside the actual workflow.

Service selection should start with the pattern and data. If the task is generic text classification or sentiment, Amazon Comprehend may fit. If the task is custom classification from tabular data and a business team wants to prototype, SageMaker Canvas may fit. If the organization needs a governed custom lifecycle, SageMaker AI is relevant. If the output is a ranked list of products for users, Amazon Personalize deserves consideration.

Generative AI can support these patterns but does not replace all of them. A foundation model can summarize why a customer might churn, generate an explanation for a human reviewer, or convert unstructured text into structured fields. However, a probabilistic generated paragraph is not the same as a validated classification model, a calibrated numeric forecast, or an auditable rule. Use Bedrock where generation or language reasoning is the value.

Use this quick mapping workflow:

Ask what the output looks like: category, number, group, future time value, or ranked list.

Confirm what historical data supports that output.

Choose a metric tied to the cost of wrong outputs.

Decide whether a managed AI service, Amazon Personalize, SageMaker Canvas, SageMaker AI, or a rule is the simplest fit.

Define human review and monitoring for high-risk or low-confidence results.

Scenario: an insurer wants to estimate claim cost. That is regression if the output is a dollar estimate. If the workflow only needs low, medium, or high complexity, classification may be better. If the estimate triggers payment or denial, the risk profile changes and human review becomes important. The service choice could start with SageMaker Canvas for exploration, but production ownership may require a fuller SageMaker AI and governance path.

Scenario: a streaming service wants to suggest the next video. That is recommendation, not simple classification. Amazon Personalize may fit if user-item interactions are available and permitted. A new catalog with little user behavior may need editorial rules or popularity lists first. The practitioner should ask how the team will handle new users, new items, inappropriate recommendations, and diversity of results.