Study guide

1.1 Credential Scope, Code, and Search Language

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

1.1 Credential Scope, Code, and Search Language

Key Takeaways Explain This Topic AI

AIF-C01 is the exam code for the AWS Certified AI Practitioner, a Foundational AWS Certification.

The credential is for people familiar with AI/ML solutions on AWS, including non-builder business and technical roles.

Use the exact credential name, exam code, and official AWS pages when searching or updating study materials.

Reject pass-rate claims, salary guarantees, exam dumps, and copied live-question language because they are not official AWS facts.

Last updated: October 2026

Source-controlled credential identity

Picture a product manager approving a customer-support chatbot, a marketing operations lead reviewing generated campaign copy, or an IT support analyst being asked whether a proposed AI tool should use Amazon Bedrock or a custom model path. AIF-C01 is built for that kind of working context. The AWS Certified AI Practitioner is a Foundational certification for people who are familiar with AI/ML solutions on AWS but do not necessarily build those solutions themselves.

That scope matters before you open any training tab. This is not an engineering-only exam, and it is not a generic AI vocabulary badge. It validates foundational AI concepts, AWS AI tools, and practical business applications of AI. A strong candidate can translate between business risk, model behavior, AWS service selection, cost awareness, and governance questions without pretending to be the data scientist, ML engineer, or security architect for every task.

Search phrase Why it matters Risk if you use loose language

AWS Certified AI Practitioner Official credential name used by AWS Certification. You may land on generic AI courses that do not cover AWS services.

AIF-C01 Official exam code for this guide. You may mix notes from another exam or an outdated series.

Foundational Official category. You may over-study builder tasks while missing practitioner judgment.

AWS Certification exam guide Source of exam scope, domains, scored items, and candidate boundaries. You may rely on vendor summaries that add unsupported claims.

AWS Skill Builder Official training and practice path. You may treat unofficial question banks as the source of record.

The search language habit

When you search, start with exact official wording: AWS Certified AI Practitioner AIF-C01 exam guide , AWS Certified AI Practitioner certification page , and AWS Skill Builder AI Practitioner Exam Prep Plan . Use those phrases to anchor your notes. If a page gives a pass-rate percentage, promises salary outcomes, claims to know live exam items, or offers exam dumps, do not use it as a factual source for this guide.

Source control is not just a publishing concern. It is a study skill. AI services change quickly, and certification pages can change logistics, language options, pricing caveats, or preparation resources. A candidate who writes down the source and date can compare later updates without blending old claims into current study material. This chapter follows the AWS certification page, the AWS exam guide, and AWS Certification policy pages.

Practitioner lens

The word practitioner is easy to underrate. A practitioner may not train a neural network, tune hyperparameters, or deploy a production ML pipeline, but they still need serious judgment. If a team proposes AI for invoice triage, the practitioner should ask whether the data is suitable, whether the task needs deterministic outcomes, whether human review is required, which AWS service category fits, and how the organization will monitor cost, privacy, fairness, and output quality.

That is the same level of seriousness expected in other professional exams. You do not memorize AWS service names as trivia. You learn what each service or concept means inside a business decision. For example, Amazon Bedrock belongs in conversations about foundation models, managed access to model choices, embeddings, knowledge bases, agents, and guardrails. Amazon SageMaker AI belongs in conversations about broader ML development and model workflows. IAM, pricing, and the shared responsibility model belong in almost every approval conversation.

Source-control checklist

Record the official source name and review date for every logistics claim.

Use AIF-C01 when naming files, notes, flashcards, and study plans.

Keep official exam facts separate from local practice-bank metadata.

Do not publish AWS pass-rate percentages unless AWS publishes them in an official source.

Do not state or imply that practice questions are live exam questions.

Remove salary, job, or certification-success guarantees.

Prefer official AWS wording for roles, domains, costs, durations, scores, and retake rules.

What belongs in Chapter 1

This chapter is not a substitute for the full AI/ML, generative AI, foundation model, responsible AI, and security domains. It is the control plane for the rest of the guide. Before studying model lifecycle or prompt engineering, you need the credential map: what the exam is, how it is delivered, what AWS says is in scope, what AWS says is out of scope, which domains carry the most weight, and how policies affect test-day and retake planning.

A good first decision is to stop collecting random notes. Build a source-led notebook with sections for official exam facts, domain weights, AWS service map, responsible AI terms, security and governance controls, practice errors, and official AWS training. Every time you add a claim, ask whether it came from AWS or from a secondary source. If it came from a secondary source, treat it as study commentary, not authority.

The payoff is cleaner thinking. When a scenario says a sales team wants a generative AI assistant, you will not panic-search broad AI advice. You will identify the AWS credential context, ask whether the task fits foundation model applications, check data and governance boundaries, and choose official preparation content that maps to the AIF-C01 guide.