Study guide
7.5 SageMaker Canvas, Studio, Clarify, Autopilot, and Data Wrangler
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
7.5 SageMaker Canvas, Studio, Clarify, Autopilot, and Data Wrangler
Key Takeaways Explain This Topic AI
Amazon SageMaker AI is the AWS path for deeper custom ML lifecycle control, while Canvas, Studio, Clarify, Autopilot, and Data Wrangler serve different roles inside that ecosystem.
SageMaker Canvas supports no-code or low-code analysis and prediction workflows for users who need ML outcomes without writing full training code.
SageMaker Studio is the builder workspace for data scientists and ML engineers who need notebooks, experiments, models, and lifecycle tools.
SageMaker Clarify supports bias and explainability analysis for existing customers (it is no longer open to new customers), which helps practitioners connect ML quality with responsible AI expectations.
Autopilot and Data Wrangler (both now surfaced through SageMaker Canvas) can reduce build effort, but they do not remove the need for data readiness, evaluation, monitoring, and business accountability.
Last updated: October 2026
Reading the SageMaker AI map
Amazon SageMaker AI is the service family to recognize when the organization needs deeper custom ML control. It is broader than one console screen. SageMaker includes tools for data preparation, notebooks, experiments, training, model building, deployment, monitoring, governance, and collaboration. For the AWS AI Practitioner level, the point is not to implement pipelines. The point is to recognize which part of SageMaker matches a role and a lifecycle need.
SageMaker Canvas is the analyst-friendly entry point. It supports no-code or low-code ML workflows where business analysts and other non-specialist users can explore data, build predictions, and use managed capabilities with less code. Canvas can be a good fit when the business has a tabular prediction problem and wants to evaluate value before committing to a full data science project. The practitioner should still ask about data quality, labels, leakage, metrics, approval, and production ownership.
SageMaker Studio is the builder workspace. Data scientists and ML engineers use Studio when they need notebooks, experiments, code, model development, training jobs, and deeper lifecycle control. Studio is not necessary for every practitioner-facing AI use case. If a team only needs document extraction, transcription, enterprise search, or a managed assistant, another service may be more appropriate. Studio becomes relevant when custom model development is actually required.
SageMaker Clarify supports responsible AI analysis for bias and explainability. AWS says Clarify is no longer open to new customers; existing customers can continue to use it, and AWS documents a replacement path built on the same standardized bias metrics, the SHAP library, SageMaker AI monitoring solutions, and Amazon Bedrock Evaluations. It helps teams examine whether features or data patterns may create unfair outcomes and how model predictions can be explained. Clarify does not make a model fair by magic. It provides evidence that teams can use during governance review. Practitioners should ask what protected or sensitive attributes matter, what fairness criteria apply, and how findings will affect launch decisions.
SageMaker Autopilot automates parts of model building. It can explore algorithms and generate candidate models so teams can compare options faster. Autopilot can reduce manual work, but it does not remove the need to validate data, choose meaningful metrics, avoid leakage, evaluate business risk, and monitor results after deployment. It is most useful when the organization has a machine learning problem and wants help generating baseline models. Since November 30, 2023, Autopilot's user interface has been moving into SageMaker Canvas; builders can still use its AutoML APIs.
Data Wrangler supports data preparation and transformation, and it is now integrated into SageMaker Canvas, where users can also explore and transform data in natural language. Data work often consumes more effort than model selection. Missing values, inconsistent categories, duplicate records, date formats, outliers, and label errors can all damage results. Data Wrangler helps teams prepare data visually and reproducibly, but a practitioner should remember that feature engineering and data engineering implementation are out of scope for the target candidate. The expected skill is recognizing why data preparation matters.
SageMaker capability Primary user Best fit Practitioner question
SageMaker Canvas Analyst or line-of-business user No-code or low-code predictions and exploration Is the problem simple enough to evaluate without a full custom ML project first?
SageMaker Studio Data scientist or ML engineer Custom model development and lifecycle work Does the team need notebooks, experiments, training, hosting, or pipelines?
SageMaker Clarify ML team, risk team, governance reviewer Bias and explainability analysis (existing customers only) Which fairness and explanation questions must be answered before use?
SageMaker Autopilot ML builder or analyst-supported team Automated model candidate exploration (UI now in Canvas) Are the data, target label, metric, and evaluation plan meaningful?
Data Wrangler Data scientist or analyst Data preparation and transformation (now inside Canvas) Is the source data clean enough for trustworthy ML?
The service boundary between Bedrock and SageMaker AI is important. Bedrock is usually the managed foundation model application choice when the task is generation, summarization, chat, RAG, or agents. SageMaker AI is the custom ML path when teams need model development and lifecycle control. Both can appear in the same organization, but the reason to choose each service should be explicit.
A practitioner should also understand the gap between prototype and production. Canvas or Autopilot may help prove that a prediction is useful. That does not automatically mean the model is approved for production use. Production requires owners, monitoring, retraining plans, cost awareness, rollback options, access controls, and user support. High-impact decisions also require fairness, explainability, and human review plans.
Use this SageMaker readiness checklist:
Confirm the prediction target and business decision the model will support.
Check whether a managed AI service or foundation model app would solve the problem with less custom ownership.
Identify the data source, label quality, update cadence, sensitivity, and expected drift.
Choose the SageMaker capability that matches the user role and lifecycle stage.
Define metrics, baseline comparison, human review, and governance requirements before launch.
Plan how results will be monitored and who can pause or change the model.
Skill Builder practice should focus on the map. Open training that introduces Canvas, Studio, and responsible AI concepts, then describe who uses each tool and why. A non-builder does not need to become a data scientist. They need enough fluency to ask whether the organization is starting a custom ML lifecycle by accident or by design.