Study guide

3.1 Data Collection, EDA, Preprocessing, and Feature Concepts

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

3.1 Data Collection, EDA, Preprocessing, and Feature Concepts

Key Takeaways Explain This Topic AI

Good ML work starts with a clear business question, a usable target outcome, and data that is legally and operationally appropriate for the use case.

EDA helps teams find missing values, skew, leakage, class imbalance, outliers, bias signals, and data quality issues before training begins.

Preprocessing and feature concepts are in scope at practitioner-awareness level: know what they do, why they matter, and which risks they introduce.

AWS services such as Amazon S3, AWS Glue, Lake Formation, and SageMaker Canvas (which now includes Data Wrangler) support governed data preparation without making the AI Practitioner a data engineer.

Last updated: October 2026

From business question to usable data

For the AWS Certified AI Practitioner scope, data preparation is not about writing feature engineering code or building a data pipeline from scratch. It is about recognizing what must be true before a team can responsibly train, buy, or use an AI/ML solution. Start with the business question. A model for fraud review, churn prediction, document classification, demand forecasting, or image quality control needs a measurable outcome, a feedback path, and data that reflects the decision being supported.

A practitioner should ask whether the target is observable. If a team wants to predict customer dissatisfaction, does it have labeled examples such as survey scores, support escalations, cancellation events, or complaint categories? If it wants to detect defective parts from images, are defect labels consistent across inspectors? If it wants to forecast demand, are stockouts, promotions, holidays, and returns recorded in a way that explains historical sales? A vague goal such as improve operations is not enough.

Data can be structured, semi-structured, or unstructured. Structured data often lives in tables, such as orders, claims, customers, transactions, sensor readings, or account balances. Unstructured data includes text, images, audio, video, and scanned documents. AWS services may help store and catalog these sources. Amazon S3 is commonly used as durable object storage for datasets. AWS Glue can catalog and prepare data. Lake Formation can help govern access to data lakes.

Amazon Textract, Transcribe, Comprehend, and Rekognition can extract or analyze signals from documents, speech, text, and images when a managed AI service fits.

Data readiness question Why it matters Practitioner signal

Is the outcome defined? Training needs a target or objective Business owner can explain success and failure cases

Is the data permitted for this use? Privacy, consent, and policy can block use Data owner and security team approved the scope

Are labels reliable? Bad labels teach the wrong pattern Labeling rules are documented and reviewed

Is the sample representative? Models fail on groups not reflected in data Data covers regions, seasons, channels, and user groups

Is leakage controlled? A model may learn future or forbidden information Features are checked against deployment-time availability

  • Is there enough history? Sparse data limits learning and validation Team can explain coverage and known gaps
  • EDA as risk discovery

Exploratory data analysis, often shortened to EDA, is the review phase where teams inspect distributions, relationships, missing values, duplicates, class balance, outliers, and unexpected patterns. The AI Practitioner does not need to calculate every statistic by hand. The important skill is knowing what EDA is supposed to reveal and why a project should not skip it.

Missing values may be harmless, meaningful, or damaging. A blank income field may mean the customer did not provide it, the system failed to collect it, or the value is not applicable. An outlier may be a true high-value transaction, a sensor failure, or a data entry error. Class imbalance matters when the event being predicted is rare, such as fraud, equipment failure, or safety incidents. A naive model can look accurate by predicting the majority class and still be useless for the business.

EDA also helps reveal bias and fairness concerns. If historical approval data reflects biased human decisions, a model trained on that history can reproduce the pattern. If a dataset underrepresents certain customer groups, languages, locations, or device types, the model may perform unevenly. A practitioner should ask how the team evaluated performance across important segments, not just across the whole dataset.

Preprocessing and feature concepts

Preprocessing converts raw data into a form that a model or managed service can use. Common steps include cleaning invalid records, handling missing values, normalizing numeric ranges, converting categories into model-friendly values, splitting text into tokens, resizing images, and separating training and validation data. Feature engineering means creating useful input signals, such as days since last order, number of failed logins in the past hour, average basket size, or a flag for weekend transactions.

These tasks are out of scope as implementation work for the target candidate, but the concepts are in scope. If a model will be used in real time, a feature must be available at real-time inference. A feature based on tomorrow's cancellation status would be leakage. A feature that uses protected personal information may create compliance or fairness concerns. A feature that is expensive to compute may make the solution too slow or costly for production.

Checklist for a practitioner review:

Confirm the business owner can name the prediction or classification target.

Confirm the data owner approved the use of each source.

Ask whether sensitive fields, personally identifiable information, and regulated data are needed or can be minimized.

Ask how missing values, outliers, duplicates, and class imbalance were handled.

Ask whether the train, validation, and test splits reflect the deployment situation.

Ask whether any feature would be unavailable when the model is actually used.

Ask whether segment-level performance was reviewed for fairness and quality.

AWS tooling can support these steps without requiring the practitioner to become a builder. SageMaker Canvas can help business analysts explore data and create no-code ML models for some use cases. SageMaker Data Wrangler, now integrated into SageMaker Canvas, can help prepare and visualize data, including through a natural language interface. Data labeling may need an internal or vendor workforce; AWS's managed labeling service, SageMaker Ground Truth, is no longer open to new customers. The service choice should match team skill, governance needs, and the risk of the decision.

The key judgment is simple: poor data readiness should stop or narrow an AI project. More model complexity will not rescue undefined outcomes, unapproved data, biased labels, missing deployment-time signals, or a weak cost-benefit case.