Study guide
2.1 AI, ML, Deep Learning, and Core Terminology
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.1 AI, ML, Deep Learning, and Core Terminology
Key Takeaways Explain This Topic AI
Artificial intelligence is the broad business capability, while machine learning is one common way to create that capability from data.
Deep learning uses layered neural networks and is often behind modern computer vision, speech, NLP, and foundation model behavior.
Training creates or adapts a model; inference uses a model to produce predictions, classifications, scores, text, images, or recommendations.
Practitioner service selection starts with the task, risk, data type, and ownership model, not with a desire to use the newest AI service.
Last updated: October 2026
The Vocabulary Stack
Artificial intelligence is the broad idea of computer systems performing tasks that usually require human judgment, perception, language understanding, planning, or decision support. In a business conversation, AI might mean a chatbot, a document classifier, a fraud score, a recommendation list, or a visual inspection workflow. The term is useful, but it is too broad for choosing an AWS service or approving a project.
Machine learning is a narrower approach inside AI. Instead of coding every rule by hand, a model learns patterns from data and then applies those patterns to new inputs. A team might train a model on historical support tickets to classify future tickets, or use historical transactions to estimate fraud risk. The business question is whether the past data is reliable enough to guide future decisions.
Deep learning is a family of ML methods that uses neural networks with many layers. Deep learning is common in image recognition, speech processing, natural language processing, translation, and foundation models. A practitioner does not need to calculate model weights for this exam, but should understand that deep learning usually needs more data, compute, monitoring, and cost awareness than a simple rules engine.
Term Practitioner meaning AWS service-selection signal
Algorithm The method used to learn or produce an output Usually hidden in managed services; explicit in custom SageMaker AI work
Model The trained asset or foundation model used for inference Bedrock model, SageMaker model, or managed AI API behind a service
Training Creating or adapting a model from data More likely SageMaker AI or a customization workflow
Inference Using the model on new input Bedrock API, managed AI service, endpoint, batch job, or embedded app feature
Bias A systematic pattern that can unfairly affect outputs Requires data review, monitoring, and sometimes human review
LLM A large language model that handles language tasks Often selected through Amazon Bedrock or used inside Amazon Quick
The model is not the whole solution. A useful AI workflow also needs input data, identity and access controls, logging, cost controls, user experience, fallback handling, and a way to measure whether the output helps. For AWS, that may involve IAM, S3, CloudWatch, CloudTrail, KMS, and business analytics alongside AI services. A non-builder still needs to ask who owns each piece.
Managed AI services hide much of the ML complexity. Amazon Rekognition can analyze images and video, Amazon Textract can extract text and structure from documents, Amazon Transcribe can convert speech to text, Amazon Translate can translate text, Amazon Polly can synthesize speech, and Amazon Comprehend can extract language insights. These are strong choices when the task matches the service boundary and the business does not need to own model training.
Foundation model services are different. Amazon Bedrock provides access to foundation models for generative AI tasks such as summarization, drafting, question answering, embeddings, and agent workflows. Amazon Quick (for business users) and Amazon Q Developer (for builders) provide ready-made generative AI assistant experiences. These services are useful when language or multimodal reasoning is central, but they introduce hallucination, prompt injection, content safety, and data governance questions.
Custom ML is a better fit when the organization has a specific prediction problem, sufficient relevant data, a measurable objective, and a need for control over model behavior. Amazon SageMaker AI supports the builder path for training, deployment, and ML lifecycle work. Amazon SageMaker Canvas supports no-code or low-code business analysis patterns. The practitioner should know the difference without pretending every team must build models.
A practical approval checklist starts with the outcome. What decision will change if the output exists? What data proves the model can work? What harm happens if the output is wrong? What service gives the simplest reliable path? What human review is needed? What will be logged, monitored, and retired? These questions matter more than whether the solution sounds advanced.
Use a managed AI service when the task is common and well bounded, such as extracting text, translating language, or recognizing labels in images.
Use Amazon Bedrock or Amazon Quick when the core need is generative language, search assistance, summarization, or guided action over enterprise content.
Use SageMaker AI when the organization needs a custom model lifecycle and has the skill, data, budget, and governance to operate it.
Use rules, reports, or workflow automation when the outcome must be deterministic or the data is too weak for learning.
Scenario judgment: a compliance team wants every invoice over a fixed threshold to require approval. That is not an ML problem; the threshold is known and deterministic. A Lambda function, application rule, or workflow step is easier to explain, test, and audit. If the same team wants to identify unusual invoice patterns that humans have not explicitly defined, ML may be appropriate after data readiness and risk review.
Another scenario: a product manager asks for AI because competitors advertise AI features. The better first step is to define the user pain. If customers spend too long searching internal documentation, Amazon Quick or a Bedrock retrieval workflow might fit. If users need exact account balances, a deterministic database query is the right core. If support agents need suggested categories, classification may help but should be measured against human baseline performance.