Study guide
3.6 SageMaker Lifecycle Service Map
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.6 SageMaker Lifecycle Service Map
Key Takeaways Explain This Topic AI
Amazon SageMaker AI is a managed service family for building, training, deploying, and operating ML models, but AI Practitioner knowledge stays at service-selection and lifecycle-awareness depth.
SageMaker Canvas supports no-code ML exploration for business users, while Studio and related capabilities support more technical ML workflows.
SageMaker capabilities map to lifecycle needs such as labeling, data preparation, training, model registry, deployment, monitoring, explainability, and pipelines.
Practitioners should know when SageMaker is appropriate and when a managed AI service, Amazon Bedrock, or a simpler non-ML workflow is a better fit.
Last updated: October 2026
Why SageMaker appears in lifecycle questions
Amazon SageMaker AI is a managed AWS service family for ML workflows. It can support data preparation, labeling, training, evaluation, model management, deployment, monitoring, explainability, and pipeline automation. For the AWS AI Practitioner, the goal is not to become a SageMaker engineer. The goal is to understand how SageMaker fits when a team needs custom ML capabilities beyond a managed AI API.
Use SageMaker when the organization needs to train, customize, host, or operate models with more control. Use managed AI services when the task already matches a packaged capability such as transcription, translation, document extraction, text analysis, image analysis, or speech generation. Use Amazon Bedrock when the use case is generative AI with foundation models, prompts, RAG, agents, model evaluation, or guardrails. Use no-code or low-code options when they meet the need with less engineering burden.
SageMaker includes features aimed at different audiences. SageMaker Canvas can help business analysts prepare data, generate predictions, and explore no-code ML for supported use cases. More technical teams may use Studio, notebooks, training jobs, processing jobs, model registry, endpoints, and pipelines. A practitioner should know the audience and governance boundary. A business user creating a forecast in Canvas is not the same operating model as an ML engineer deploying a real-time endpoint.
Lifecycle need SageMaker capability to recognize Practitioner meaning
Label data SageMaker Ground Truth (no longer open to new customers) Helps create labeled datasets with human or automated labeling workflows
Prepare and inspect data SageMaker Canvas data preparation (Data Wrangler is now integrated into Canvas) Supports visual preparation and exploration of data
Build no-code models SageMaker Canvas Lets analysts create ML predictions without writing training code for supported scenarios
Train custom models SageMaker training jobs, built-in algorithms, custom containers Requires ML skills and governed training data
- Find starting models SageMaker JumpStart Provides pretrained models and solution templates to evaluate
- Track model versions SageMaker Model Registry Supports versioning, approval states, and model lineage
- Deploy models SageMaker endpoints, batch transform Serves real-time or batch predictions
Monitor models SageMaker Model Monitor (no longer open to new customers) Helps detect data quality and drift issues for hosted models; AWS's replacement guidance uses open-source monitoring solutions and CloudWatch
Analyze bias and explainability SageMaker Clarify (no longer open to new customers) Helps assess bias and feature attribution in supported workflows
- Automate lifecycle SageMaker Pipelines Orchestrates repeatable ML workflows for technical teams
- Canvas, Studio, and audience fit
SageMaker Canvas is important for practitioner scenarios because the exam target includes people who use but do not necessarily build AI/ML solutions. Canvas can help a business analyst evaluate a tabular prediction problem, run what-if analysis, and share results under governance controls. It does not remove the need for data quality, permission review, metric interpretation, or monitoring. A no-code interface can still produce a poor model if the business target is unclear or the data is biased.
SageMaker Studio and related technical tools fit data scientists and ML engineers. They may prepare notebooks, launch training jobs, manage experiments, register models, and deploy endpoints. The practitioner does not need to know every button or parameter. The important exam-level distinction is that Studio supports custom ML work, while managed AI services and Bedrock reduce different kinds of model-building responsibility.
Deployment and monitoring map
SageMaker deployment patterns include real-time endpoints for low-latency predictions and batch transform for offline scoring. Real-time serving can be useful for fraud checks, recommendations, dynamic risk scores, or application features that need immediate predictions. Batch transform can fit monthly churn scoring, offline document classification, or overnight forecasting. The practitioner should ask about latency, volume, cost, scaling, and rollback before approving either pattern.
Model Monitor has helped detect changes in input data or model behavior for SageMaker-hosted models; it is no longer open to new customers, and AWS's replacement guidance combines open-source SageMaker AI monitoring solutions, Amazon Quick Sight dashboards, and CloudWatch. CloudWatch remains important for logs, metrics, and alarms around endpoints and applications. CloudTrail remains important for auditing API activity. These tools support operations, but they do not define business action. The owner must decide what happens when drift is detected, latency rises, or prediction quality drops.
SageMaker Clarify can help existing customers investigate bias and explainability; it is no longer open to new customers, and AWS's replacement path computes the same standardized bias metrics and SHAP values directly. For a practitioner, that means asking whether the model was evaluated for important groups and whether stakeholders can understand why predictions happen well enough for the use case. Explainability needs vary. A movie recommendation may not need the same explanation depth as a credit, healthcare, employment, or compliance workflow.
When SageMaker is too much or not enough
SageMaker can be the right service for custom ML, but it is not the default answer to every AI question. If the use case is standard translation, start with Translate. If the use case is invoice extraction, evaluate Textract. If the use case is a generative Q and A assistant over documents, evaluate Bedrock with Knowledge Bases and Guardrails. If deterministic rules satisfy the process, use rules.
SageMaker may also be not enough by itself. A production solution may need S3 data storage, Glue catalogs, Lake Formation access governance, IAM least privilege, KMS encryption, VPC networking, CloudWatch monitoring, CloudTrail audit, CI/CD tooling, application integration, and business review processes. SageMaker is part of the lifecycle, not a complete governance program.
Practitioner service-selection drill
Use this short drill when reading scenarios:
Is the task a common managed AI capability? Start with the relevant managed AWS AI service.
Is the task generative AI with prompts, foundation models, RAG, or agents? Evaluate Amazon Bedrock and related controls.
Is the user a business analyst needing no-code prediction from approved data? Consider SageMaker Canvas.
Does the team need custom training, model hosting, registry, monitoring, or pipelines? Consider SageMaker AI.
Is the decision deterministic, low value, or unsupported by data? Avoid ML or narrow the project.
This map keeps SageMaker in the right place. It is powerful when the business needs custom ML lifecycle control and has the skills to operate it. It is excessive when a managed service solves the job with less risk, and it is unsafe when the organization lacks data readiness or governance ownership.