CloudExamPro — AWS Certified AI Practitioner (AIF-C01) Premium Study Guide
CloudExamPro Premium Edition 2026

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.

5
Exam Domains
17
Chapters
13
Premium Modules
30+
Decision Matrices
25
Exam Traps

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.

Coach's Note

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

Table 0.1 — Choose Your Reading Path
If You Are…Start WithThenSkip Until Review
New to AI/MLTerminology Primer → Ch 1–5Ch 6–17 in orderPremium Modules M6–M8
Experienced with AWS but new to AICh 6–9 (GenAI)Ch 10–13 (FM applications)Ch 1–5 (skim)
Experienced with AI/ML but new to AWSCh 5, Ch 10, Ch 11Ch 16–17 (security/governance)Ch 1–4 (skim)
Exam in 7 daysM10 (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.

Table 0.2 — Official Exam Domains and Weights
DomainWeightFocus
Domain 1: Fundamentals of AI and ML20%AI/ML concepts, learning paradigms, problem types, data, evaluation metrics, AWS AI services
Domain 2: Fundamentals of Generative AI24%Foundation models, LLM mechanics, prompt engineering, hallucinations, RAG
Domain 3: Applications of Foundation Models28%Amazon Bedrock, SageMaker AI, customization strategy, agents, Guardrails, evaluation
Domain 4: Guidelines for Responsible AI14%Fairness, bias, explainability, transparency, human oversight, safety
Domain 5: Security, Compliance, and Governance14%IAM, encryption, PrivateLink, CloudTrail, Macie, Audit Manager, data residency, governance
Important

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

Table 0.3 — 7-Day Study Plan
DayFocusDeliverable
1Ch 1–3 (AI/ML foundations, lifecycle)Complete Term Primer + Ch 1–3 Knowledge Checks
2Ch 4–5 (Evaluation, AWS services)Memorize evaluation metrics matrix
3Ch 6–7 (GenAI, LLM mechanics)Complete inference parameter matrix
4Ch 8–9 (Prompt engineering, RAG)Prompt technique comparison table
5Ch 10–13 (Bedrock, SageMaker, customization)Bedrock vs SageMaker matrix
6Ch 14–17 (Responsible AI, security)M6 Trap Library + M7 Trigger Phrases
7M9–M10 (Rapid review, final-day sheet)M11 Self-Assessment + M13 Exam-Day Checklist

14-Day Recommended Plan

Table 0.4 — 14-Day Study Plan
DaysFocusPriority
1–3Ch 1–5 (Domain 1)Foundations — do not rush
4–6Ch 6–9 (Domain 2)Highest combined weight with Domain 3
7–10Ch 10–13 (Domain 3)Largest single domain (28%)
11Ch 14–15 (Domain 4)Responsible AI
12Ch 16–17 (Domain 5)Security, compliance, governance
13M1–M8 (Premium Modules)Decision matrices + trap library
14M9–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.

Table 0.5 — Essential AI/ML Terminology
TermPlain-English DefinitionExam Context
Artificial Intelligence (AI)Broad field of making machines perform tasks requiring human intelligenceThe outermost category
Machine Learning (ML)Subset of AI that learns patterns from dataMost exam scenarios sit here
Deep LearningML using multi-layer neural networksImages, audio, text at scale
Generative AIDeep learning that creates new contentText, image, video generation
Foundation Model (FM)Large pre-trained model adaptable to many tasksBedrock's core offering
Large Language Model (LLM)Foundation model specialized for textChatbots, summarization, translation
TokenUnit of text a model processes (word, subword, character)Context window, billing
EmbeddingNumeric vector representing meaningRAG, semantic search
Context WindowMaximum tokens a model can process at onceWhy long inputs fail
PromptInput instruction to a modelPrompt engineering
InferenceUsing a trained model to generate outputRuntime phase
TrainingLearning model weights from dataPre-training, fine-tuning
Fine-TuningFurther training a model on labeled task dataDomain adaptation
Continued Pre-TrainingFurther training on unlabeled domain dataDomain knowledge expansion
RAGRetrieval Augmented Generation — grounding responses in external dataReduces hallucinations
HallucinationModel generates plausible but false contentKey GenAI risk
TemperatureInference parameter controlling randomness0 = deterministic, 1 = creative
Top KLimits next-token candidates to K most probableDiversity control
Top PNucleus sampling — limits candidates by cumulative probabilityAlternative to Top K
GuardrailsSafety controls on model input and outputBedrock Guardrails
AgentAI system that reasons and calls external tools/APIsBedrock Agents
Vector DatabaseDatabase optimized for similarity search on embeddingsOpenSearch, Aurora pgvector
ChunkingSplitting documents into smaller units for embeddingRAG pipeline
OverfittingModel memorizes training data, fails on new dataTrain-good/test-bad
UnderfittingModel too simple to learn the patternTrain-bad/test-bad
RegularizationTechnique to reduce overfitting (L1, L2)SageMaker Linear Learner
PrecisionCorrect positive predictions / all positive predictionsMinimize false positives
RecallCorrect positive predictions / all actual positivesMinimize false negatives
F1 ScoreHarmonic mean of precision and recallImbalanced classes
ROUGESummarization evaluation metricCompare to references
BLEUTranslation evaluation metricCompare to references
BERTScoreSemantic similarity metric using embeddingsBedrock auto-eval for summarization
Data DriftInput distribution changes over timeModel Monitor detects
Concept DriftInput-output relationship changesModel Monitor detects
BiasSystematic error producing unfair outcomesSageMaker Clarify detects
ExplainabilityUnderstanding why a model made a decisionSageMaker Clarify SHAP values
Data ResidencyData must remain in a specific geographic regionCompliance requirement
PrivateLinkPrivate network connection to AWS servicesBedrock without public internet
Model CardStandardized model documentationGovernance and audit
Prompt InjectionMalicious input overriding system instructionsSecurity risk
Domain 1 · Chapter 1

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.

Memory Anchor

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

Table 1.1 — Managed AI Services vs. ML Platforms
DimensionManaged AI ServicesML Platforms
ExamplesRekognition, Comprehend, Transcribe, Polly, Translate, Personalize, Kendra, TextractSageMaker AI, Bedrock (customization), Deep Learning AMIs
ML expertise requiredNoneYes (SageMaker); moderate (Bedrock fine-tuning)
Time to valueMinutesDays to weeks
Best forStandard tasksDomain-specific tasks, proprietary data
Coach's Takeaway

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.

Domain 1 · Chapter 2

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.

Memory Anchor

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

Table 2.1 — Classification vs. Regression
DimensionClassificationRegression
Output typeCategoryContinuous number
ExampleWill customer churn? (yes/no)How much will customer spend? ($)
Loss functionCross-entropyMSE, MAE
Evaluation metricPrecision, recall, F1, accuracyRMSE, MAE, R²
Domain 1 · Chapter 3

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.

Key Concept

Business goal first, always. Compliance, regulatory requirements, and success metrics are defined before any technical work begins.

3.2 Data Types

Table 3.1 — Data Types and ML Approaches
Data TypeExampleML ApproachAWS Service
Structured (tabular)Customer records, sales transactionsClassical MLSageMaker AI, Personalize
Unstructured (text)Reviews, emails, documentsNLP, LLMsComprehend, Bedrock, Textract
Unstructured (image/video)Photos, surveillanceComputer visionRekognition, SageMaker AI
Unstructured (audio)Voice recordingsSpeech recognitionTranscribe, HealthScribe
Time-seriesStock prices, sensor dataForecastingSageMaker AI (DeepAR)
Domain 1 · Chapter 4

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

Table 4.1 — Classification Metrics
MetricFormulaMeasuresWhen to Use
Accuracy(TP+TN) / TotalOverall correctnessBalanced classes
PrecisionTP / (TP+FP)Correctness of positive predictionsMinimize false positives
RecallTP / (TP+FN)Coverage of actual positivesMinimize false negatives
F1 Score2 × (P × R) / (P + R)Balance of precision and recallImbalanced classes
Exam Trap

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

Table 4.2 — Text Generation Metrics
MetricPurposeWhen to Use
ROUGESummarization quality (recall-oriented)Comparing summaries to references
BLEUTranslation quality (precision-oriented)Comparing translations to references
BERTScoreSemantic similarity via embeddingsBedrock automatic evaluation for summarization
Important Nuance

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

Table 4.3 — Overfitting vs. Underfitting
SignatureDiagnosisRemedy
Train-good, test-badOverfittingIncrease regularization, reduce complexity, more data
Train-bad, test-badUnderfittingIncrease complexity, add features, reduce regularization
Domain 1 · Chapter 5

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

Table 5.1 — Managed AI Services by Problem
ServiceProblem SolvedWhen to UseAlternative
Amazon RekognitionImage and video analysisObject detection, facial analysis, moderationSageMaker AI
Amazon ComprehendText analysisSentiment, entities, toxicitySageMaker AI, Bedrock
Amazon TranscribeSpeech to textSubtitles, call transcriptionHealthScribe
Amazon PollyText to speechVoice-overs, accessibilityNone
Amazon TranslateLanguage translationMultilingual contentNone
Amazon TextractDocument extractionOCR, forms, tablesBedrock Data Automation
Amazon KendraEnterprise searchIntranet, knowledge base searchOpenSearch Service
Amazon PersonalizeRecommendationsProduct/content recommendationsSageMaker AI
Amazon Fraud DetectorFraud detectionPayments, account takeoverSageMaker AI

5.2 Amazon SageMaker AI Feature Map

Table 5.2 — SageMaker AI Features by Task
FeaturePurpose
SageMaker StudioIntegrated development environment
SageMaker AutopilotAutomated model building and tuning
SageMaker JumpStartPre-trained models and solution templates
SageMaker Data WranglerVisual data preparation
SageMaker ClarifyBias detection and explainability
SageMaker Model MonitorProduction drift detection
SageMaker Model RegistryModel versioning and approval
SageMaker Model CardsStandardized model documentation
SageMaker Ground TruthData labeling with human review
SageMaker CanvasNo-code ML for business analysts
SageMaker Feature StoreCentralized feature repository
SageMaker PipelinesML workflow orchestration
SageMaker Serverless InferenceModel deployment without managing infrastructure
SageMaker Batch TransformOffline inference for large datasets

5.3 Amazon Bedrock Feature Map

Table 5.3 — Bedrock Features by Task
FeaturePurpose
Model accessBrowse and invoke FMs from multiple providers
Knowledge BasesManaged RAG — connect data and retrieve context
AgentsOrchestrate multi-step tasks with API calls
GuardrailsContent filters, denied topics, PII detection, grounding
Prompt ManagementStore, version, and reuse prompts
Model EvaluationAutomatic and human evaluation of outputs
Provisioned ThroughputDedicated capacity for steady traffic
Batch InferenceBulk generation at discounted rates
Prompt CachingReuse prompt prefixes to reduce latency and cost
Prompt RouterDynamically select the best model per request
Coach's Takeaway

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 Complete

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.

Domain-specific questions targeting AI & ML distinctions
Instant score breakdown — see exactly where you lose points
Explanations written in the same instructor voice as this guide
Built for AIF-C01's question style — no generic filler
Test Your Domain 1 Readiness →
Domain 2 · Chapter 6

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.

Memory Anchor

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

Table 6.1 — Model Selection Factors
FactorWhat It MeansExam Trigger
ModalityInput/output types supported"Text and image inputs" → multimodal
LatencyResponse time"Real-time" → prioritize low latency
Context windowMaximum input size in tokens"Long documents fail" → context limit
CostPer-token pricing"Minimize cost" → smaller model
CustomizationFine-tuning support"Domain-specific" → fine-tuning
Coach's Takeaway

Select the smallest model that satisfies the performance requirement. Larger models cost more without adding value when a smaller model already meets the task.

Domain 2 · Chapter 7

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.

Exam Trap

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

Table 7.1 — Inference Parameters
ParameterEffectUse When
TemperatureControls randomness (0 = deterministic, 1 = creative)Lower for facts, higher for creativity
Top KLimits next-token candidates to K most probableBalance diversity and focus
Top PNucleus sampling — cumulative probability cutoffAlternative to Top K
Max tokensMaximum output lengthControl response size
Stop sequencesTokens that end generationPrevent runaway output
Key Distinction

Temperature 0 = deterministic. Temperature 1 = maximum randomness. Lower temperature reduces hallucination risk. Higher temperature increases creativity.

Domain 2 · Chapter 8

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

Table 8.1 — Prompt Engineering Techniques
TechniqueWhat It DoesWhen to UseExample Trigger
Zero-shotNo examples; task onlySimple, well-defined tasks"Classify the following text…"
Few-shotA few labeled examples before taskFormat or style must be matchedThree examples, then "Now classify this"
Chain-of-thoughtInstructs step-by-step reasoningComplex multi-step problems"Think step by step"
ReActReasoning + external tool/API callsNeed live data or actions"Check inventory and respond"
Prompt chainingOutput of one prompt feeds nextMulti-stage complex tasksSequential subtask execution
Memory Anchor

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.

Domain 2 · Chapter 9

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

Table 9.1 — RAG Pipeline Stages
StageWhen It RunsLatency Requirement
Parse documentsOffline (batch)None
Chunk documentsOffline (batch)None
Generate content embeddingsOffline (batch)None
Build search indexOffline (batch)None
Generate query embeddingsOnline (query time)Low
Retrieve relevant contentOnline (query time)Low
Generate responseOnline (query time)Low
Coach's Takeaway

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 Complete

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.

Domain-specific questions targeting GenAI distinctions
Instant score breakdown — see exactly where you lose points
Explanations written in the same instructor voice as this guide
Built for AIF-C01's question style — no generic filler
Test Your Domain 2 Readiness →
Domain 3 · Chapter 10

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

Table 10.1 — Bedrock Capabilities
CapabilityPurposeWhen to Use
Knowledge BasesManaged RAGGround responses in company data
AgentsMulti-step task orchestrationAPI calls, tool use, transactions
GuardrailsSafety controlsBlock harmful content, PII, denied topics
Prompt ManagementStore and reuse promptsStandardize prompt templates
Model EvaluationAssess model qualityCompare models, measure accuracy
Prompt CachingReuse prompt prefixesReduce latency and cost
Prompt RouterDynamic model selectionSingle endpoint, best model per request

10.3 Pricing Models

Table 10.2 — Bedrock Pricing Models
ModelBest ForWhen to Choose
On-DemandUnpredictable or low usagePilot phase, variable traffic
Provisioned ThroughputSteady, high-volume trafficPredictable usage, custom models
BatchPeriodic bulk generationWeekly reports, catalog updates
Coach's Takeaway

Steady, predictable traffic → Provisioned Throughput. Unpredictable or low usage → On-Demand. Periodic bulk → Batch.

Domain 3 · Chapter 11

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

Table 11.1 — SageMaker AI Features by Lifecycle Stage
Lifecycle StageFeaturePurpose
Data preparationData WranglerVisual, low-code data preparation
Data labelingGround TruthHuman review and labeling
Model buildingAutopilotAutomated model building and tuning
Model buildingCanvasNo-code ML for business analysts
Model buildingJumpStartPre-trained models and templates
TrainingSageMaker TrainingManaged training jobs
Bias/explainabilityClarifyBias detection and SHAP explanations
GovernanceModel CardsStandardized model documentation
GovernanceModel RegistryVersioning and approval workflows
DeploymentEndpointsReal-time inference
DeploymentServerless InferenceNo infrastructure management
DeploymentBatch TransformOffline inference for large datasets
MonitoringModel MonitorDrift detection
Exam Trap

Model Monitor vs. Clarify. Model Monitor detects production drift. Clarify detects bias and explains predictions. Both are governance features, but they solve different problems.

Domain 3 · Chapter 12

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

Table 12.1 — Customization Approaches
ApproachData RequiredEffortWhen to Use
Prompt engineeringNoneLowestStyle, format, simple task adaptation
RAGDocuments (unlabeled)ModerateFrequently changing data, grounded answers
Fine-tuningLabeled input-output pairsHighTask-specific behavior, style adaptation
Continued pre-trainingUnlabeled domain textHighestDomain knowledge expansion
Memory Anchor

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.

Domain 3 · Chapter 13

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

Table 13.1 — Bedrock Guardrails Policies
PolicyWhat It DoesWhen to Use
Content filtersBlock harmful categories (hate, violence, sexual, insults)General safety
Denied topicsBlock custom subject areasPolitics, competitor products, legal advice
Word filtersBlock specific words or phrasesProfanity, brand names
Sensitive information filtersBlock or mask PIICustomer data protection
Contextual grounding checkVerify responses are supported by source contextReduce hallucinations
Prompt attacksDetect jailbreak attemptsPublic-facing chatbots
Exam Trap

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

Table 13.2 — Bedrock Evaluation Metrics
MetricWhat It MeasuresTask Type
BERTScoreSemantic similarity to referenceSummarization (automatic)
ROUGEN-gram overlap with referenceSummarization (academic)
BLEUTranslation qualityTranslation
FaithfulnessResponse grounded in retrieved contextRAG
CompletenessAll parts of prompt addressedAgent responses
CorrectnessFactual accuracyGeneral
HarmfulnessToxic content detectionSafety
RefusalModel declines to answerGuardrail testing
Domain 3 Complete

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.

Domain-specific questions targeting FM applications
Instant score breakdown — see exactly where you lose points
Explanations written in the same instructor voice as this guide
Built for AIF-C01's question style — no generic filler
Test Your Domain 3 Readiness →
Domain 4 · Chapter 14

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

Table 14.1 — Responsible AI Dimensions
DimensionDefinitionExam Trigger
FairnessEquitable outcomes across demographic groupsDiverse data, protected groups
ExplainabilityUnderstanding why a model made a decisionRationale, SHAP, feature importance
TransparencyVisibility into how AI systems make decisionsModel Cards, documentation
Privacy and SecurityData protection and access controlEncryption, IAM, PII
SafetyPreventing harmful output and misuseGuardrails, content filters
RobustnessResilience to unexpected inputsAdversarial testing
ControllabilityHuman oversight and interventionHuman-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.

Coach's Takeaway

Bias from training data → fix the data. Bias from model design → use fairness-aware techniques. Diverse, balanced data is the foundation of fair AI.

Domain 4 · Chapter 15

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

Table 15.1 — Transparency Documentation Tools
ToolWhat It DocumentsWhen to Use
SageMaker Model CardsPurpose, performance, limitations, risksCustom model governance
AWS AI Service CardsAWS service capabilities and limitationsUnderstanding managed services
SageMaker Model RegistryVersion tracking and approval statusModel 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.

Key Concept

High-stakes decisions about people (hiring, lending, healthcare) require human review. A2I provides the workflow infrastructure.

Domain 4 Complete

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.

Domain-specific questions targeting Responsible AI
Instant score breakdown — see exactly where you lose points
Explanations written in the same instructor voice as this guide
Built for AIF-C01's question style — no generic filler
Test Your Domain 4 Readiness →
Domain 5 · Chapter 16

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

Table 16.1 — Shared Responsibility for AI Services
LayerAWS ResponsibilityYour Responsibility
InfrastructureData centers, hardware, networkingNone
Managed service endpointsAPI availability, patchingConfigure VPC endpoints
Foundation models (Bedrock)Model hosting, base model integrityModel access policies, guardrails
Training dataStorage durabilityData classification, encryption, access control
Application logicNoneInput validation, output filtering, logging
Key Concept

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.

Domain 5 · Chapter 17

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

Table 17.1 — AWS Compliance Services
ServicePurposeWhen to Use
AWS Audit ManagerAutomated evidence collection and compliance reportsRegulatory assessments
AWS ConfigResource configuration tracking and compliancePolicy adherence monitoring
AWS CloudTrailAPI activity loggingAudit trails
AWS CloudTrail LakeImmutable, queryable API activity storeTamper-proof audit
AWS ArtifactAWS compliance reports and certificationsDemonstrating AWS compliance
Amazon MacieSensitive data discovery in S3PII detection
Amazon InspectorVulnerability scanningEC2, 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.

Coach's Takeaway

Data lifecycle management covers creation, updates, retention, and scheduled deletion. It is a governance component, not a security service.

Domain 5 Complete

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.

Domain-specific questions targeting Security & Governance
Instant score breakdown — see exactly where you lose points
Explanations written in the same instructor voice as this guide
Built for AIF-C01's question style — no generic filler
Test Your Domain 5 Readiness →
Premium Module M1

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

Table M1.1 — Amazon Bedrock vs. Amazon SageMaker AI
DimensionAmazon BedrockAmazon SageMaker AI
Primary purposeManaged access to foundation modelsBuild, train, deploy custom ML models
ML expertise requiredLow to moderateModerate to high
Model customizationFine-tuning, continued pre-trainingFull control over algorithms and training
Infrastructure managementFully managedManaged instances, but more configuration
Best forGenAI applications, RAG, agentsCustom 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

Table M1.2 — Customization Approach Selection
RequirementPrompt EngineeringRAGFine-Tuning
Data changes frequentlyNoYesNo
Need source citationsNoYesNo
Task-specific behaviorLimitedNoYes
Lowest costYesModerateHigh
Least effortYesModerateHigh
Domain knowledge expansionNoPartialNo (use continued pre-training)

M1.3 Classification vs. Regression

Table M1.3 — Classification vs. Regression
DimensionClassificationRegression
OutputCategoryContinuous number
ExampleWill customer churn? (yes/no)How much will customer spend? ($)
MetricsPrecision, recall, F1, accuracy, AUCRMSE, MAE, R²
Exam trigger"Which category," "whether""How many," "how much"

M1.4 Supervised vs. Unsupervised vs. Reinforcement Learning

Table M1.4 — Learning Paradigms
ParadigmDataGoalExam Trigger
SupervisedLabeledPredict known outcome"Predict," "classify," "labeled data"
UnsupervisedUnlabeledDiscover structure"Group," "segment," "no labels"
ReinforcementReward signalsLearn sequential decisions"Reward," "trial and error," "agent"
Premium Module M2

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

Table M2.1 — Scenario-Based Selection
ScenarioChooseWhy
Build a chatbot grounded in company documentsBedrock with Knowledge BasesManaged RAG, no training
Train a custom churn prediction modelSageMaker AITabular data, classical ML
Fine-tune an LLM for domain-specific toneBedrock fine-tuningManaged fine-tuning workflow
Detect bias in a hiring modelSageMaker ClarifyPre-training and post-training bias metrics
Monitor a deployed model for driftSageMaker Model MonitorProduction drift detection
Build an AI assistant that queries APIsBedrock AgentsMulti-step orchestration
Premium Module M3

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

Table M3.1 — Approach Selection by Problem
ProblemApproachWhy
Responses are generic or off-topicPrompt engineering (few-shot)Examples anchor the model
Model lacks domain knowledgeContinued pre-training or RAGPre-training for internal knowledge; RAG for external retrieval
Model needs specific output formatPrompt engineering or fine-tuningPrompting for simple format; fine-tuning for complex patterns
Data changes frequentlyRAGUpdate knowledge base, not model
Model needs to learn a new taskFine-tuningTask-specific labeled data
Model needs source citationsRAGRetrieved documents provide provenance
Exam Trap

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.

Premium Module M4

AI/ML Evaluation Metrics Guide

This module defines key metrics, explains what they measure, and shows when each is useful.

M4.1 Classification Metrics

Table M4.1 — Classification Metrics
MetricFormulaMeasuresWhen to Use
Accuracy(TP+TN)/TotalOverall correctnessBalanced classes
PrecisionTP/(TP+FP)Correctness of positivesMinimize false positives
RecallTP/(TP+FN)Coverage of positivesMinimize false negatives
F12×(P×R)/(P+R)Balance of precision and recallImbalanced classes
AUCArea under ROC curveDiscrimination abilityBinary classification

M4.2 Regression Metrics

Table M4.2 — Regression Metrics
MetricMeasuresWhen to Use
RMSERoot mean squared errorPenalizes large errors
MAEMean absolute errorInterpretable in original units
MSEMean squared errorStandard for optimization
R²Proportion of variance explainedGoodness of fit

M4.3 Generative AI Metrics

Table M4.3 — Text Generation Metrics
MetricPurposeWhen to Use
ROUGESummarization qualityCompare summaries to references
BLEUTranslation qualityCompare translations to references
BERTScoreSemantic similarityBedrock auto-eval for summarization
FaithfulnessGrounded in retrieved contextRAG evaluation
CompletenessAll prompt parts addressedAgent response quality
Premium Module M5

Generative AI Terminology Reference

Concise, accurate definitions with examples for the GenAI terms the exam tests.

Table M5.1 — Generative AI Terminology
TermDefinitionExample
Foundation Model (FM)Large pre-trained model adaptable to many tasksAmazon Nova, Anthropic Claude
Large Language Model (LLM)FM specialized for textClaude, Llama, Titan Text
TokenUnit of text processing"Hello world" = 2 tokens
EmbeddingNumeric vector representing meaningText → [0.2, -0.5, 0.8, …]
Context WindowMaximum input size in tokensClaude 200K context
TemperatureRandomness parameter0 = deterministic, 1 = creative
Top KLimits next-token candidatesTop K = 50
Top PNucleus sampling cutoffTop P = 0.9
RAGGrounding responses in external dataBedrock Knowledge Bases
HallucinationPlausible but false outputFabricated citation
GuardrailsSafety controlsBedrock Guardrails
AgentAI system that calls tools/APIsBedrock Agents
Vector DatabaseDatabase for similarity searchOpenSearch, Aurora pgvector
ChunkingSplitting documents for embedding500-token chunks with overlap
Prompt InjectionMalicious input overriding instructions"Ignore previous instructions"
Premium Module M6

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.

Memory Anchor

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.

Coach's Takeaway

Every trap has a decisive requirement that makes one option correct. Train yourself to name that requirement before comparing options.

Premium Module M7

Trigger Phrase and Decision Clue Index

Map meaningful scenario requirements to the relevant concepts. Use this when a scenario feels ambiguous.

Table M7.1 — Trigger Phrase Index
Trigger PhraseConceptWhy It Matters
"Predict a category"ClassificationSupervised, discrete output
"Predict a number"RegressionSupervised, continuous output
"Group similar items"ClusteringUnsupervised, no labels
"No labeled data"Unsupervised or pre-trained modelRules out supervised training
"Labeled data"Supervised learningEnables classification or regression
"Minimize false positives"PrecisionQuality of positive predictions
"Minimize false negatives"RecallCoverage of actual positives
"Imbalanced classes"F1 scoreAccuracy is misleading
"Real-time response"Low latency / inference speedModel selection criterion
"Steady rate of requests"Provisioned ThroughputPredictable usage
"Unpredictable usage"On-DemandPay-per-use
"Frequently changing data"RAGUpdate knowledge base, not model
"Domain-specific behavior"Fine-tuningLabeled task data
"Domain knowledge from documents"Continued pre-trainingUnlabeled domain text
"Ground responses in sources"RAGReduces hallucinations
"Block harmful content"Guardrails content filtersPredefined categories
"Block politics"Guardrails denied topicsCustom subject areas
"Protect PII"Guardrails sensitive information filtersDetect and mask PII
"Detect jailbreak attempts"Guardrails prompt attacksAdversarial input detection
"Explain model decisions"SageMaker ClarifySHAP values, feature importance
"Detect production drift"SageMaker Model MonitorData drift and concept drift
"Document model for audit"SageMaker Model CardsPurpose, performance, limitations
"Version and approve models"SageMaker Model RegistryLifecycle management
"No-code ML"SageMaker CanvasVisual interface
"Automated model tuning"SageMaker AutopilotAutoML
"Pre-trained models"SageMaker JumpStartTemplates and notebooks
"Human review of predictions"Amazon A2IConfidence thresholds
"Label training data"SageMaker Ground TruthManaged labeling
"Private connection to Bedrock"AWS PrivateLinkNo public internet
"Encrypt model artifacts"AWS KMSCustomer-managed keys
"Restrict model access"IAM policiesLeast privilege
"Find sensitive data in S3"Amazon MaciePII discovery
"Compliance assessment"AWS Audit ManagerFramework-mapped evidence
"AWS compliance reports"AWS ArtifactISO, SOC, PCI
"API activity audit"AWS CloudTrailWho did what, when
"Tamper-proof audit trail"AWS CloudTrail LakeImmutable, queryable
Premium Module M8

AWS AI Service Selection Guide

In-scope services organized by problem solved, with appropriate use cases, limitations, and similar alternatives.

Table M8.1 — Service Selection by Problem
ProblemServiceUse CaseLimitationAlternative
Image analysisAmazon RekognitionObject detection, moderationLimited customizationSageMaker AI
Text analysisAmazon ComprehendSentiment, entities, toxicityLimited domain customizationBedrock, SageMaker AI
Speech to textAmazon TranscribeSubtitles, call transcriptionGeneral purposeHealthScribe (clinical)
Text to speechAmazon PollyVoice-overs, accessibilityLimited voice stylesNone
TranslationAmazon TranslateMultilingual contentGeneral purposeNone
Document extractionAmazon TextractOCR, forms, tablesNot semantic understandingBedrock Data Automation
Enterprise searchAmazon KendraIntranet, knowledge baseNot generativeOpenSearch + Bedrock
RecommendationsAmazon PersonalizeProduct/content recommendationsNot general-purpose MLSageMaker AI
Fraud detectionAmazon Fraud DetectorPayments, account takeoverSpecific to fraudSageMaker AI
Custom MLSageMaker AIAny custom modelRequires ML expertiseCanvas (no-code)
Foundation modelsAmazon BedrockGenAI applicationsManaged, less controlSageMaker AI
Code generationAmazon Q DeveloperIDE code completionDeveloper-focusedBedrock
Enterprise Q&AAmazon Q BusinessEmployee knowledge queriesInternal focusBedrock Knowledge Bases
Image generationAmazon Nova CanvasText-to-imageImage onlyStable Diffusion on Bedrock
Video generationAmazon Nova ReelText-to-videoShort clipsNone
Premium Module M9

Rapid Review and Memory Anchors

Short, accurate recall prompts based on meaningful conceptual distinctions.

Learning Paradigms

Labeled data + prediction target = supervised. No labels + discover structure = unsupervised. Rewards + actions = reinforcement.

Classification vs. Regression

Category → classification. Number → regression. "Which" and "whether" = classification. "How many" and "how much" = regression.

Precision vs. Recall

Precision = quality of positive predictions. Recall = quantity of positives found. F1 balances both. Use F1 for imbalanced classes.

Overfitting vs. Underfitting

Train-good/test-bad = overfitting. Train-bad/test-bad = underfitting. Regularization trades training fit for generalization.

RAG vs. Fine-Tuning

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 vs. SageMaker AI

Bedrock = managed foundation models. SageMaker AI = custom ML models. "Foundation model" → Bedrock. "Custom model" → SageMaker AI.

Guardrails Policies

Content filters = predefined harmful categories. Denied topics = custom subject areas. Word filters = specific terms. Contextual grounding = source verification. Prompt attacks = jailbreak detection.

Evaluation Metrics

ROUGE = summarization. BLEU = translation. BERTScore = semantic similarity. Faithfulness = RAG grounding. Completeness = agent response coverage.

Inference Parameters

Temperature = randomness. Top K = candidate limit. Top P = nucleus sampling. Lower temperature = deterministic. Higher temperature = creative.

Security Services

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.

Premium Module M10

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
Last-Minute Reminder

Read every question for the decisive requirement. The exam rewards the candidate who identifies the constraint, not the one who memorizes the most services.

Premium Module M11

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

Premium Module M12

Acronym and Glossary Reference

Searchable or clearly organized terminology for quick reference.

Table M12.1 — Acronyms and Glossary
Term/AcronymExpansionDefinition
AIArtificial IntelligenceBroad field of simulating human intelligence
A2IAmazon Augmented AIHuman review workflows for ML predictions
BERTScoreBidirectional Encoder Representations from Transformers ScoreSemantic similarity metric
BLEUBilingual Evaluation UnderstudyTranslation quality metric
CTRClick-Through RateEngagement metric
FMFoundation ModelLarge pre-trained adaptable model
IAMIdentity and Access ManagementAWS access control service
KMSKey Management ServiceAWS encryption key management
LLMLarge Language ModelText-specialized foundation model
MCPModel Context ProtocolStandard for connecting AI to external tools
MLMachine LearningSubset of AI that learns from data
PIIPersonally Identifiable InformationSensitive personal data
RAGRetrieval Augmented GenerationGrounding LLM responses in external data
RLHFReinforcement Learning from Human FeedbackAligning models with human preferences
ROUGERecall-Oriented Understudy for Gisting EvaluationSummarization quality metric
SHAPSHapley Additive exPlanationsFeature importance for explainability
Premium Module M13

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.

  1. AWS Certified AI Practitioner (AIF-C01) Exam Guide — Official exam domains, task statements, and weights.
  2. AIF-C01 In-Scope AWS Services — Official list of in-scope services.
  3. Amazon Bedrock User Guide — Service overview, models, capabilities.
  4. Amazon Bedrock Knowledge Bases — Managed RAG implementation.
  5. Amazon Bedrock Guardrails — Content filters, denied topics, PII filters, contextual grounding.
  6. Amazon Bedrock Agents — Multi-step orchestration and API calls.
  7. Amazon Bedrock Model Evaluation — Automatic and human evaluation metrics.
  8. Amazon Bedrock Data Protection — Data-handling guarantees and third-party sharing policy.
  9. AWS PrivateLink for Amazon Bedrock — Private VPC connectivity.
  10. SageMaker Model Cards — Standardized model documentation.
  11. SageMaker Clarify — Bias detection and explainability.
  12. SageMaker Model Monitor — Production drift detection.
  13. SageMaker Automatic Model Tuning — Hyperparameter optimization.
  14. SageMaker Canvas — No-code ML.
  15. SageMaker JumpStart — Pre-trained models and templates.
  16. SageMaker Data Wrangler — Visual data preparation.
  17. SageMaker Ground Truth — Data labeling.
  18. AWS Audit Manager — Compliance evidence collection.
  19. AWS Config — Resource configuration and compliance.
  20. AWS CloudTrail — API activity logging.
  21. AWS CloudTrail Lake — Immutable, queryable audit store.
  22. Amazon Macie — Sensitive data discovery.
  23. Amazon Inspector — Vulnerability scanning.
  24. AWS Artifact — AWS compliance reports.
  25. Amazon Q Business — Enterprise AI assistant.
  26. Amazon Q Developer — Developer productivity.
  27. Amazon Nova — Multimodal foundation models.
  28. Amazon Nova Canvas — Image generation.
  29. Amazon Nova Reel — Video generation.
  30. AWS — What is RAG? — RAG explanation.
  31. AWS — What is Prompt Engineering? — Prompting techniques.
  32. AWS — What are Embeddings? — Embeddings explanation.
  33. AWS — What is Overfitting? — Overfitting explanation.
  34. AWS Responsible AI — Responsible AI dimensions and resources.
  35. AWS Well-Architected Machine Learning Lens — ML lifecycle phases.
  36. AWS CAF for AI — AI governance framework.
  37. AWS Data Residency — Data residency compliance.
  38. AWS Prescriptive Guidance — Common LLM Attacks — Prompt injection and jailbreak.
  39. Amazon Bedrock Prompt Management — Store and reuse prompts.
  40. Amazon Bedrock Provisioned Throughput — Dedicated capacity.
  41. Amazon Bedrock Batch Inference — Bulk generation.
Reference Verification

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.

Limited-time offer · ends in -- Days : -- Hrs : -- Min : -- Sec
Get Instant Access