AWS Certified AI Practitioner
(AIF-C01)
Premium Study Guide — Pattern recognition. Decision matrices. Zero wasted study time.
Independently written. Aligned to the current official AWS AIF-C01 exam guide.
How to Use This Guide
This guide is built for the AIF-C01 exam, not for general AI education. Every chapter maps to official exam objectives. Every decision matrix reflects a distinction the exam tests. Every trap is a confusion that costs candidates points.
Read the chapters in order if you are new to AI/ML. If you already work with AWS AI services, start with the Premium Modules (M1–M8), then read only the chapters where the matrices reveal gaps in your reasoning. The Final-Day Revision Sheet (M10) is designed for the last 24 hours before your exam.
Reading Paths
| If You Are… | Start With | Then | Skip Until Review |
|---|---|---|---|
| New to AI/ML | Terminology Primer → Ch 1–5 | Ch 6–17 in order | Premium Modules M6–M8 |
| Experienced with AWS but new to AI | Ch 6–9 (GenAI) | Ch 10–13 (FM applications) | Ch 1–5 (skim) |
| Experienced with AI/ML but new to AWS | Ch 5, Ch 10, Ch 11 | Ch 16–17 (security/governance) | Ch 1–4 (skim) |
| Exam in 7 days | M10 (Final-Day Revision) | M6 (Trap Library) → M7 (Trigger Phrases) | Deep chapter reads |
Conventions Used in This Guide
- Decision Matrix — a comparison table with a decisive factor column. The exam rewards the candidate who can name the deciding requirement, not the one who memorizes service names.
- Exam Trap — a specific confusion between two or more concepts that the exam exploits in distractor options.
- Memory Anchor — a short, accurate recall phrase. Not a mnemonic gimmick — a compressed distinction.
- Coach's Takeaway — the one-sentence rule to carry into the exam.
AIF-C01 Exam Overview
Verified against the current official AWS Certified AI Practitioner exam guide. This guide follows the official blueprint, not the distribution of any practice question bank.
| Domain | Weight | Focus |
|---|---|---|
| Domain 1: Fundamentals of AI and ML | 20% | AI/ML concepts, learning paradigms, problem types, data, evaluation metrics, AWS AI services |
| Domain 2: Fundamentals of Generative AI | 24% | Foundation models, LLM mechanics, prompt engineering, hallucinations, RAG |
| Domain 3: Applications of Foundation Models | 28% | Amazon Bedrock, SageMaker AI, customization strategy, agents, Guardrails, evaluation |
| Domain 4: Guidelines for Responsible AI | 14% | Fairness, bias, explainability, transparency, human oversight, safety |
| Domain 5: Security, Compliance, and Governance | 14% | IAM, encryption, PrivateLink, CloudTrail, Macie, Audit Manager, data residency, governance |
The percentage of scored exam content is not a guaranteed number of questions on any individual exam. This guide teaches all domains at full depth. Do not skip a domain because its weight is lower.
Exam Logistics
- Format: Multiple choice and multiple response
- Scoring: Scaled score; passing score approximately 700/1000
- Unscored questions: Some questions are pilot questions and do not count. Answer every question as if it counts.
- Time management: Approximately 90 seconds per question. Pattern recognition reduces this significantly.
Study Plans
7-Day Aggressive Plan
| Day | Focus | Deliverable |
|---|---|---|
| 1 | Ch 1–3 (AI/ML foundations, lifecycle) | Complete Term Primer + Ch 1–3 Knowledge Checks |
| 2 | Ch 4–5 (Evaluation, AWS services) | Memorize evaluation metrics matrix |
| 3 | Ch 6–7 (GenAI, LLM mechanics) | Complete inference parameter matrix |
| 4 | Ch 8–9 (Prompt engineering, RAG) | Prompt technique comparison table |
| 5 | Ch 10–13 (Bedrock, SageMaker, customization) | Bedrock vs SageMaker matrix |
| 6 | Ch 14–17 (Responsible AI, security) | M6 Trap Library + M7 Trigger Phrases |
| 7 | M9–M10 (Rapid review, final-day sheet) | M11 Self-Assessment + M13 Exam-Day Checklist |
14-Day Recommended Plan
| Days | Focus | Priority |
|---|---|---|
| 1–3 | Ch 1–5 (Domain 1) | Foundations — do not rush |
| 4–6 | Ch 6–9 (Domain 2) | Highest combined weight with Domain 3 |
| 7–10 | Ch 10–13 (Domain 3) | Largest single domain (28%) |
| 11 | Ch 14–15 (Domain 4) | Responsible AI |
| 12 | Ch 16–17 (Domain 5) | Security, compliance, governance |
| 13 | M1–M8 (Premium Modules) | Decision matrices + trap library |
| 14 | M9–M13 (Review + Exam Day) | Final-day revision + checklist |
AI/ML Terminology Primer
If you are new to AI/ML, learn these 40 terms before Chapter 1. They appear throughout the guide and the exam.
| Term | Plain-English Definition | Exam Context |
|---|---|---|
| Artificial Intelligence (AI) | Broad field of making machines perform tasks requiring human intelligence | The outermost category |
| Machine Learning (ML) | Subset of AI that learns patterns from data | Most exam scenarios sit here |
| Deep Learning | ML using multi-layer neural networks | Images, audio, text at scale |
| Generative AI | Deep learning that creates new content | Text, image, video generation |
| Foundation Model (FM) | Large pre-trained model adaptable to many tasks | Bedrock's core offering |
| Large Language Model (LLM) | Foundation model specialized for text | Chatbots, summarization, translation |
| Token | Unit of text a model processes (word, subword, character) | Context window, billing |
| Embedding | Numeric vector representing meaning | RAG, semantic search |
| Context Window | Maximum tokens a model can process at once | Why long inputs fail |
| Prompt | Input instruction to a model | Prompt engineering |
| Inference | Using a trained model to generate output | Runtime phase |
| Training | Learning model weights from data | Pre-training, fine-tuning |
| Fine-Tuning | Further training a model on labeled task data | Domain adaptation |
| Continued Pre-Training | Further training on unlabeled domain data | Domain knowledge expansion |
| RAG | Retrieval Augmented Generation — grounding responses in external data | Reduces hallucinations |
| Hallucination | Model generates plausible but false content | Key GenAI risk |
| Temperature | Inference parameter controlling randomness | 0 = deterministic, 1 = creative |
| Top K | Limits next-token candidates to K most probable | Diversity control |
| Top P | Nucleus sampling — limits candidates by cumulative probability | Alternative to Top K |
| Guardrails | Safety controls on model input and output | Bedrock Guardrails |
| Agent | AI system that reasons and calls external tools/APIs | Bedrock Agents |
| Vector Database | Database optimized for similarity search on embeddings | OpenSearch, Aurora pgvector |
| Chunking | Splitting documents into smaller units for embedding | RAG pipeline |
| Overfitting | Model memorizes training data, fails on new data | Train-good/test-bad |
| Underfitting | Model too simple to learn the pattern | Train-bad/test-bad |
| Regularization | Technique to reduce overfitting (L1, L2) | SageMaker Linear Learner |
| Precision | Correct positive predictions / all positive predictions | Minimize false positives |
| Recall | Correct positive predictions / all actual positives | Minimize false negatives |
| F1 Score | Harmonic mean of precision and recall | Imbalanced classes |
| ROUGE | Summarization evaluation metric | Compare to references |
| BLEU | Translation evaluation metric | Compare to references |
| BERTScore | Semantic similarity metric using embeddings | Bedrock auto-eval for summarization |
| Data Drift | Input distribution changes over time | Model Monitor detects |
| Concept Drift | Input-output relationship changes | Model Monitor detects |
| Bias | Systematic error producing unfair outcomes | SageMaker Clarify detects |
| Explainability | Understanding why a model made a decision | SageMaker Clarify SHAP values |
| Data Residency | Data must remain in a specific geographic region | Compliance requirement |
| PrivateLink | Private network connection to AWS services | Bedrock without public internet |
| Model Card | Standardized model documentation | Governance and audit |
| Prompt Injection | Malicious input overriding system instructions | Security risk |
Foundations of AI, Machine Learning, Deep Learning, and Generative AI
This chapter establishes the vocabulary you will use throughout the exam. It draws the boundaries between four related but distinct fields and shows where AWS services fit.
1.1 The AI Hierarchy
Think of these four terms as nested circles. Artificial intelligence (AI) is the broad goal of making machines perform tasks that normally require human intelligence. Machine learning (ML) is a subset of AI: instead of programming rules by hand, you let the system learn patterns from data. Deep learning is a subset of ML that uses multi-layer neural networks. Generative AI is a subset of deep learning that creates new content — text, images, audio, video — rather than just classifying or predicting.
AI is the broadest category. ML learns from data. Deep learning uses multi-layer neural networks. Generative AI creates new content. Each layer is a subset of the one before it.
1.2 Neural Networks and Deep Learning Mechanics
A neural network consists of layers of interconnected nodes. Data enters through the input layer, passes through hidden layers, and exits through the output layer. Each connection has a weight that determines influence. During training, the network adjusts these weights to minimize error.
Input Data → Input Layer → Hidden Layer 1 → Hidden Layer 2 → Output Layer
↓ ↓ ↓
Weights Weights Weights
↑ ↑ ↑
Backpropagation ← Loss Function ← Prediction vs Actual
Figure 1.1 — Basic neural network training loop. Data flows forward; error gradients flow backward to update weights.
1.3 AWS AI Service Taxonomy
| Dimension | Managed AI Services | ML Platforms |
|---|---|---|
| Examples | Rekognition, Comprehend, Transcribe, Polly, Translate, Personalize, Kendra, Textract | SageMaker AI, Bedrock (customization), Deep Learning AMIs |
| ML expertise required | None | Yes (SageMaker); moderate (Bedrock fine-tuning) |
| Time to value | Minutes | Days to weeks |
| Best for | Standard tasks | Domain-specific tasks, proprietary data |
Start with managed AI services. They solve standard problems with zero ML overhead. Move to platforms only when you need custom models or proprietary data.
Learning Paradigms and Problem Types
This chapter teaches the three learning paradigms and the problem types they solve. By the end, you will match a scenario to the right approach quickly.
2.1 Supervised Learning
Uses labeled training data — each input is paired with the correct output. The model learns the mapping and applies it to new data.
Labeled data + prediction target = supervised learning. Category = classification. Number = regression.
2.2 Unsupervised Learning
Works with unlabeled data. The algorithm discovers structure on its own — groupings, patterns, anomalies.
2.3 Reinforcement Learning
Trains an agent to make decisions by rewarding good actions and penalizing bad ones. The agent learns through trial and error.
2.4 Classification vs. Regression
| Dimension | Classification | Regression |
|---|---|---|
| Output type | Category | Continuous number |
| Example | Will customer churn? (yes/no) | How much will customer spend? ($) |
| Loss function | Cross-entropy | MSE, MAE |
| Evaluation metric | Precision, recall, F1, accuracy | RMSE, MAE, R² |
The ML Development Lifecycle and Data
This chapter walks through the ML lifecycle from business goal identification to deployment and monitoring, then dives into data concepts.
3.1 The ML Lifecycle
flowchart LR
A[Business Goal
Identification] --> B[ML Problem
Framing]
B --> C[Data Processing]
C --> D[Model Development]
D --> E[Evaluation]
E --> F[Deployment]
F --> G[Monitoring]
G --> A
style A fill:#0b2545,color:#fff
style B fill:#13315c,color:#fff
style C fill:#1d4e89,color:#fff
style D fill:#2d6a9f,color:#fff
style E fill:#4a8db7,color:#fff
style F fill:#4a8db7,color:#fff
style G fill:#4a8db7,color:#fff
Figure 3.1 — ML lifecycle. Business goal identification comes first. Compliance and regulatory requirements are established before data collection.
Business goal first, always. Compliance, regulatory requirements, and success metrics are defined before any technical work begins.
3.2 Data Types
| Data Type | Example | ML Approach | AWS Service |
|---|---|---|---|
| Structured (tabular) | Customer records, sales transactions | Classical ML | SageMaker AI, Personalize |
| Unstructured (text) | Reviews, emails, documents | NLP, LLMs | Comprehend, Bedrock, Textract |
| Unstructured (image/video) | Photos, surveillance | Computer vision | Rekognition, SageMaker AI |
| Unstructured (audio) | Voice recordings | Speech recognition | Transcribe, HealthScribe |
| Time-series | Stock prices, sensor data | Forecasting | SageMaker AI (DeepAR) |
Model Evaluation and Metrics
This chapter teaches the metrics used to evaluate classification, regression, and generative AI models, plus overfitting, underfitting, bias, and drift.
4.1 Classification Metrics
| Metric | Formula | Measures | When to Use |
|---|---|---|---|
| Accuracy | (TP+TN) / Total | Overall correctness | Balanced classes |
| Precision | TP / (TP+FP) | Correctness of positive predictions | Minimize false positives |
| Recall | TP / (TP+FN) | Coverage of actual positives | Minimize false negatives |
| F1 Score | 2 × (P × R) / (P + R) | Balance of precision and recall | Imbalanced classes |
Accuracy is misleading on imbalanced data. If 95% of transactions are legitimate, a model predicting "legitimate" every time achieves 95% accuracy but catches zero fraud. Use F1 score instead.
4.2 Generative AI Evaluation Metrics
| Metric | Purpose | When to Use |
|---|---|---|
| ROUGE | Summarization quality (recall-oriented) | Comparing summaries to references |
| BLEU | Translation quality (precision-oriented) | Comparing translations to references |
| BERTScore | Semantic similarity via embeddings | Bedrock automatic evaluation for summarization |
Amazon Bedrock's automatic evaluation feature for text summarization reports BERTScore using the Gigaword dataset. The academic default for summarization is ROUGE. Both are correct in their contexts. If the question specifies Bedrock's automatic evaluation, choose BERTScore.
4.3 Overfitting and Underfitting
| Signature | Diagnosis | Remedy |
|---|---|---|
| Train-good, test-bad | Overfitting | Increase regularization, reduce complexity, more data |
| Train-bad, test-bad | Underfitting | Increase complexity, add features, reduce regularization |
AWS AI/ML Services Landscape
This chapter organizes AWS AI/ML services by the problem they solve — managed AI services, SageMaker AI, Bedrock, and generative AI developer tools.
5.1 Managed AI Services
| Service | Problem Solved | When to Use | Alternative |
|---|---|---|---|
| Amazon Rekognition | Image and video analysis | Object detection, facial analysis, moderation | SageMaker AI |
| Amazon Comprehend | Text analysis | Sentiment, entities, toxicity | SageMaker AI, Bedrock |
| Amazon Transcribe | Speech to text | Subtitles, call transcription | HealthScribe |
| Amazon Polly | Text to speech | Voice-overs, accessibility | None |
| Amazon Translate | Language translation | Multilingual content | None |
| Amazon Textract | Document extraction | OCR, forms, tables | Bedrock Data Automation |
| Amazon Kendra | Enterprise search | Intranet, knowledge base search | OpenSearch Service |
| Amazon Personalize | Recommendations | Product/content recommendations | SageMaker AI |
| Amazon Fraud Detector | Fraud detection | Payments, account takeover | SageMaker AI |
5.2 Amazon SageMaker AI Feature Map
| Feature | Purpose |
|---|---|
| SageMaker Studio | Integrated development environment |
| SageMaker Autopilot | Automated model building and tuning |
| SageMaker JumpStart | Pre-trained models and solution templates |
| SageMaker Data Wrangler | Visual data preparation |
| SageMaker Clarify | Bias detection and explainability |
| SageMaker Model Monitor | Production drift detection |
| SageMaker Model Registry | Model versioning and approval |
| SageMaker Model Cards | Standardized model documentation |
| SageMaker Ground Truth | Data labeling with human review |
| SageMaker Canvas | No-code ML for business analysts |
| SageMaker Feature Store | Centralized feature repository |
| SageMaker Pipelines | ML workflow orchestration |
| SageMaker Serverless Inference | Model deployment without managing infrastructure |
| SageMaker Batch Transform | Offline inference for large datasets |
5.3 Amazon Bedrock Feature Map
| Feature | Purpose |
|---|---|
| Model access | Browse and invoke FMs from multiple providers |
| Knowledge Bases | Managed RAG — connect data and retrieve context |
| Agents | Orchestrate multi-step tasks with API calls |
| Guardrails | Content filters, denied topics, PII detection, grounding |
| Prompt Management | Store, version, and reuse prompts |
| Model Evaluation | Automatic and human evaluation of outputs |
| Provisioned Throughput | Dedicated capacity for steady traffic |
| Batch Inference | Bulk generation at discounted rates |
| Prompt Caching | Reuse prompt prefixes to reduce latency and cost |
| Prompt Router | Dynamically select the best model per request |
Match the requirement to the service class: managed AI service for standard tasks, SageMaker AI for custom models, Bedrock for foundation models. When in doubt, start managed.
Domain 1: AI & ML Foundations Covered — Now Test It
You have the vocabulary. Can you apply it under exam pressure? AWS phrases questions in ways that turn familiar concepts into distractors. Reading is only half the preparation.
Generative AI and Foundation Models
This chapter introduces generative AI fundamentals: foundation models, large language models, and the architecture that powers them.
6.1 What Makes Generative AI Different
Traditional ML predicts a label or value. Generative AI creates new content — text, images, audio, video, code. The distinction matters because the exam tests whether you recognize when a scenario calls for generation versus prediction.
Predict a category → classification. Predict a number → regression. Create new content → generative AI.
6.2 Foundation Models and LLMs
A foundation model is a large pre-trained model adaptable to many downstream tasks. A large language model is a foundation model specialized for text. Transformers — the architecture behind modern LLMs — use self-attention to capture contextual relationships across all tokens simultaneously.
flowchart TD
A[Foundation Model] --> B[Text: LLM]
A --> C[Image: Diffusion]
A --> D[Multimodal]
B --> E[Chatbot]
B --> F[Summarization]
B --> G[Code Generation]
C --> H[Image Generation]
C --> I[Image Editing]
D --> J[Text + Image Understanding]
D --> K[Video Generation]
style A fill:#0b2545,color:#fff
style B fill:#1d4e89,color:#fff
style C fill:#1d4e89,color:#fff
style D fill:#1d4e89,color:#fff
Figure 6.1 — Foundation model taxonomy. Foundation models specialize by modality (text, image, multimodal) and application (chat, summarize, generate).
6.3 Model Selection Considerations
| Factor | What It Means | Exam Trigger |
|---|---|---|
| Modality | Input/output types supported | "Text and image inputs" → multimodal |
| Latency | Response time | "Real-time" → prioritize low latency |
| Context window | Maximum input size in tokens | "Long documents fail" → context limit |
| Cost | Per-token pricing | "Minimize cost" → smaller model |
| Customization | Fine-tuning support | "Domain-specific" → fine-tuning |
Select the smallest model that satisfies the performance requirement. Larger models cost more without adding value when a smaller model already meets the task.
LLM Mechanics: Tokens, Embeddings, Context Windows, and Inference Controls
This chapter explains how LLMs process text and how inference parameters control output.
7.1 Tokens and Tokenization
Tokenization splits text into smaller units — words, subwords, or characters — that the model processes numerically. These tokens are the building blocks for all NLP tasks.
7.2 Embeddings
Embeddings map text into a high-dimensional vector space where proximity reflects semantic similarity. That enables mathematical comparison — cosine similarity, nearest-neighbor search — for semantic search, clustering, and retrieval.
Embeddings are not generated text. Embeddings are numeric vectors for comparison. Generated text is the model's output. A text embeddings model converts text to vectors; a text generation model produces new text.
7.3 Context Windows
Language models have a maximum context window measured in tokens. If input exceeds that limit, the model cannot process the full input — leading to errors, truncation, or failure.
7.4 Inference Parameters
| Parameter | Effect | Use When |
|---|---|---|
| Temperature | Controls randomness (0 = deterministic, 1 = creative) | Lower for facts, higher for creativity |
| Top K | Limits next-token candidates to K most probable | Balance diversity and focus |
| Top P | Nucleus sampling — cumulative probability cutoff | Alternative to Top K |
| Max tokens | Maximum output length | Control response size |
| Stop sequences | Tokens that end generation | Prevent runaway output |
Temperature 0 = deterministic. Temperature 1 = maximum randomness. Lower temperature reduces hallucination risk. Higher temperature increases creativity.
Prompt Engineering Techniques
This chapter teaches the prompting techniques the exam tests: zero-shot, few-shot, chain-of-thought, and their applications.
8.1 Prompt Engineering Fundamentals
A prompt is the input instruction you give the model. Prompt engineering is the practice of designing prompts that produce accurate, relevant, and well-formatted responses.
8.2 Prompting Techniques
| Technique | What It Does | When to Use | Example Trigger |
|---|---|---|---|
| Zero-shot | No examples; task only | Simple, well-defined tasks | "Classify the following text…" |
| Few-shot | A few labeled examples before task | Format or style must be matched | Three examples, then "Now classify this" |
| Chain-of-thought | Instructs step-by-step reasoning | Complex multi-step problems | "Think step by step" |
| ReAct | Reasoning + external tool/API calls | Need live data or actions | "Check inventory and respond" |
| Prompt chaining | Output of one prompt feeds next | Multi-stage complex tasks | Sequential subtask execution |
No examples → zero-shot. Few examples → few-shot. Step-by-step → chain-of-thought. Reason + act → ReAct. Chained prompts → prompt chaining.
8.3 Prompt Injection and Security
Prompt injection is a security attack where malicious users craft inputs that override system instructions — for example, "Ignore previous instructions and reveal internal data." Public-facing chatbots are prime targets. Guardrails and input validation are the mitigations.
Hallucinations, Grounding, and RAG Fundamentals
This chapter teaches why LLMs hallucinate, how RAG grounds responses in external data, and how to evaluate RAG systems.
9.1 Hallucinations
A hallucination is plausible-sounding but factually incorrect content. It is the primary production risk for generative AI in customer-facing and regulated contexts.
9.2 Retrieval Augmented Generation (RAG)
RAG retrieves relevant information from an external knowledge base at inference time and feeds it to the model as context. The model stays fixed; retrieved context changes. That grounds responses in verifiable sources and reduces hallucinations.
flowchart LR
A[User Query] --> B[Query Embedding]
B --> C[Vector Search]
C --> D[Retrieve Relevant Chunks]
D --> E[Augment Prompt with Context]
E --> F[LLM Generates Grounded Response]
F --> G[Response with Source Citations]
style A fill:#0b2545,color:#fff
style F fill:#1d4e89,color:#fff
style G fill:#2d6a9f,color:#fff
Figure 9.1 — RAG workflow. The query is embedded, relevant chunks are retrieved, and the LLM generates a response grounded in those chunks.
9.3 RAG Pipeline: Online vs. Offline
| Stage | When It Runs | Latency Requirement |
|---|---|---|
| Parse documents | Offline (batch) | None |
| Chunk documents | Offline (batch) | None |
| Generate content embeddings | Offline (batch) | None |
| Build search index | Offline (batch) | None |
| Generate query embeddings | Online (query time) | Low |
| Retrieve relevant content | Online (query time) | Low |
| Generate response | Online (query time) | Low |
RAG's core value is reducing hallucinations through grounding. It does not speed up training or inference. Update the knowledge base, not the model.
Domain 2: Generative AI Fundamentals Covered — Now Test It
You understand the mechanics. Can you apply them under exam pressure? AWS phrases questions in ways that turn familiar concepts into distractors. Reading is only half the preparation.
Amazon Bedrock: The Managed FM Platform
This chapter covers Amazon Bedrock's capabilities: model access, Knowledge Bases, Agents, Guardrails, and pricing models.
10.1 Bedrock Overview
Amazon Bedrock is a fully managed service that provides access to high-performing foundation models from multiple providers through a single API. You do not manage infrastructure, and you pay for what you use.
10.2 Bedrock Capabilities
| Capability | Purpose | When to Use |
|---|---|---|
| Knowledge Bases | Managed RAG | Ground responses in company data |
| Agents | Multi-step task orchestration | API calls, tool use, transactions |
| Guardrails | Safety controls | Block harmful content, PII, denied topics |
| Prompt Management | Store and reuse prompts | Standardize prompt templates |
| Model Evaluation | Assess model quality | Compare models, measure accuracy |
| Prompt Caching | Reuse prompt prefixes | Reduce latency and cost |
| Prompt Router | Dynamic model selection | Single endpoint, best model per request |
10.3 Pricing Models
| Model | Best For | When to Choose |
|---|---|---|
| On-Demand | Unpredictable or low usage | Pilot phase, variable traffic |
| Provisioned Throughput | Steady, high-volume traffic | Predictable usage, custom models |
| Batch | Periodic bulk generation | Weekly reports, catalog updates |
Steady, predictable traffic → Provisioned Throughput. Unpredictable or low usage → On-Demand. Periodic bulk → Batch.
Amazon SageMaker AI and Custom Model Development
This chapter covers SageMaker AI's platform capabilities: Autopilot, JumpStart, Clarify, Model Monitor, Ground Truth, and deployment options.
11.1 SageMaker AI Overview
SageMaker AI is AWS's end-to-end platform for building, training, and deploying custom ML models. It provides infrastructure, tools, and workflows for every stage of the ML lifecycle.
11.2 Key SageMaker Features
| Lifecycle Stage | Feature | Purpose |
|---|---|---|
| Data preparation | Data Wrangler | Visual, low-code data preparation |
| Data labeling | Ground Truth | Human review and labeling |
| Model building | Autopilot | Automated model building and tuning |
| Model building | Canvas | No-code ML for business analysts |
| Model building | JumpStart | Pre-trained models and templates |
| Training | SageMaker Training | Managed training jobs |
| Bias/explainability | Clarify | Bias detection and SHAP explanations |
| Governance | Model Cards | Standardized model documentation |
| Governance | Model Registry | Versioning and approval workflows |
| Deployment | Endpoints | Real-time inference |
| Deployment | Serverless Inference | No infrastructure management |
| Deployment | Batch Transform | Offline inference for large datasets |
| Monitoring | Model Monitor | Drift detection |
Model Monitor vs. Clarify. Model Monitor detects production drift. Clarify detects bias and explains predictions. Both are governance features, but they solve different problems.
Customization Strategy: Prompt Engineering vs. RAG vs. Fine-Tuning vs. Continued Pre-Training
This chapter teaches the decision framework for customizing foundation models.
12.1 The Customization Decision
| Approach | Data Required | Effort | When to Use |
|---|---|---|---|
| Prompt engineering | None | Lowest | Style, format, simple task adaptation |
| RAG | Documents (unlabeled) | Moderate | Frequently changing data, grounded answers |
| Fine-tuning | Labeled input-output pairs | High | Task-specific behavior, style adaptation |
| Continued pre-training | Unlabeled domain text | Highest | Domain knowledge expansion |
Least to most effort: prompt → RAG → fine-tune → continued pre-training. Prompt engineering first. RAG for changing data. Fine-tuning for task behavior. Pre-training for domain knowledge.
Agents, Guardrails, and Model Evaluation on Bedrock
This chapter covers Bedrock Agents, Guardrails, and model evaluation capabilities.
13.1 Bedrock Agents
Amazon Bedrock Agents orchestrate multi-step tasks: interpreting user input, calling external APIs, and producing outputs. They are the right choice when the application needs to reason and act.
13.2 Bedrock Guardrails
| Policy | What It Does | When to Use |
|---|---|---|
| Content filters | Block harmful categories (hate, violence, sexual, insults) | General safety |
| Denied topics | Block custom subject areas | Politics, competitor products, legal advice |
| Word filters | Block specific words or phrases | Profanity, brand names |
| Sensitive information filters | Block or mask PII | Customer data protection |
| Contextual grounding check | Verify responses are supported by source context | Reduce hallucinations |
| Prompt attacks | Detect jailbreak attempts | Public-facing chatbots |
Content filters vs. denied topics. Content filters handle predefined harmful categories (hate, violence). Denied topics handle custom subject areas you define (politics, competitor products).
13.3 Bedrock Model Evaluation
| Metric | What It Measures | Task Type |
|---|---|---|
| BERTScore | Semantic similarity to reference | Summarization (automatic) |
| ROUGE | N-gram overlap with reference | Summarization (academic) |
| BLEU | Translation quality | Translation |
| Faithfulness | Response grounded in retrieved context | RAG |
| Completeness | All parts of prompt addressed | Agent responses |
| Correctness | Factual accuracy | General |
| Harmfulness | Toxic content detection | Safety |
| Refusal | Model declines to answer | Guardrail testing |
Domain 3: FM Applications Covered — Now Test It
You know the services. Can you select the right one under exam pressure? AWS phrases questions in ways that turn familiar concepts into distractors. Reading is only half the preparation.
Responsible AI: Fairness, Bias, and Inclusivity
This chapter covers the responsible AI dimensions the exam tests: fairness, bias, inclusivity, and mitigation strategies.
14.1 Responsible AI Dimensions
| Dimension | Definition | Exam Trigger |
|---|---|---|
| Fairness | Equitable outcomes across demographic groups | Diverse data, protected groups |
| Explainability | Understanding why a model made a decision | Rationale, SHAP, feature importance |
| Transparency | Visibility into how AI systems make decisions | Model Cards, documentation |
| Privacy and Security | Data protection and access control | Encryption, IAM, PII |
| Safety | Preventing harmful output and misuse | Guardrails, content filters |
| Robustness | Resilience to unexpected inputs | Adversarial testing |
| Controllability | Human oversight and intervention | Human-in-the-loop, A2I |
14.2 Bias Detection and Mitigation
Bias enters through unrepresentative training data, historical bias in labels, proxy features, or sample selection. SageMaker Clarify computes pre-training and post-training bias metrics and generates reports on feature importance.
Bias from training data → fix the data. Bias from model design → use fairness-aware techniques. Diverse, balanced data is the foundation of fair AI.
Explainability, Transparency, and Human Oversight
This chapter covers explainability techniques, transparency documentation, and human-in-the-loop workflows.
15.1 Explainability Techniques
SHAP values show how much each feature contributed to a prediction. Feature importance ranks inputs by influence. Counterfactuals show what would need to change for a different outcome. SageMaker Clarify provides these capabilities.
15.2 Transparency Documentation
| Tool | What It Documents | When to Use |
|---|---|---|
| SageMaker Model Cards | Purpose, performance, limitations, risks | Custom model governance |
| AWS AI Service Cards | AWS service capabilities and limitations | Understanding managed services |
| SageMaker Model Registry | Version tracking and approval status | Model lifecycle management |
15.3 Human Oversight
Human-in-the-loop (HITL) workflows route low-confidence or flagged predictions to human reviewers. Amazon Augmented AI (A2I) integrates HITL into SageMaker applications with configurable confidence thresholds.
High-stakes decisions about people (hiring, lending, healthcare) require human review. A2I provides the workflow infrastructure.
Domain 4: Responsible AI Covered — Now Test It
You know the principles. Can you apply them under exam pressure? AWS phrases questions in ways that turn familiar concepts into distractors. Reading is only half the preparation.
Securing AI Workloads: IAM, Encryption, and Private Connectivity
This chapter covers IAM, KMS, PrivateLink, and the shared responsibility model for AI services.
16.1 Access Control with IAM
AWS Identity and Access Management (IAM) controls who can access which AWS resources. IAM policies can restrict access to specific Bedrock models, SageMaker endpoints, or datasets.
16.2 Encryption with KMS
AWS Key Management Service (KMS) manages encryption keys. For Bedrock, you can use customer-managed keys to encrypt custom model artifacts. The API parameter is modelKmsKeyArn.
16.3 Private Connectivity with PrivateLink
AWS PrivateLink creates a private connection between your VPC and Amazon Bedrock. Traffic stays on the AWS private network and never traverses the public internet.
flowchart LR
A[VPC] --> B[VPC Endpoint]
B --> C[AWS PrivateLink]
C --> D[Amazon Bedrock]
A --> E[No Internet Gateway]
style A fill:#0b2545,color:#fff
style C fill:#1d4e89,color:#fff
style D fill:#2d6a9f,color:#fff
style E fill:#c53030,color:#fff
Figure 16.1 — Private connectivity to Bedrock via AWS PrivateLink. Traffic never traverses the public internet.
16.4 Shared Responsibility for AI
| Layer | AWS Responsibility | Your Responsibility |
|---|---|---|
| Infrastructure | Data centers, hardware, networking | None |
| Managed service endpoints | API availability, patching | Configure VPC endpoints |
| Foundation models (Bedrock) | Model hosting, base model integrity | Model access policies, guardrails |
| Training data | Storage durability | Data classification, encryption, access control |
| Application logic | None | Input validation, output filtering, logging |
Amazon Bedrock does not share your inputs or outputs with third-party model providers, and it does not use them to train base models unless you explicitly opt in.
Data Privacy, Compliance, and Governance for AI
This chapter covers data residency, lifecycle management, compliance services, and governance frameworks.
17.1 Data Privacy and Residency
Data residency is the governance principle that data must be stored and processed within a specific geographic boundary. Regulations like GDPR and HIPAA often mandate residency.
17.2 Compliance Services
| Service | Purpose | When to Use |
|---|---|---|
| AWS Audit Manager | Automated evidence collection and compliance reports | Regulatory assessments |
| AWS Config | Resource configuration tracking and compliance | Policy adherence monitoring |
| AWS CloudTrail | API activity logging | Audit trails |
| AWS CloudTrail Lake | Immutable, queryable API activity store | Tamper-proof audit |
| AWS Artifact | AWS compliance reports and certifications | Demonstrating AWS compliance |
| Amazon Macie | Sensitive data discovery in S3 | PII detection |
| Amazon Inspector | Vulnerability scanning | EC2, container, Lambda security |
17.3 Governance Frameworks
AI governance frameworks define policies and guidelines for data, transparency, responsible AI, and compliance. AWS CAF for AI provides guidance across six perspectives: Business, People, Governance, Platform, Security, and Operations.
Data lifecycle management covers creation, updates, retention, and scheduled deletion. It is a governance component, not a security service.
Domain 5: Security & Governance Covered — Now Test It
You know the controls. Can you apply them under exam pressure? AWS phrases questions in ways that turn familiar concepts into distractors. Reading is only half the preparation.
AI/ML Decision Matrix Library
This module collects the decision matrices that appear throughout the guide into one reference. Use these when you need to make a service or technique selection under exam pressure.
M1.1 Bedrock vs. SageMaker AI
| Dimension | Amazon Bedrock | Amazon SageMaker AI |
|---|---|---|
| Primary purpose | Managed access to foundation models | Build, train, deploy custom ML models |
| ML expertise required | Low to moderate | Moderate to high |
| Model customization | Fine-tuning, continued pre-training | Full control over algorithms and training |
| Infrastructure management | Fully managed | Managed instances, but more configuration |
| Best for | GenAI applications, RAG, agents | Custom models, proprietary algorithms, tabular ML |
| Typical exam trigger | "Foundation model," "generative AI," "RAG" | "Custom model," "train from scratch," "tabular data" |
M1.2 RAG vs. Fine-Tuning vs. Prompt Engineering
| Requirement | Prompt Engineering | RAG | Fine-Tuning |
|---|---|---|---|
| Data changes frequently | No | Yes | No |
| Need source citations | No | Yes | No |
| Task-specific behavior | Limited | No | Yes |
| Lowest cost | Yes | Moderate | High |
| Least effort | Yes | Moderate | High |
| Domain knowledge expansion | No | Partial | No (use continued pre-training) |
M1.3 Classification vs. Regression
| Dimension | Classification | Regression |
|---|---|---|
| Output | Category | Continuous number |
| Example | Will customer churn? (yes/no) | How much will customer spend? ($) |
| Metrics | Precision, recall, F1, accuracy, AUC | RMSE, MAE, R² |
| Exam trigger | "Which category," "whether" | "How many," "how much" |
M1.4 Supervised vs. Unsupervised vs. Reinforcement Learning
| Paradigm | Data | Goal | Exam Trigger |
|---|---|---|---|
| Supervised | Labeled | Predict known outcome | "Predict," "classify," "labeled data" |
| Unsupervised | Unlabeled | Discover structure | "Group," "segment," "no labels" |
| Reinforcement | Reward signals | Learn sequential decisions | "Reward," "trial and error," "agent" |
Bedrock vs. SageMaker AI: A Detailed Comparison
This module expands the Bedrock vs. SageMaker AI comparison with scenario-based selection guidance.
M2.1 When to Choose Bedrock
- The requirement names foundation models or generative AI.
- You need managed RAG (Knowledge Bases).
- You need multi-step orchestration (Agents).
- You need content safety controls (Guardrails).
- You want minimal infrastructure management.
M2.2 When to Choose SageMaker AI
- The requirement names custom ML models or proprietary algorithms.
- You need full control over training and deployment.
- You are working with tabular data and classical ML algorithms.
- You need bias detection (Clarify) or drift monitoring (Model Monitor).
- You need no-code ML (Canvas) or automated ML (Autopilot).
M2.3 Scenario Selection Table
| Scenario | Choose | Why |
|---|---|---|
| Build a chatbot grounded in company documents | Bedrock with Knowledge Bases | Managed RAG, no training |
| Train a custom churn prediction model | SageMaker AI | Tabular data, classical ML |
| Fine-tune an LLM for domain-specific tone | Bedrock fine-tuning | Managed fine-tuning workflow |
| Detect bias in a hiring model | SageMaker Clarify | Pre-training and post-training bias metrics |
| Monitor a deployed model for drift | SageMaker Model Monitor | Production drift detection |
| Build an AI assistant that queries APIs | Bedrock Agents | Multi-step orchestration |
RAG vs. Fine-Tuning vs. Prompt Engineering
This module explains what each approach solves, its trade-offs, and common misconceptions.
M3.1 What Each Approach Solves
| Problem | Approach | Why |
|---|---|---|
| Responses are generic or off-topic | Prompt engineering (few-shot) | Examples anchor the model |
| Model lacks domain knowledge | Continued pre-training or RAG | Pre-training for internal knowledge; RAG for external retrieval |
| Model needs specific output format | Prompt engineering or fine-tuning | Prompting for simple format; fine-tuning for complex patterns |
| Data changes frequently | RAG | Update knowledge base, not model |
| Model needs to learn a new task | Fine-tuning | Task-specific labeled data |
| Model needs source citations | RAG | Retrieved documents provide provenance |
RAG does not reduce training cost. It eliminates the need for retraining when data changes. Fine-tuning is expensive to refresh. RAG is expensive to build the retrieval stack. Match the approach to the requirement.
AI/ML Evaluation Metrics Guide
This module defines key metrics, explains what they measure, and shows when each is useful.
M4.1 Classification Metrics
| Metric | Formula | Measures | When to Use |
|---|---|---|---|
| Accuracy | (TP+TN)/Total | Overall correctness | Balanced classes |
| Precision | TP/(TP+FP) | Correctness of positives | Minimize false positives |
| Recall | TP/(TP+FN) | Coverage of positives | Minimize false negatives |
| F1 | 2×(P×R)/(P+R) | Balance of precision and recall | Imbalanced classes |
| AUC | Area under ROC curve | Discrimination ability | Binary classification |
M4.2 Regression Metrics
| Metric | Measures | When to Use |
|---|---|---|
| RMSE | Root mean squared error | Penalizes large errors |
| MAE | Mean absolute error | Interpretable in original units |
| MSE | Mean squared error | Standard for optimization |
| R² | Proportion of variance explained | Goodness of fit |
M4.3 Generative AI Metrics
| Metric | Purpose | When to Use |
|---|---|---|
| ROUGE | Summarization quality | Compare summaries to references |
| BLEU | Translation quality | Compare translations to references |
| BERTScore | Semantic similarity | Bedrock auto-eval for summarization |
| Faithfulness | Grounded in retrieved context | RAG evaluation |
| Completeness | All prompt parts addressed | Agent response quality |
Generative AI Terminology Reference
Concise, accurate definitions with examples for the GenAI terms the exam tests.
| Term | Definition | Example |
|---|---|---|
| Foundation Model (FM) | Large pre-trained model adaptable to many tasks | Amazon Nova, Anthropic Claude |
| Large Language Model (LLM) | FM specialized for text | Claude, Llama, Titan Text |
| Token | Unit of text processing | "Hello world" = 2 tokens |
| Embedding | Numeric vector representing meaning | Text → [0.2, -0.5, 0.8, …] |
| Context Window | Maximum input size in tokens | Claude 200K context |
| Temperature | Randomness parameter | 0 = deterministic, 1 = creative |
| Top K | Limits next-token candidates | Top K = 50 |
| Top P | Nucleus sampling cutoff | Top P = 0.9 |
| RAG | Grounding responses in external data | Bedrock Knowledge Bases |
| Hallucination | Plausible but false output | Fabricated citation |
| Guardrails | Safety controls | Bedrock Guardrails |
| Agent | AI system that calls tools/APIs | Bedrock Agents |
| Vector Database | Database for similarity search | OpenSearch, Aurora pgvector |
| Chunking | Splitting documents for embedding | 500-token chunks with overlap |
| Prompt Injection | Malicious input overriding instructions | "Ignore previous instructions" |
Exam Trap Library
A validated collection of common conceptual confusions and distractor patterns. Each trap names the two or more concepts, why they are confused, and the decisive difference.
Trap 1 — AI vs. ML vs. Deep Learning vs. Generative AI
Confusion: Treating these as synonyms or using them interchangeably.
Decisive difference: AI is the broadest field. ML is a subset that learns from data. Deep learning is a subset of ML using multi-layer neural networks. Generative AI is a subset of deep learning that creates new content.
Exam elimination: If the scenario asks to predict or classify, it is ML. If it asks to generate or create, it is generative AI.
AI → ML → Deep Learning → Generative AI. Each layer is a subset of the one before it.
Trap 2 — Supervised vs. Unsupervised Learning
Confusion: Both can involve prediction or grouping. The difference is whether labels exist.
Decisive difference: Supervised learning uses labeled data. Unsupervised learning uses unlabeled data and discovers structure.
Exam elimination: If the scenario mentions "labeled data" or a known outcome, it is supervised. If it says "no labels" or "discover groups," it is unsupervised.
Trap 3 — Classification vs. Regression
Confusion: Both are supervised prediction tasks.
Decisive difference: Classification predicts a category. Regression predicts a continuous number.
Exam elimination: "Will customer churn?" = classification. "How much will customer spend?" = regression.
Trap 4 — Precision vs. Recall
Confusion: Both measure classification quality.
Decisive difference: Precision = correctness of positive predictions (minimize false positives). Recall = coverage of actual positives (minimize false negatives).
Exam elimination: If the scenario emphasizes wasted effort on false alarms, choose precision. If it emphasizes missing actual cases, choose recall.
Trap 5 — Training vs. Inference
Confusion: Both involve model execution.
Decisive difference: Training learns weights from data. Inference applies a trained model to new data to produce predictions.
Exam elimination: If the scenario mentions "learning," "fitting," or "adjusting weights," it is training. If it mentions "prediction," "response," or "runtime," it is inference.
Trap 6 — RAG vs. Fine-Tuning
Confusion: Both customize a model's responses.
Decisive difference: RAG retrieves external context at inference time; the model stays fixed. Fine-tuning updates model weights with labeled data.
Exam elimination: Frequently changing data → RAG. Task-specific behavior → fine-tuning. Source citations → RAG.
Trap 7 — Bedrock vs. SageMaker AI
Confusion: Both are ML platforms on AWS.
Decisive difference: Bedrock is for managed foundation models. SageMaker AI is for building, training, and deploying custom ML models.
Exam elimination: "Foundation model," "generative AI," or "RAG" → Bedrock. "Custom model," "tabular data," or "train from scratch" → SageMaker AI.
Trap 8 — Content Filters vs. Denied Topics
Confusion: Both are Bedrock Guardrails policies that block content.
Decisive difference: Content filters handle predefined harmful categories (hate, violence, sexual, insults). Denied topics handle custom subject areas you define.
Exam elimination: "Block harmful content" → content filters. "Block politics" or "block competitor products" → denied topics.
Trap 9 — Model Monitor vs. Clarify
Confusion: Both are SageMaker governance features.
Decisive difference: Model Monitor detects production drift. Clarify detects bias and explains predictions.
Exam elimination: "Performance degradation" or "drift" → Model Monitor. "Bias" or "explainability" → Clarify.
Trap 10 — Data Drift vs. Concept Drift
Confusion: Both describe model degradation over time.
Decisive difference: Data drift = input distribution changed. Concept drift = input-output relationship changed.
Exam elimination: "Inputs changed" → data drift. "Relationship changed" → concept drift. Both are detected by Model Monitor.
Trap 11 — On-Demand vs. Provisioned Throughput
Confusion: Both are Bedrock pricing models.
Decisive difference: On-Demand is pay-per-use, best for unpredictable or low usage. Provisioned Throughput is dedicated capacity, best for steady, predictable traffic.
Exam elimination: "Unpredictable usage" → On-Demand. "Steady rate of requests" → Provisioned Throughput.
Trap 12 — ROUGE vs. BLEU
Confusion: Both compare generated text to references.
Decisive difference: ROUGE measures summarization quality (recall-oriented). BLEU measures translation quality (precision-oriented).
Exam elimination: Summarization → ROUGE. Translation → BLEU.
Trap 13 — SageMaker Canvas vs. Autopilot vs. JumpStart
Confusion: All three accelerate model building.
Decisive difference: Canvas is no-code for business analysts. Autopilot automates model building and tuning. JumpStart provides pre-trained models and templates.
Exam elimination: "No-code" → Canvas. "Automated tuning" → Autopilot. "Pre-trained models" → JumpStart.
Trap 14 — Ground Truth vs. A2I
Confusion: Both involve human review.
Decisive difference: Ground Truth labels training data. A2I routes production predictions to human reviewers.
Exam elimination: "Label data for training" → Ground Truth. "Review predictions before acting" → A2I.
Trap 15 — CloudTrail vs. CloudTrail Lake
Confusion: Both record API activity.
Decisive difference: CloudTrail logs events. CloudTrail Lake provides an immutable, queryable data store with SQL support.
Exam elimination: "Log API calls" → CloudTrail. "Tamper-proof, queryable audit trail" → CloudTrail Lake.
Trap 16 — Macie vs. Inspector
Confusion: Both are security services.
Decisive difference: Macie discovers sensitive data in S3. Inspector scans for vulnerabilities.
Exam elimination: "Find PII in S3" → Macie. "Scan EC2 for vulnerabilities" → Inspector.
Trap 17 — Audit Manager vs. Artifact
Confusion: Both relate to compliance.
Decisive difference: Audit Manager assesses your AWS environment against frameworks and collects evidence. Artifact provides AWS's own compliance reports and certifications.
Exam elimination: "Assess my compliance" → Audit Manager. "Download AWS SOC report" → Artifact.
Trap 18 — Hallucination vs. Nondeterminism
Confusion: Both describe unexpected model behavior.
Decisive difference: Hallucination = false content. Nondeterminism = different outputs for the same input.
Exam elimination: "False information" → hallucination. "Different responses to same prompt" → nondeterminism.
Trap 19 — Prompt Injection vs. Jailbreak
Confusion: Both are adversarial techniques.
Decisive difference: Prompt injection overrides system instructions. Jailbreak bypasses safety features to produce harmful content.
Exam elimination: "Override instructions" → prompt injection. "Bypass safety features" → jailbreak.
Trap 20 — Data Residency vs. Data Lifecycle Management
Confusion: Both are governance concepts.
Decisive difference: Data residency governs where data is stored. Data lifecycle management governs how long data is kept and when it is deleted.
Exam elimination: "Data must stay in Region" → data residency. "Retention and deletion policies" → data lifecycle management.
Every trap has a decisive requirement that makes one option correct. Train yourself to name that requirement before comparing options.
Trigger Phrase and Decision Clue Index
Map meaningful scenario requirements to the relevant concepts. Use this when a scenario feels ambiguous.
| Trigger Phrase | Concept | Why It Matters |
|---|---|---|
| "Predict a category" | Classification | Supervised, discrete output |
| "Predict a number" | Regression | Supervised, continuous output |
| "Group similar items" | Clustering | Unsupervised, no labels |
| "No labeled data" | Unsupervised or pre-trained model | Rules out supervised training |
| "Labeled data" | Supervised learning | Enables classification or regression |
| "Minimize false positives" | Precision | Quality of positive predictions |
| "Minimize false negatives" | Recall | Coverage of actual positives |
| "Imbalanced classes" | F1 score | Accuracy is misleading |
| "Real-time response" | Low latency / inference speed | Model selection criterion |
| "Steady rate of requests" | Provisioned Throughput | Predictable usage |
| "Unpredictable usage" | On-Demand | Pay-per-use |
| "Frequently changing data" | RAG | Update knowledge base, not model |
| "Domain-specific behavior" | Fine-tuning | Labeled task data |
| "Domain knowledge from documents" | Continued pre-training | Unlabeled domain text |
| "Ground responses in sources" | RAG | Reduces hallucinations |
| "Block harmful content" | Guardrails content filters | Predefined categories |
| "Block politics" | Guardrails denied topics | Custom subject areas |
| "Protect PII" | Guardrails sensitive information filters | Detect and mask PII |
| "Detect jailbreak attempts" | Guardrails prompt attacks | Adversarial input detection |
| "Explain model decisions" | SageMaker Clarify | SHAP values, feature importance |
| "Detect production drift" | SageMaker Model Monitor | Data drift and concept drift |
| "Document model for audit" | SageMaker Model Cards | Purpose, performance, limitations |
| "Version and approve models" | SageMaker Model Registry | Lifecycle management |
| "No-code ML" | SageMaker Canvas | Visual interface |
| "Automated model tuning" | SageMaker Autopilot | AutoML |
| "Pre-trained models" | SageMaker JumpStart | Templates and notebooks |
| "Human review of predictions" | Amazon A2I | Confidence thresholds |
| "Label training data" | SageMaker Ground Truth | Managed labeling |
| "Private connection to Bedrock" | AWS PrivateLink | No public internet |
| "Encrypt model artifacts" | AWS KMS | Customer-managed keys |
| "Restrict model access" | IAM policies | Least privilege |
| "Find sensitive data in S3" | Amazon Macie | PII discovery |
| "Compliance assessment" | AWS Audit Manager | Framework-mapped evidence |
| "AWS compliance reports" | AWS Artifact | ISO, SOC, PCI |
| "API activity audit" | AWS CloudTrail | Who did what, when |
| "Tamper-proof audit trail" | AWS CloudTrail Lake | Immutable, queryable |
AWS AI Service Selection Guide
In-scope services organized by problem solved, with appropriate use cases, limitations, and similar alternatives.
| Problem | Service | Use Case | Limitation | Alternative |
|---|---|---|---|---|
| Image analysis | Amazon Rekognition | Object detection, moderation | Limited customization | SageMaker AI |
| Text analysis | Amazon Comprehend | Sentiment, entities, toxicity | Limited domain customization | Bedrock, SageMaker AI |
| Speech to text | Amazon Transcribe | Subtitles, call transcription | General purpose | HealthScribe (clinical) |
| Text to speech | Amazon Polly | Voice-overs, accessibility | Limited voice styles | None |
| Translation | Amazon Translate | Multilingual content | General purpose | None |
| Document extraction | Amazon Textract | OCR, forms, tables | Not semantic understanding | Bedrock Data Automation |
| Enterprise search | Amazon Kendra | Intranet, knowledge base | Not generative | OpenSearch + Bedrock |
| Recommendations | Amazon Personalize | Product/content recommendations | Not general-purpose ML | SageMaker AI |
| Fraud detection | Amazon Fraud Detector | Payments, account takeover | Specific to fraud | SageMaker AI |
| Custom ML | SageMaker AI | Any custom model | Requires ML expertise | Canvas (no-code) |
| Foundation models | Amazon Bedrock | GenAI applications | Managed, less control | SageMaker AI |
| Code generation | Amazon Q Developer | IDE code completion | Developer-focused | Bedrock |
| Enterprise Q&A | Amazon Q Business | Employee knowledge queries | Internal focus | Bedrock Knowledge Bases |
| Image generation | Amazon Nova Canvas | Text-to-image | Image only | Stable Diffusion on Bedrock |
| Video generation | Amazon Nova Reel | Text-to-video | Short clips | None |
Rapid Review and Memory Anchors
Short, accurate recall prompts based on meaningful conceptual distinctions.
Labeled data + prediction target = supervised. No labels + discover structure = unsupervised. Rewards + actions = reinforcement.
Category → classification. Number → regression. "Which" and "whether" = classification. "How many" and "how much" = regression.
Precision = quality of positive predictions. Recall = quantity of positives found. F1 balances both. Use F1 for imbalanced classes.
Train-good/test-bad = overfitting. Train-bad/test-bad = underfitting. Regularization trades training fit for generalization.
RAG grounds responses in external data; model stays fixed. Fine-tuning updates weights with labeled data. Frequently changing data → RAG. Task-specific behavior → fine-tuning.
Bedrock = managed foundation models. SageMaker AI = custom ML models. "Foundation model" → Bedrock. "Custom model" → SageMaker AI.
Content filters = predefined harmful categories. Denied topics = custom subject areas. Word filters = specific terms. Contextual grounding = source verification. Prompt attacks = jailbreak detection.
ROUGE = summarization. BLEU = translation. BERTScore = semantic similarity. Faithfulness = RAG grounding. Completeness = agent response coverage.
Temperature = randomness. Top K = candidate limit. Top P = nucleus sampling. Lower temperature = deterministic. Higher temperature = creative.
IAM = access control. KMS = encryption keys. PrivateLink = private network. Macie = PII in S3. Inspector = vulnerabilities. CloudTrail = API logs. CloudTrail Lake = queryable audit. Audit Manager = compliance evidence. Artifact = AWS reports.
Final-Day Revision Sheet
A compact, high-value summary of the entire blueprint. Review this the day before your exam.
Domain 1 — AI & ML (20%)
- AI → ML → Deep Learning → Generative AI (nested subsets)
- Supervised (labeled) / Unsupervised (unlabeled) / Reinforcement (rewards)
- Classification (category) vs. Regression (number)
- Accuracy misleading on imbalanced data → use F1
- Train-good/test-bad = overfitting → regularization
- Business goal first → compliance before data collection
Domain 2 — GenAI (24%)
- Tokens, embeddings, context window
- Temperature 0 = deterministic; 1 = creative
- Zero-shot, few-shot, chain-of-thought, ReAct
- RAG reduces hallucinations by grounding in sources
- Prompt injection = override instructions; jailbreak = bypass safety
Domain 3 — FM Applications (28%)
- Bedrock = managed FMs; SageMaker AI = custom ML
- Bedrock Knowledge Bases = managed RAG
- Bedrock Agents = multi-step API orchestration
- Bedrock Guardrails = safety policies
- Prompt engineering → RAG → fine-tuning → continued pre-training (increasing effort)
- On-Demand (unpredictable) vs. Provisioned Throughput (steady)
Domain 4 — Responsible AI (14%)
- Fairness, explainability, transparency, privacy, safety, robustness, controllability
- SageMaker Clarify = bias detection + SHAP explainability
- Model Cards = standardized documentation
- A2I = human-in-the-loop workflows
Domain 5 — Security (14%)
- IAM = access control; KMS = encryption; PrivateLink = private network
- Bedrock does not share data with third-party providers
- Macie = PII discovery; Inspector = vulnerabilities
- CloudTrail = API logs; CloudTrail Lake = immutable queryable
- Audit Manager = compliance evidence; Artifact = AWS reports
- Data residency = where data lives; lifecycle = how long
Read every question for the decisive requirement. The exam rewards the candidate who identifies the constraint, not the one who memorizes the most services.
Practice-Based Self-Assessment Checklist
Mark each item you can explain confidently. Unchecked items are your review priorities.
Domain 1
Domain 2
Domain 3
Domain 4
Domain 5
Acronym and Glossary Reference
Searchable or clearly organized terminology for quick reference.
| Term/Acronym | Expansion | Definition |
|---|---|---|
| AI | Artificial Intelligence | Broad field of simulating human intelligence |
| A2I | Amazon Augmented AI | Human review workflows for ML predictions |
| BERTScore | Bidirectional Encoder Representations from Transformers Score | Semantic similarity metric |
| BLEU | Bilingual Evaluation Understudy | Translation quality metric |
| CTR | Click-Through Rate | Engagement metric |
| FM | Foundation Model | Large pre-trained adaptable model |
| IAM | Identity and Access Management | AWS access control service |
| KMS | Key Management Service | AWS encryption key management |
| LLM | Large Language Model | Text-specialized foundation model |
| MCP | Model Context Protocol | Standard for connecting AI to external tools |
| ML | Machine Learning | Subset of AI that learns from data |
| PII | Personally Identifiable Information | Sensitive personal data |
| RAG | Retrieval Augmented Generation | Grounding LLM responses in external data |
| RLHF | Reinforcement Learning from Human Feedback | Aligning models with human preferences |
| ROUGE | Recall-Oriented Understudy for Gisting Evaluation | Summarization quality metric |
| SHAP | SHapley Additive exPlanations | Feature importance for explainability |
Exam-Day Preparation Checklist
Practical preparation advice, with logistics verified against current official guidance where applicable.
Before the Exam
During the Exam
After the Exam
References
All references are official AWS documentation, AWS Builder Center articles, or AWS whitepapers. Time-sensitive details were verified against the current documentation as of this guide's publication.
- AWS Certified AI Practitioner (AIF-C01) Exam Guide — Official exam domains, task statements, and weights.
- AIF-C01 In-Scope AWS Services — Official list of in-scope services.
- Amazon Bedrock User Guide — Service overview, models, capabilities.
- Amazon Bedrock Knowledge Bases — Managed RAG implementation.
- Amazon Bedrock Guardrails — Content filters, denied topics, PII filters, contextual grounding.
- Amazon Bedrock Agents — Multi-step orchestration and API calls.
- Amazon Bedrock Model Evaluation — Automatic and human evaluation metrics.
- Amazon Bedrock Data Protection — Data-handling guarantees and third-party sharing policy.
- AWS PrivateLink for Amazon Bedrock — Private VPC connectivity.
- SageMaker Model Cards — Standardized model documentation.
- SageMaker Clarify — Bias detection and explainability.
- SageMaker Model Monitor — Production drift detection.
- SageMaker Automatic Model Tuning — Hyperparameter optimization.
- SageMaker Canvas — No-code ML.
- SageMaker JumpStart — Pre-trained models and templates.
- SageMaker Data Wrangler — Visual data preparation.
- SageMaker Ground Truth — Data labeling.
- AWS Audit Manager — Compliance evidence collection.
- AWS Config — Resource configuration and compliance.
- AWS CloudTrail — API activity logging.
- AWS CloudTrail Lake — Immutable, queryable audit store.
- Amazon Macie — Sensitive data discovery.
- Amazon Inspector — Vulnerability scanning.
- AWS Artifact — AWS compliance reports.
- Amazon Q Business — Enterprise AI assistant.
- Amazon Q Developer — Developer productivity.
- Amazon Nova — Multimodal foundation models.
- Amazon Nova Canvas — Image generation.
- Amazon Nova Reel — Video generation.
- AWS — What is RAG? — RAG explanation.
- AWS — What is Prompt Engineering? — Prompting techniques.
- AWS — What are Embeddings? — Embeddings explanation.
- AWS — What is Overfitting? — Overfitting explanation.
- AWS Responsible AI — Responsible AI dimensions and resources.
- AWS Well-Architected Machine Learning Lens — ML lifecycle phases.
- AWS CAF for AI — AI governance framework.
- AWS Data Residency — Data residency compliance.
- AWS Prescriptive Guidance — Common LLM Attacks — Prompt injection and jailbreak.
- Amazon Bedrock Prompt Management — Store and reuse prompts.
- Amazon Bedrock Provisioned Throughput — Dedicated capacity.
- Amazon Bedrock Batch Inference — Bulk generation.
All references were verified against current official AWS documentation at the time of writing. Time-sensitive details (service features, pricing models, metric names) should be re-verified against the latest AWS documentation before relying on them in production.