AWS Certified AI Practitioner
Exam code AIF-C01. This single page holds two things: a fast high-level overview to orient you, and a thorough study guide covering every exam domain, AI/ML vocabulary, in-scope services, and community-recommended study materials. Overview items link straight into their deep-dive sections.
65 questions 90 minutes 700/1000 to pass $100 USD Valid 3 yearsPart 1 — High-Level Overview
What & Why
The AWS Certified AI Practitioner is AWS's foundational AI/ML credential. It validates that you understand AI, ML, and generative AI concepts and can identify appropriate AWS services for a given use case — not that you can build, train, or tune a model. Think of it as the Cloud Practitioner (CLF-C02) exam's sibling for the AI/ML domain: broad vocabulary and service-selection knowledge over deep technical implementation.
You are not expected to write training code, engineer features, tune hyperparameters, or build ML pipelines. You are expected to read a business scenario, recognize the underlying AI/ML concept, and pick the right AWS service or the right responsible-AI/security control.
Exam at a Glance
| Attribute | Value |
|---|---|
| Exam code | AIF-C01 |
| Level | Foundational |
| Questions | 65 total — 50 scored + 15 unscored (pretest, not identified) |
| Question types | Multiple choice, multiple response, ordering, and matching |
| Time | 90 minutes |
| Passing score | 700 out of 100–1000 (scaled, compensatory) |
| Cost | 100 USD |
| Delivery | Pearson VUE test center or online proctored |
| Validity | 3 years |
The 5 Domains
Applications of Foundation Models is the single biggest chunk — study prompt engineering, RAG, and FM customization tradeoffs hardest.
| Domain | What it tests | Deep dive |
|---|---|---|
| 1 · Fundamentals of AI/ML 20% | Core AI/ML terminology, use-case fit, and the AI/ML development lifecycle. | → §4 |
| 2 · Fundamentals of GenAI 24% | Tokens/embeddings/transformers, GenAI advantages & disadvantages, AWS GenAI infrastructure. | → §5 |
| 3 · Applications of FMs 28% | FM selection, RAG, prompt engineering, fine-tuning, and evaluation methods. | → §6 |
| 4 · Responsible AI 14% | Bias, fairness, transparency, explainability, and legal/environmental considerations. | → §7 |
| 5 · Security, Compliance & Governance 14% | Securing AI systems, and governance/compliance frameworks for AI. | → §8 |
Core Services Snapshot
If you master this shortlist you cover the majority of questions. Each links to its detailed treatment.
Generative AI
Amazon Bedrock (+ Guardrails, Knowledge Bases, Agents, AgentCore, Prompt Management), Amazon Nova, Amazon Q. → detailsML Platform
Amazon SageMaker AI (+ JumpStart, Clarify, Model Cards, Model Monitor, Ground Truth). → detailsAI Services (pre-built)
Comprehend, Rekognition, Textract, Transcribe, Translate, Polly, Lex, Personalize. → detailsResponsible AI & Governance
Bedrock Guardrails, SageMaker Clarify, AI Service Cards, Model Cards, Amazon A2I. → detailsSecurity
IAM, KMS, Macie, PrivateLink, Secrets Manager, Inspector, Artifact. → detailsSupporting Data/Compute
S3, EC2, Lambda, VPC, RDS/Aurora, OpenSearch Service (vector search), Glue. → detailsRecommended Materials (community consensus)
Synthesized from r/AWSCertifications pass write-ups and commonly recommended courses/practice exams for AIF-C01.
Study Plan (Quick Version)
Built on learning science — active recall + spaced repetition beat passive re-watching. This is a foundational exam, so the plan is short — don't over-pad it.
- Week 1: Watch a full video course. After each domain, close the notes and recall it; make flashcards for every service and vocabulary term that's new to you.
- Week 2: Deep-dive Domain 3 (28%, the biggest) and Domain 2 (24%) — together over half the exam. Teach RAG, prompt engineering, and fine-tuning tradeoffs out loud (Feynman).
- Week 3: Practice exams in review mode, interleaved across domains; study every wrong answer's explanation and turn misses into flashcards. Repeat to consistent 80%+.
- Final days: AWS Skill Builder's free official practice questions, skim the in-scope/out-of-scope service lists and the Cram Jam, sleep well.
→ Detailed retention-based plan (§13) · ⚡ Cram Jam one-pager · → Exam-day tips & traps (§14)
Part 2 — Thorough Study Guide
1 · Exam Details & Logistics
AIF-C01 "validates a candidate's ability to explain and understand key concepts of AI, ML, and generative AI including relevant AWS services and tools." It is a scenario-light, terminology-heavy exam: recognize the term, recognize the right service, move on.
Scoring mechanics
- 65 questions, only 50 are scored. The other 15 are unscored "pretest" items AWS is trialing — they are not marked, so treat every question as if it counts.
- Scaled score 100–1000, pass at 700. It is compensatory: you do not need to pass each domain individually, only the overall exam. A strong domain can offset a weak one.
- No penalty for guessing — never leave a question blank. Unanswered = incorrect.
Question types
| Type | Format |
|---|---|
| Multiple choice | 1 correct answer among 4 options (3 distractors). |
| Multiple response | 2 or more correct answers among 5 or more options; all-or-nothing scoring — every correct option must be selected and no incorrect ones. |
| Ordering | Place 3–5 responses into the correct order (e.g. steps of the ML lifecycle). |
| Matching | Match a list of responses against 3–7 prompts; all pairs must be correct for credit. |
Target candidate
Up to 6 months of exposure to AI/ML technologies on AWS, in a business or technical role. Crucially, the candidate uses AI/ML solutions but does not necessarily build them. AWS recommends familiarity with core AWS services (Amazon EC2, Amazon S3, AWS Lambda, Amazon Bedrock, Amazon SageMaker AI), the shared responsibility model, IAM, and AWS pricing models before attempting the exam.
Logistics
| Item | Detail |
|---|---|
| Price | 100 USD (plus local taxes / FX). |
| Delivery | Pearson VUE testing center, or online proctored from home (quiet private room, webcam, ID check). |
| Recertification | Valid 3 years. Recertify by re-passing the current exam version. |
2 · AI/ML Vocabulary Primer
This exam is heavily terminology-driven, and many candidates are new to ML. Get these contrasts solid before the domain deep-dives — most questions are really testing whether you can tell two adjacent terms apart.
AI vs ML vs deep learning vs GenAI vs agentic AI
| Term | Definition |
|---|---|
| Artificial Intelligence (AI) | The broadest field: building systems that perform tasks normally requiring human intelligence. |
| Machine Learning (ML) | A subset of AI: systems that learn patterns from data rather than being explicitly programmed with rules. |
| Deep Learning | A subset of ML using multi-layer neural networks; powers computer vision, NLP, and foundation models. |
| Generative AI (GenAI) | A subset of deep learning: models that generate new content (text, image, audio, video, code) rather than just classify or predict, typically built on foundation models (FMs) and large language models (LLMs). |
| Agentic AI | Systems where an AI agent plans, uses tools, and takes multi-step actions toward a goal with limited human intervention, rather than producing a single response to a single prompt. |
Supervised vs unsupervised vs reinforcement learning
| Type | Data | Goal | Example |
|---|---|---|---|
| Supervised learning | Labeled data (input + known correct output) | Learn a mapping from input to output | Classification, regression |
| Unsupervised learning | Unlabeled data | Find structure/patterns without a target answer | Clustering, anomaly detection, dimensionality reduction |
| Reinforcement learning | An agent, an environment, and a reward signal | Learn a policy that maximizes cumulative reward through trial and error | Game-playing agents, RLHF (reinforcement learning from human feedback) used to align LLMs |
Classification vs regression vs clustering
| Technique | Learning type | Output | Example |
|---|---|---|---|
| Classification | Supervised | A discrete category/label | Spam vs not-spam, fraud vs legitimate |
| Regression | Supervised | A continuous numeric value | Predicting house price, forecasting demand |
| Clustering | Unsupervised | Groups of similar items, no predefined labels | Customer segmentation |
Training vs inference
- Training — the process of learning model parameters from data. Happens once (or periodically for re-training), is compute-intensive, and is largely out of scope for this exam beyond recognizing the concept.
- Inference — using a trained model to make a prediction/generate output on new input. This is what candidates actually configure and pay for day to day.
| Inference type | Characteristics | Use when |
|---|---|---|
| Real-time | Low-latency, persistent endpoint, always-on cost | Interactive apps, chatbots, fraud checks at transaction time |
| Batch | Large volume processed together, no live endpoint needed | Nightly scoring of a whole dataset |
| Asynchronous | Queue-based; request submitted, result retrieved later | Large payloads or long-running inference where the caller doesn't need to block |
| Serverless | Auto-scales (including to zero), pay only for what you use | Intermittent or unpredictable traffic; avoid managing/paying for idle capacity |
Labeled vs unlabeled, and data modalities
| Concept | Meaning |
|---|---|
| Labeled data | Each example has a known, correct output attached — required for supervised learning. |
| Unlabeled data | No attached output — used for unsupervised learning or as raw pre-training corpus for FMs. |
| Structured data | Fits neatly into rows/columns (tabular) — e.g. a database table. |
| Unstructured data | No fixed schema — text, images, audio, video. |
| Time-series data | Ordered by time, e.g. sensor readings, stock prices — used for forecasting. |
Bias, fairness, and model fit
| Term | Meaning |
|---|---|
| Bias | Systematic error — a model that consistently favors or disfavors certain outcomes or groups, often inherited from unrepresentative training data. |
| Fairness | The property of a model treating different groups equitably; measured and improved using tools like SageMaker Clarify. |
| Overfitting | The model memorizes training data (including its noise) and performs poorly on new, unseen data — high variance. |
| Underfitting | The model is too simple to capture the underlying pattern — performs poorly on both training and new data — high bias in the statistical sense. |
GenAI-specific vocabulary
| Term | Meaning |
|---|---|
| Token | The basic unit of text an LLM processes (roughly a word or word-piece); pricing and context limits are measured in tokens. |
| Chunking | Splitting a large document into smaller pieces before embedding, so retrieval returns relevant, appropriately-sized context. |
| Embedding | A numeric vector representation of text/image/audio capturing semantic meaning — similar meanings land close together in vector space. |
| Vector database | A database optimized to store embeddings and perform fast similarity search (nearest-neighbor search). |
| Foundation model (FM) | A large model pre-trained on broad data that can be adapted to many downstream tasks. |
| Large language model (LLM) | A foundation model specialized for text — the most common FM type discussed on the exam. |
| Multi-modal model | A model that accepts and/or generates more than one data type (e.g. text + image). |
| Diffusion model | A generative model architecture (commonly used for image generation) that learns to reverse a noise-adding process. |
| Transformer | The neural network architecture (self-attention based) underlying most modern LLMs. |
| Context window | The maximum amount of input + output text (in tokens) a model can consider at once. |
| Hallucination | Confident but factually incorrect or fabricated model output. |
| Grounding | Anchoring model output to verifiable source data (e.g. via RAG) to reduce hallucination. |
3 · In-Scope & Out-of-Scope AWS Services
AWS publishes explicit in-scope and out-of-scope service lists for AIF-C01. No other guide in this repo has an out-of-scope list — it is genuinely useful because it tells you exactly which services you can stop worrying about, even if they sound AI-adjacent.
In-scope services by category
| Category | Services |
|---|---|
| Machine Learning | Amazon Bedrock, Amazon Bedrock AgentCore, Amazon Comprehend, Amazon Lex, Amazon Nova, Amazon Personalize, Amazon Polly, Amazon Rekognition, Amazon SageMaker AI, Amazon SageMaker JumpStart, Amazon Textract, Amazon Transcribe, Amazon Translate, AWS Transform |
| Security, Identity & Compliance | AWS Artifact, AWS IAM, Amazon Inspector, AWS KMS, Amazon Macie, AWS Secrets Manager |
| Management & Governance | AWS CloudTrail, Amazon CloudWatch, AWS Config, AWS Trusted Advisor, AWS Well-Architected Tool |
| Analytics | AWS Data Exchange, Amazon EMR, AWS Glue, AWS Glue DataBrew, AWS Lake Formation, Amazon OpenSearch Service, Amazon Quick, Amazon Redshift |
| Database | Amazon Aurora, Amazon DocumentDB, Amazon DynamoDB, Amazon ElastiCache, Amazon Neptune, Amazon RDS |
| Compute | Amazon EC2, AWS Lambda |
| Containers | Amazon ECS, Amazon EKS |
| Storage | Amazon S3, Amazon S3 Glacier |
| Networking & Content Delivery | Amazon CloudFront, Amazon VPC |
| Developer Tools | Kiro, Strands Agents |
| Cloud Financial Management | AWS Budgets, AWS Cost Explorer |
Out-of-scope services (selected — services that sound AI-related but aren't tested)
| Category | Services |
|---|---|
| Security, Identity & Compliance | ACM, CloudHSM, Amazon Cognito, Amazon Detective, Directory Service, Firewall Manager, GuardDuty, IAM Identity Center, Payment Cryptography, Private CA, RAM, Security Hub, Security Lake, Shield, Signer, Verified Permissions, WAF |
| Machine Learning | AWS DeepComposer, AWS HealthImaging, AWS HealthOmics, Amazon Monitron, AWS Panorama |
| Management & Governance | Control Tower, Health Dashboard, Launch Wizard, License Manager, Managed Grafana, Managed Service for Prometheus, OpsWorks, Organizations, Proton, Resilience Hub, Resource Explorer, Resource Groups, Systems Manager Incident Manager, Service Catalog, Service Quotas, Telco Network Builder, User Notifications |
| Developer Tools | AppConfig, Application Composer, CloudShell, CodeCatalyst, CodeStar, Fault Injection Service, X-Ray |
| Networking & Content Delivery | App Mesh, Cloud Map, Direct Connect, Global Accelerator, Private 5G, Route 53 (+ Application Recovery Controller), VPC IP Address Manager |
| Compute / Containers | App Runner, Elastic Beanstalk, EC2 Image Builder, Lightsail, Red Hat OpenShift Service on AWS (ROSA) |
| Storage / Database | AWS Backup, Elastic Disaster Recovery, Keyspaces, QLDB, Timestream |
| Analytics / Application Integration | Clean Rooms, CloudSearch, Amazon MSK, AppFlow, Amazon MQ, Simple Workflow Service |
| Other | Entire IoT family (IoT Core, Greengrass, SiteWise, etc.), Media Services (Elastic Transcoder, Elemental*, IVS), Migration & Transfer services (DMS, DataSync, Application Migration Service, etc.), End User Computing (WorkSpaces, AppStream), Frontend Web/Mobile (Amplify, Device Farm, Location Service), Business Applications (Chime, Pinpoint, SES, Wickr) |
Both lists are officially described as non-exhaustive and subject to change — treat them as the strongest available signal, not an exhaustive contract.
4 · Domain 1 — Fundamentals of AI and ML 20%
Three official task statements: (1.1) explain basic AI concepts and terminologies, (1.2) identify practical use cases for AI, and (1.3) describe the AI/ML development lifecycle.
4.1 · Basic AI Concepts & Terminology
Task 1.1 tests the vocabulary in §2 directly: AI, ML, deep learning, neural networks, computer vision, NLP, model, algorithm, training/inferencing, bias, fairness, fit, LLM, GenAI, agentic AI, and the differences between them. It also covers the types of inferencing (batch, real-time, asynchronous, serverless — see §2's table), the types of data (labeled/unlabeled, tabular, time-series, image, text, structured/unstructured), and the three learning paradigms (supervised, unsupervised, reinforcement).
4.2 · Practical Use Cases for AI
| When AI/ML adds value | Example |
|---|---|
| Assisting human decision-making | Fraud-risk scoring that a human reviewer still approves |
| Scaling a solution beyond manual capacity | Classifying millions of support tickets |
| Automating repetitive pattern-recognition work | Document data extraction, image tagging |
| When AI/ML is NOT appropriate | Why |
|---|---|
| The cost of building/operating the model exceeds the value it creates | Cost-benefit analysis fails |
| The business needs a guaranteed, deterministic outcome | ML produces probabilistic predictions, not certainties — e.g. don't use ML where a fixed business rule is required |
| Use case | Technique / service |
|---|---|
| Predict a category (spam/not-spam, fraud/legit) | Classification |
| Predict a number (price, demand) | Regression |
| Group similar items with no labels | Clustering |
| Understand image content | Computer vision — Amazon Rekognition |
| Understand/generate language | NLP — Amazon Comprehend, Bedrock LLMs |
| Convert speech to text | Amazon Transcribe |
| Convert text to speech | Amazon Polly |
| Recommend products/content | Amazon Personalize |
| Build a conversational chatbot | Amazon Lex |
| Extract text/data from documents | Amazon Textract |
| Translate between languages | Amazon Translate |
| End-to-end ML build/train/deploy | Amazon SageMaker AI |
4.3 · AI/ML Development Lifecycle
| Stage | What happens |
|---|---|
| Business goal identification | Define the problem and success criteria before touching data or models. |
| Data collection & preparation | Gather, clean, and label data (out of scope to perform yourself, but recognize it as a lifecycle stage). |
| Model selection | Choose an algorithm, a pre-trained open-source model, or a foundation model. |
| Training | Fit the model to data (custom training) — or skip this by using a pre-trained/foundation model. |
| Evaluation | Measure performance against metrics before deployment. |
| Deployment | Serve the model — via a managed API service (e.g. a Bedrock/SageMaker endpoint) or self-hosted (e.g. on EC2/containers). |
| Monitoring & re-training | Watch for drift/degraded performance in production; retrain as needed. |
MLOps concepts
MLOps applies DevOps discipline to ML: experimentation, repeatable processes, scalable systems, managing technical debt, achieving production readiness, model monitoring, and model re-training. On this exam, know the concept exists and what it aims to solve — not how to implement a pipeline (that's explicitly out of scope).
Evaluating models: performance vs business metrics
| Metric type | Examples |
|---|---|
| Model performance | Accuracy, precision, recall, F1 score |
| Business | Cost per user, development costs, customer feedback, return on investment (ROI) |
5 · Domain 2 — Fundamentals of GenAI 24%
Three official task statements: (2.1) explain the basic concepts of GenAI, (2.2) understand GenAI's capabilities and limitations for business problems, and (2.3) describe AWS infrastructure and technologies for building GenAI applications.
5.1 · Basic GenAI Concepts
Task 2.1 covers tokens, chunking, embeddings, vectors, prompt engineering, transformer-based LLMs, FMs, multi-modal models, and diffusion models (all defined in §2), plus the following.
| GenAI use case | Example |
|---|---|
| Content generation | Image, video, audio generation |
| Summarization | Condensing long documents/meeting transcripts |
| AI assistants & customer service agents | Conversational support, internal knowledge assistants |
| Translation & code generation | Language translation, code completion/generation |
| Search & recommendation | Semantic search, personalized recommendations |
The FM lifecycle
Data selection → model selection → pre-training → fine-tuning → evaluation → deployment → feedback. See §6.3 for the fine-tuning methods themselves.
Token-based pricing
Most FM APIs (including Bedrock) charge per token, counting both input and output tokens. Longer prompts and longer responses cost more and take longer to generate — this is why prompt length, output length, and prompt caching (reusing a cached, already-processed prompt prefix to cut cost/latency on repeated calls) matter for both cost and performance.
Context engineering
The practice of deliberately constructing what an FM sees at inference time — retrieved documents, conversation history, tool outputs, system instructions — rather than relying on the prompt text alone. It is the broader discipline that prompt engineering (§6.2) and RAG (§6.1) are both techniques within.
Agentic AI concepts
| Concept | Meaning |
|---|---|
| Multi-agent system patterns | Multiple specialized agents collaborating (e.g. a planner agent delegating to tool-using worker agents) rather than one monolithic prompt. |
| Model Context Protocol (MCP) | A standard protocol connecting agents to external tools/systems/data sources in a consistent way. |
| Multi-agent communication patterns | How agents pass messages/results between each other. |
| Memory management | How an agent retains context across turns/sessions (short-term vs long-term memory). |
| Tool usage | An agent invoking external functions/APIs to take action or fetch information. |
| Workflow orchestration | Coordinating multi-step agent tasks, retries, and branching logic. |
5.2 · Capabilities & Limitations
| Advantage | What it means |
|---|---|
| Adaptability | One FM handles many tasks without task-specific training. |
| Responsiveness | Fast, interactive generation for real-time use cases. |
| Conversational capability | Multi-turn, natural-language interaction. |
| Content generation | Produces novel text/image/audio/video/code output. |
| Disadvantage | What it means |
|---|---|
| Hallucination | Confident but fabricated/incorrect output. |
| Interpretability | Hard to explain exactly why an FM produced a given output. |
| Inaccuracy | Output may simply be wrong, especially outside the training data's coverage. |
| Nondeterminism | The same prompt can produce different outputs on different runs. |
Factors when selecting a GenAI model
Model type, performance requirements, capabilities, constraints, compliance, cost, latency, and model complexity. See §6.1 for the full FM-selection criteria list.
Business value & metrics for GenAI applications
| Metric | What it measures |
|---|---|
| Cross-domain performance | Consistency of quality across different topics/use cases |
| ROI | Value generated vs cost to build/run |
| Efficiency | Resources/time consumed per unit of output |
| Conversion rate | Business outcome driven by the application (e.g. purchases) |
| Average revenue per user (ARPU) | Revenue impact per user |
| Accuracy | Correctness of generated output against ground truth |
| Customer lifetime value | Long-term value of retained/satisfied customers |
5.3 · AWS Infrastructure for GenAI
| Service/feature | Role |
|---|---|
| Amazon Bedrock | Managed access to multiple FMs (Amazon Nova, Anthropic Claude, Meta Llama, and others) through one API — no infrastructure to manage. |
| Amazon SageMaker AI / SageMaker JumpStart | Build/train/deploy custom models, or deploy pre-built/open-source foundation models with a few clicks. |
| Amazon Quick | AWS's business-user-facing AI/analytics assistant experience. |
| Kiro | Agentic AI IDE/development experience. |
| Strands Agents | A framework/SDK for building AI agents. |
| Amazon Bedrock AgentCore | Infrastructure and identity/tooling for running agents built with Bedrock or open-source frameworks at scale. |
Why build GenAI apps on AWS
- Accessibility & lower barrier to entry — no need to train an FM from scratch.
- Efficiency & cost-effectiveness — pay only for what's used; no idle GPU clusters to manage.
- Speed to market — managed APIs let teams ship faster.
- Security, compliance, responsibility, safety — inherits AWS's compliance posture and Bedrock's built-in responsible-AI tooling (Guardrails).
Cost tradeoffs of AWS GenAI services
Responsiveness, availability, redundancy, performance, regional coverage, token-based pricing vs provisioned throughput (reserved capacity for predictable, high-volume workloads at a flat rate instead of per-token), and the added cost of custom models (fine-tuning/continued pre-training) versus using a base FM as-is.
6 · Domain 3 — Applications of Foundation Models 28%
The largest domain. Four task statements: (3.1) design considerations for FM applications, (3.2) effective prompt engineering, (3.3) training and fine-tuning FMs, and (3.4) methods to evaluate FM performance.
6.1 · FM Application Design
Selection criteria for choosing an FM
| Criterion | Consideration |
|---|---|
| Cost | Per-token pricing varies widely by model size/provider. |
| Modality | Text-only vs multi-modal (image/audio/video in or out). |
| Latency | Real-time chat needs fast, often smaller, models. |
| Multi-lingual support | Not every model performs equally across languages. |
| Model size & complexity | Bigger isn't always better — smaller models can be cheaper/faster for narrow tasks. |
| Customization | Does it support fine-tuning / continued pre-training? |
| Input/output length | Context window size limits how much you can feed in or get back. |
| Prompt caching | Support for caching repeated prompt prefixes to cut cost/latency. |
Inference parameters
| Parameter | Effect |
|---|---|
| Temperature | Controls randomness. Low (near 0) → deterministic, focused output. High → more creative/varied, less predictable output. |
| Top-p / Top-k | Restrict sampling to the most probable next-token candidates, trading diversity for coherence. |
| Input/output length | Longer inputs consume more of the context window and cost more tokens; capping output length controls cost and runaway generations. |
Retrieval Augmented Generation (RAG)
RAG retrieves relevant external data (via a vector similarity search) and injects it into the prompt at inference time, so the FM generates an answer grounded in that retrieved data instead of relying solely on what it memorized during training. Amazon Bedrock Knowledge Bases is the managed AWS implementation: it handles chunking, embedding, vector storage, and retrieval automatically.
| Business benefit of RAG | Why |
|---|---|
| Reduces hallucination | Answers are grounded in retrieved, verifiable source documents. |
| Keeps answers current | No need to retrain/fine-tune the FM every time source data changes — just update the knowledge base. |
| Cheaper than fine-tuning | No training job required to incorporate new domain knowledge. |
Vector database options on AWS
| Service | Vector capability |
|---|---|
| Amazon OpenSearch Service | Native vector search (k-NN) engine; a common Bedrock Knowledge Bases backend. |
| Amazon Aurora (PostgreSQL-compatible) | pgvector extension for embedding storage/search. |
| Amazon Neptune | Graph database with vector search support for graph-augmented retrieval. |
| Amazon RDS for PostgreSQL | pgvector extension, same idea as Aurora PostgreSQL. |
FM customization approaches — cost tradeoffs
| Approach | Relative cost/effort | What it does |
|---|---|---|
| Pre-training | Highest | Train a model from scratch on your own corpus. Almost never the exam's correct answer — extremely expensive. |
| Fine-tuning | High | Further train an existing FM on your labeled data to specialize it. |
| Continued pre-training | Medium-high | Further train on unlabeled domain data to adapt the model's general knowledge without task-specific labels. |
| RAG | Low-medium | No model weights change; inject retrieved context at inference time. |
| In-context learning / prompt engineering | Lowest | No training at all — just craft the prompt (zero/few-shot examples). |
| Model distillation | Medium | Train a smaller "student" model to mimic a larger "teacher" model's behavior, for cheaper/faster inference. |
AI agents
An AI agent uses an FM to reason about a task, decide which tools to call (APIs, retrieval, code execution), and take multi-step action toward a goal — rather than producing one static response. Business applications: automating multi-step workflows (e.g. booking a trip, resolving a support ticket end-to-end) that a single prompt-response can't handle.
6.2 · Prompt Engineering
| Concept/construct | Meaning |
|---|---|
| Context | Background information given to the model to ground its response. |
| Instruction | The explicit task/command given to the model. |
| Negative prompt | Tells the model what to avoid generating (common in image generation). |
| Technique | Description |
|---|---|
| Zero-shot | No examples given — the model relies purely on its pre-trained knowledge. |
| Single-shot / one-shot | Exactly one example given in the prompt. |
| Few-shot | Multiple examples given, to demonstrate the desired pattern/format. |
| Chain-of-thought (CoT) | Prompt the model to reason step by step before answering, improving accuracy on complex/multi-step problems. |
| Prompt templates | Reusable prompt structures with variable slots, for consistency across many calls. |
Benefits & best practices
Response-quality improvement, structured experimentation, layering in guardrails, discovery of model capabilities, specificity and concision in instructions, and using multiple comments/sections to organize a complex prompt.
Prompt risks
| Risk | Meaning |
|---|---|
| Prompt exposure | Leaking the system prompt or proprietary prompt engineering to an end user. |
| Prompt poisoning | Injecting malicious content into training/retrieval data to corrupt future outputs. |
| Prompt hijacking | An attacker's input redirects the model away from its intended task. |
| Jailbreaking | Crafting input specifically to bypass the model's safety guardrails/restrictions. |
Prompt versioning & management
Amazon Bedrock Prompt Management lets teams create, version, test, and share prompt templates across an organization — the answer to "manage and track changes to prompts used in production" questions.
6.3 · Training & Fine-Tuning
| Term | Meaning |
|---|---|
| Pre-training | Initial training of an FM from scratch on a massive, broad dataset. |
| Fine-tuning | Further training a pre-trained FM on a smaller, labeled, task/domain-specific dataset. |
| Continuous pre-training | Further training on additional unlabeled domain data, without task-specific labels. |
| Distillation | Training a smaller model to replicate a larger model's outputs/behavior. |
Fine-tuning methods
- Instruction tuning — fine-tune on (instruction, response) pairs so the model follows directions better.
- Domain adaptation — specialize the model's language/knowledge for a specific industry or subject.
- Transfer learning — reuse a model trained on one task as the starting point for a related task.
- Continuous pre-training — as above, adapting general knowledge without labeled examples.
Preparing data to fine-tune
Data curation (selecting quality examples), governance (tracking provenance/consent), size (enough examples to move the model without overfitting), labeling (accuracy of the target outputs), representativeness (covering the range of real inputs), and RLHF (reinforcement learning from human feedback — humans rank model outputs, and that signal trains a reward model used to further align the FM).
6.4 · Evaluating FM Performance
| Evaluation approach | Description |
|---|---|
| Human-in-the-loop evaluation | People review/score model outputs directly — highest quality signal, most expensive/slowest. |
| Benchmark datasets | Standardized test sets used to compare models objectively. |
| Amazon Bedrock Model Evaluation | Managed tooling to run automatic or human evaluation jobs against candidate models directly in Bedrock. |
| LLM-as-a-judge | Using another (often larger/more capable) LLM to score a model's outputs — faster and cheaper than human review, though less authoritative. |
Metrics for FM performance
| Metric | Used for |
|---|---|
| ROUGE (Recall-Oriented Understudy for Gisting Evaluation) | Summarization quality — overlap between generated and reference summaries. |
| BLEU (Bilingual Evaluation Understudy) | Translation quality — n-gram overlap with reference translations. |
| BERTScore | Semantic similarity between generated and reference text using contextual embeddings, more meaning-aware than raw n-gram overlap. |
| Perplexity | How well a language model predicts a sample — lower is generally better (a classical LM fluency metric). |
| Human evaluation | Direct human judgment of quality/usefulness. |
Evaluating FM-based applications and business alignment
Beyond the base model, evaluate the whole application: RAG pipelines (retrieval relevance + generation quality), agents (task completion, tool-call correctness), and workflows (end-to-end success rate). Business-alignment metrics include task completion rate, user satisfaction, and cost per interaction — and whether the FM meets objectives like productivity or user engagement.
7 · Domain 4 — Guidelines for Responsible AI 14%
Two official task statements: (4.1) explain the development of responsible AI systems, and (4.2) recognize the importance of transparent and explainable models.
7.1 · Developing Responsible AI Systems
| Feature of responsible AI | Meaning |
|---|---|
| Bias / Fairness | Treating groups equitably; avoiding systematic disadvantage. |
| Inclusivity | Designing for a broad range of users and use cases. |
| Robustness | Performing reliably under varied/adversarial conditions. |
| Safety | Avoiding harmful outputs or actions. |
| Veracity | Truthfulness/accuracy of output — the opposite of hallucination. |
Amazon Bedrock Guardrails is the named tool for identifying/enforcing these features in production: content filters, denied topics, word filters, sensitive-information filters, and contextual grounding checks — see §10 for the full breakdown.
Responsible model selection
Consider environmental impact and sustainability — larger models consume more energy per inference; choosing an appropriately-sized model for the task is itself a responsible-AI decision, not just a cost one.
Legal risks of GenAI
- Intellectual property infringement claims — generated content resembling copyrighted training data.
- Biased model outputs — discriminatory or unfair results creating legal/reputational exposure.
- Loss of customer trust — from visible failures (hallucinations, bias, unsafe output).
- End-user risk and hallucinations — users acting on fabricated/incorrect information.
Dataset characteristics that reduce bias
Inclusivity, diversity, curated data sources, and balanced datasets (no group over/under-represented) — poor data on any of these dimensions is the most common root cause of a biased model.
Bias vs variance effects
| Problem | Effect |
|---|---|
| Bias (demographic) | Systematically worse outcomes for specific groups. |
| Overfitting (high variance) | Great on training data, poor generalization to new/real data. |
| Underfitting (high statistical bias) | Poor performance everywhere — the model never learned the pattern. |
Tools to detect and monitor bias, trustworthiness, and truthfulness
Analyzing label quality, human audits, and subgroup analysis (comparing model performance across demographic slices) — conceptually; Amazon SageMaker Clarify is the AWS tool that operationalizes this. See §10.
7.2 · Transparent & Explainable Models
| Transparent & explainable | Not transparent/explainable ("black box") | |
|---|---|---|
| Example | Linear/logistic regression, decision trees | Deep neural networks, large FMs |
| Can you say why it made a decision? | Yes, directly from model structure | Difficult — requires post-hoc explainability tooling |
| Typical tradeoff | Often lower raw performance on complex tasks | Often higher performance, harder to audit/trust |
| Tool | Purpose |
|---|---|
| Amazon SageMaker Model Cards | Structured documentation of a model's intended use, training data, evaluation results, and limitations. |
| Amazon Bedrock Model Evaluations | Compare/evaluate FMs, including for responsible-AI dimensions. |
| Open-source models, data, and licensing | Openly published model weights/data/licenses increase transparency and independent auditability versus a fully closed model. |
Human-centered design for explainable AI
User-feedback mechanisms (letting users flag wrong/harmful output) and AI decision transparency (clearly communicating to users when they're interacting with AI and how a decision/output was produced) are the exam's named principles.
8 · Domain 5 — Security, Compliance, and Governance for AI Solutions 14%
Two official task statements: (5.1) explain methods to secure AI systems, and (5.2) recognize governance and compliance regulations for AI systems. Full deep dive in §11; this section maps the task statements to the exam guide's own objective language.
8.1 · Securing AI Systems
| AWS service/feature | Named for |
|---|---|
| IAM roles, policies, and permissions | Access control to Bedrock/SageMaker resources |
| Encryption | Data at rest and in transit |
| Amazon Macie | Discover sensitive data (PII) in S3 data used for AI |
| AWS PrivateLink | Keep inference/training traffic off the public internet |
| AWS shared responsibility model | Divides security duties between AWS and the customer |
| Amazon Bedrock AgentCore Identity / Policy in AgentCore | Identity and access control specifically for agentic workloads |
| Amazon Bedrock Guardrails | Runtime content/topic/PII filtering — see §10 |
Source citation & data lineage — documenting where training/grounding data came from (data cataloging, SageMaker Model Cards) so outputs can be traced back to their origin. Secure data engineering best practices: assessing data quality, privacy-enhancing technologies, data access control, data integrity. Security/privacy considerations: application security, threat detection, vulnerability management, infrastructure protection, prompt injection, encryption at rest/in transit, data leakage prevention, output filtering/validation, audit trail and logging for AI interactions, and toxicity. Hallucination detection & grounding: RAG grounding, output validation, and confidence scoring.
8.2 · Governance & Compliance
| AWS service | Role in AI governance |
|---|---|
| AWS Config | Track resource configuration/compliance over time. |
| Amazon Inspector | Automated vulnerability scanning. |
| AWS Artifact | Self-serve compliance reports (SOC, PCI, ISO). |
| AWS CloudTrail | Audit log of API calls, including model invocation. |
| AWS Trusted Advisor | Best-practice checks across cost, performance, security, fault tolerance. |
Data governance strategies: data lifecycles, logging, residency, monitoring/observation, retention. Governance process: policies, review cadence, review strategies, transparency standards, team training requirements, and named governance frameworks such as the Generative AI Security Scoping Matrix (AWS's framework for classifying a GenAI application's risk/ownership scope). See §11 for external regulatory frameworks (ISO 42001, NIST AI RMF, EU AI Act, GDPR).
9 · AWS AI/ML Service Reference
A category-organized reference of the in-scope AI/ML services, deeper than the domain sections above.
Amazon Bedrock — building block by building block
| Feature | What it does |
|---|---|
| Model access | Single API to multiple FM providers (Amazon Nova, Anthropic Claude, Meta Llama, Mistral, and others) without managing infrastructure. |
| Knowledge Bases | Managed RAG — handles chunking, embedding, vector storage, and retrieval automatically. |
| Agents / AgentCore | Build agents that plan, call tools/APIs, and take multi-step action; AgentCore adds identity, memory, and runtime infrastructure for scale. |
| Guardrails | Runtime safety controls — see §10 for full detail. |
| Prompt Management | Create, version, and share prompt templates. |
| Model Evaluation | Automatic or human evaluation jobs to compare candidate models. |
| Fine-tuning / continued pre-training | Customize a base FM on your own data directly within Bedrock. |
| Provisioned Throughput | Reserved inference capacity at a flat rate, for high-volume/predictable workloads instead of per-token pricing. |
Amazon SageMaker AI — the ML platform
| Feature | What it does |
|---|---|
| Studio / notebooks | Managed environment to build, train, and deploy custom ML models. |
| JumpStart | One-click access to pre-built/open-source and foundation models. |
| Clarify | Bias detection and feature-attribution explainability — see §10. |
| Model Cards | Structured model documentation (intended use, training data, evaluation, limitations). |
| Model Monitor | Detects data/quality drift in deployed model endpoints over time. |
| Ground Truth | Managed data labeling (with human labelers) to prepare training data. |
| Endpoints | Real-time or serverless inference hosting for a trained/deployed model. |
Pre-built AI services (no model-building required)
| Service | Purpose |
|---|---|
| Amazon Comprehend | NLP — sentiment, entities, key phrases, language detection, PII detection in text. |
| Amazon Rekognition | Image and video analysis — object/scene detection, facial analysis, content moderation. |
| Amazon Textract | Extract text, forms, and tables from scanned documents. |
| Amazon Transcribe | Speech-to-text. |
| Amazon Translate | Language translation. |
| Amazon Polly | Text-to-speech. |
| Amazon Lex | Conversational chatbot/voice-bot interfaces. |
| Amazon Personalize | Recommendation engines. |
| Amazon Nova | Amazon's own family of foundation models, available via Bedrock. |
| AWS Transform | AI-powered tooling to accelerate application/code modernization. |
Supporting infrastructure & data services
| Service | Role in an AI/ML architecture |
|---|---|
| Amazon S3 / S3 Glacier | Store training data, model artifacts, and archived data cost-effectively. |
| Amazon EC2 / AWS Lambda | Compute for self-hosted inference or event-driven pipeline steps. |
| Amazon ECS / EKS | Container orchestration for custom model-serving workloads. |
| Amazon VPC / CloudFront | Network isolation and content delivery for AI applications. |
| Aurora, DynamoDB, RDS, ElastiCache, DocumentDB, Neptune | Application data stores; several double as vector stores (§6.1). |
| AWS Glue / Glue DataBrew / EMR / Lake Formation | Data preparation and data lake tooling feeding ML pipelines. |
| Amazon OpenSearch Service | Vector search backend, commonly paired with Bedrock Knowledge Bases. |
| Amazon Redshift / Amazon Quick | Data warehousing and business-facing analytics/AI assistant experience. |
10 · Responsible AI Tooling & Evaluation Metrics
Documentation artifacts
| Artifact | Purpose |
|---|---|
| AWS AI Service Cards | AWS-published documentation of a specific AWS AI service's intended use cases, limitations, and responsible-AI design choices (e.g. a card for Rekognition). |
| Amazon SageMaker Model Cards | Documentation you create for your own trained/deployed models — intended use, training data, evaluation results, limitations. |
Bias detection & explainability
| Tool | What it does |
|---|---|
| Amazon SageMaker Clarify | Detects potential bias in training data and model predictions across demographic groups, and provides feature attribution (which input features drove a given prediction) for explainability. |
Amazon Bedrock Guardrails
| Guardrail component | What it filters/enforces |
|---|---|
| Content filters | Blocks harmful content categories (hate, violence, sexual content, etc.) at configurable strength. |
| Denied topics | Blocks a defined list of topics the application should never discuss. |
| Word filters | Blocks specific words/phrases (e.g. profanity, competitor names). |
| Sensitive-information filters | Detects/redacts PII in input or output. |
| Contextual grounding checks | Verifies a RAG response is actually grounded in the retrieved source content, flagging ungrounded (likely hallucinated) claims. |
Human review
Amazon Augmented AI (A2I) inserts a human review step into an ML workflow for low-confidence predictions or a required compliance checkpoint, before output is acted upon.
Evaluation metrics summary
| Domain | Metrics |
|---|---|
| Classical ML | Accuracy, precision, recall, F1 score, AUC-ROC |
| GenAI text quality | BLEU, ROUGE, BERTScore, perplexity, human evaluation |
| Business | User satisfaction, cross-domain performance, conversion rate, average revenue per user, efficiency, ROI, cost per interaction |
11 · Security, Compliance and Governance Deep Dive
Shared responsibility applied to AI
Identity & access
| Control | Use |
|---|---|
| IAM roles/policies | Grant least-privilege access to invoke Bedrock models, read/write SageMaker resources, or manage Knowledge Bases. |
| Resource-based policies | Control cross-account access to specific Bedrock/SageMaker resources. |
| Bedrock AgentCore Identity | Identity specifically scoped to agent runtime execution. |
Encryption
| State | Mechanism |
|---|---|
| At rest | AWS KMS-managed encryption for S3 training data, SageMaker storage volumes, and Bedrock resources. |
| In transit | TLS for API calls to Bedrock/SageMaker endpoints. |
Network isolation
VPC endpoints / AWS PrivateLink keep inference and training traffic off the public internet by routing it privately within the AWS network — the standard answer for "our AI workload must not traverse the internet."
Data protection & discovery
| Service | Role |
|---|---|
| Amazon Macie | Discover PII/sensitive data in S3 buckets used for training or RAG source data. |
| AWS Secrets Manager | Store credentials/API keys used by AI applications. |
| Data residency controls | Choosing which AWS Region processes/stores data to meet regulatory requirements. |
Auditing
AWS CloudTrail logs model-invocation API calls (who called which model, when) for audit trails. Source citation and documentation — tracing an output back to the data/model version that produced it — is itself a governance control, supported by Model Cards and data cataloging.
AI-specific threats
| Threat | Description |
|---|---|
| Prompt injection | Malicious instructions embedded in user input (or retrieved content) attempting to override the system prompt or extract sensitive data. |
| Jailbreaking | Crafted input designed to bypass a model's built-in safety restrictions. |
| Model/data poisoning | Corrupting training or RAG source data so the model learns or retrieves incorrect/malicious content. |
| Data leakage | Sensitive information from training data or context inadvertently surfacing in output. |
Governance & compliance frameworks
| Framework | What it is |
|---|---|
| ISO 42001 | International standard for an AI management system. |
| NIST AI RMF | U.S. NIST's AI Risk Management Framework. |
| EU AI Act | European Union regulation classifying and governing AI systems by risk level. |
| GDPR | EU data-protection regulation, relevant wherever AI systems process personal data. |
| AWS compliance tooling | Purpose |
|---|---|
| AWS Config | Continuous resource configuration/compliance tracking. |
| AWS Audit Manager | Continuously collect evidence for audits against a chosen framework. |
| AWS Artifact | On-demand access to AWS's own compliance reports and agreements. |
12 · Study Materials (Community)
Synthesized from r/AWSCertifications AIF-C01 pass write-ups and threads recommending practice-exam providers.
| Resource | Type | Notes |
|---|---|---|
| AWS Skill Builder — "Exam Prep Standard Course: AWS Certified AI Practitioner" | Free official course | AWS's own prep course; pairs with the free official practice question set on the same platform. |
| freeCodeCamp — "AWS Certified AI Practitioner (AIF-C01)" by Andrew Brown | Free video course (YouTube) | Full-length free course by an AWS Hero; repeatedly cited in pass write-ups as a solid free option. |
| Stephané Maarek — Udemy AIF-C01 course | Paid video course | Same instructor whose SAA-C03/SCS-C03 courses are the community favorites; cited directly in a September 2025 pass write-up. |
| Frank Kane — "Mastering AWS Certified AI Practitioner AIF-C01" | Paid video course | Named alongside Maarek's course in community roundups. |
| Tutorials Dojo — AIF-C01 Practice Exams | Paid practice exams | Same provider whose practice exams are the top recommendation for SAA-C03/SCS-C03; offers a free sampler. |
| AWS Skill Builder official practice exam | Free official practice questions | Directly from AWS; the closest approximation to real question style/difficulty. |
13 · Study Plan
This is a foundational exam — the plan below is intentionally short (about 3 weeks), unlike the 8-week plan appropriate for a Specialty exam. Don't pad it.
| Principle | Why it works | How to apply it here |
|---|---|---|
| Active recall | Retrieving information strengthens memory more than re-reading it. | After each domain, close the notes and write out the vocabulary/service list from memory before checking §2/§9. |
| Spaced repetition | Reviewing just before you'd forget cements long-term retention. | Flashcard every service-selection contrast (RAG vs fine-tuning, Guardrails vs Clarify) and review daily. |
| Interleaving | Mixing topics beats blocked practice for discrimination tasks. | Practice exams that mix all five domains, not one domain per session. |
| Elaboration / Feynman technique | Explaining why exposes gaps. | Talk through the FM-customization cost tradeoff table (§6.1) out loud from memory. |
| Hands-on practice | Doing beats watching. | Try a Bedrock model in the console, run a Knowledge Base query, and configure a Guardrail in a sandbox account. |
The weekly plan
| Phase | Focus | Actions |
|---|---|---|
| Week 1 Foundations | Domain 1 (20%) and Domain 2 (24%) — vocabulary and GenAI basics | Learn: first half of your video course. Retrieve: after each section, blank-page recall of §2's vocabulary tables; make flashcards. Apply: try Bedrock's model playground in a sandbox account. |
| Week 2 Domain 3 (28%, the biggest) + Domains 4/5 | Prompt engineering, RAG, fine-tuning tradeoffs, responsible AI, security | Learn: finish the course. Apply: stand up a Bedrock Knowledge Base against a small S3 document set; configure a Guardrail with a denied topic. Retrieve: daily flashcard review of Week 1 material. |
| Week 3 Practice & polish | Full practice exams in review mode, interleaved | Take Tutorials Dojo (or the AWS Skill Builder official set). Read every explanation, even for correct answers. Turn each miss into a flashcard. Retake until consistent 80%+. Final day: light flashcard review only, skim the Cram Jam, sleep well. |
14 · Exam-Day Tips & Traps
Technique
- Read the last sentence first. Identify what's actually being asked for — "least operational overhead," "without retraining," "grounded in company data." That qualifier decides between two plausible-sounding options.
- Watch for out-of-scope distractors. Any option that involves writing training code, tuning hyperparameters, or building a pipeline yourself is very likely wrong on this exam — reread §1's out-of-scope list.
- Flag & move on. 90 minutes / 65 questions ≈ 1.4 minutes each. Don't sink 5 minutes into one question — flag it and return later.
- Never leave a blank — there is no penalty for guessing.
- Watch multiple-response questions closely. They're all-or-nothing — selecting 3 of 2 correct answers scores zero, same as selecting 0.
Recurring traps
- GuardDuty, Security Hub, Shield, WAF are out of scope — despite sounding like "secure AI systems" answers, the exam's AI-security toolbox is IAM, KMS, Macie, PrivateLink, and Bedrock Guardrails.
- RAG vs fine-tuning — "use our own current documents without retraining" = RAG. "Teach the model our tone/format on many labeled examples" = fine-tuning.
- SageMaker Clarify (bias detection) vs Bedrock Guardrails (runtime content filtering) — Clarify analyzes training data/model predictions for bias; Guardrails filters live application input/output.
- Statistical bias (underfitting) vs responsible-AI bias (unfair treatment) — same word, different concept; read context.
- Precision/recall/F1/AUC-ROC are for classical ML; BLEU/ROUGE/BERTScore/perplexity are for GenAI text — don't cross-apply them.
- Training vs inference — the exam almost never expects you to configure training; it expects you to pick the right inference pattern (real-time, batch, async, serverless).
- Compensatory scoring — you don't need to pass Domain 3 specifically; an overall 700+ across all domains passes.
- Amazon Q / Amazon Quick / Kiro / Strands Agents are named AWS-branded tools in the objectives — recognize what each does at a glance rather than confusing them with generic "an AI agent."
15 · Glossary
A fast lookup table for acronyms and terms the exam guide and practice questions drop without expansion.
| Term | Meaning |
|---|---|
| A2I | Amazon Augmented AI (human review step) |
| ARPU | Average Revenue Per User |
| AUC-ROC | Area Under the Curve – Receiver Operating Characteristic |
| BLEU | Bilingual Evaluation Understudy |
| CoT | Chain-of-Thought (prompting) |
| F1 score | Harmonic mean of precision and recall |
| FM | Foundation Model |
| GenAI | Generative AI |
| KMS | Key Management Service |
| LLM | Large Language Model |
| MCP | Model Context Protocol |
| Term | Meaning |
|---|---|
| MLOps | Machine Learning Operations |
| NLP | Natural Language Processing |
| PII | Personally Identifiable Information |
| RAG | Retrieval Augmented Generation |
| RLHF | Reinforcement Learning from Human Feedback |
| ROI | Return on Investment |
| ROUGE | Recall-Oriented Understudy for Gisting Evaluation |
| RMF | Risk Management Framework (NIST AI RMF) |
| VPC | Virtual Private Cloud |
| WORM | Write Once, Read Many |
16 · Worked Example Questions
Ten scenario-style questions worked through the way you should approach the real exam: identify the optimization keyword, eliminate the wrong-service distractors, then pick between what's left.
Example 1 — Applications of Foundation Models
"A company wants its customer-support chatbot to answer questions using the company's internal knowledge-base documents, which change daily, without retraining the underlying model. Which approach best meets this requirement?"
- Eliminate: fine-tuning the model on the documents — requires a training job every time documents change, which fights "change daily."
- Eliminate: pre-training a new model — vastly disproportionate cost/effort for this use case.
- Correct: Retrieval Augmented Generation (RAG) via Amazon Bedrock Knowledge Bases — retrieves current documents at query time and grounds the response, with no retraining needed when documents change.
Example 2 — Fundamentals of GenAI
"A team notices their generative AI model sometimes produces confident, fluent answers that are factually incorrect and not supported by any source. What is this phenomenon called?"
- Eliminate: "nondeterminism" — describes output varying between runs, not fabricated content specifically.
- Eliminate: "bias" — describes systematic unfairness toward a group, not fabrication.
- Correct: hallucination — confident but incorrect/fabricated output, the defining limitation of generative models covered in Domain 2.
Example 3 — Fundamentals of AI and ML
"A retailer wants to group customers into segments based on purchasing behavior, with no predefined categories. Which ML approach fits?"
- Eliminate: classification — requires predefined labeled categories, which the scenario says don't exist.
- Eliminate: regression — predicts a continuous number, not a group assignment.
- Correct: clustering, an unsupervised learning technique that groups similar items without predefined labels — exactly "segment with no predefined categories."
Example 4 — Guidelines for Responsible AI
"A company wants to check whether its trained fraud-detection model performs equally well across different age groups before deploying it. Which AWS service should it use?"
- Eliminate: Amazon Bedrock Guardrails — filters live content/topics at inference time in GenAI applications; doesn't analyze a trained model's fairness across demographic subgroups.
- Eliminate: SageMaker Model Monitor — watches for data/quality drift after deployment, not pre-deployment subgroup bias analysis.
- Correct: Amazon SageMaker Clarify — purpose-built to detect bias in training data and model predictions across defined groups, plus explain feature attribution.
Example 5 — Security, Compliance and Governance
"An organization's AI application calls Amazon Bedrock from within a VPC and must ensure inference traffic never traverses the public internet. What should it configure?"
- Eliminate: AWS Shield — DDoS protection, unrelated to keeping traffic off the public internet, and explicitly out of scope for this exam.
- Eliminate: Amazon Macie — discovers sensitive data in S3, doesn't control network paths.
- Correct: a VPC interface endpoint (AWS PrivateLink) for Bedrock — keeps the API traffic on the AWS private network instead of routing over the internet.
Example 6 — Applications of Foundation Models
"A developer wants a generated response to be more focused and deterministic, with less creative variation between runs on the same prompt. Which inference parameter should they lower?"
- Eliminate: context window / input length — controls how much text fits in a prompt, not output randomness.
- Eliminate: token count limit — caps response length, not its variability.
- Correct: temperature — lowering it makes output more deterministic and focused; raising it increases creativity/variation.
Example 7 — Fundamentals of GenAI
"A company is comparing two Bedrock-hosted foundation models for a chat application and wants to reduce cost on repeated calls that reuse the same long system prompt. Which capability should it use?"
- Eliminate: fine-tuning — solves a customization problem, not a per-call cost/latency problem for a repeated prompt prefix.
- Eliminate: reducing the context window — not a capability the developer chooses per-call; it's a fixed model property.
- Correct: prompt caching — reuses the already-processed portion of a repeated prompt prefix, cutting token cost and latency on subsequent calls.
Example 8 — Guidelines for Responsible AI
"A model performs very well on its training data but poorly on new, unseen data in production. What is this called, and what underlying problem does it indicate?"
- Eliminate: underfitting — describes poor performance on both training and new data, the opposite pattern.
- Eliminate: demographic bias — describes unequal treatment of groups, not a training/generalization gap.
- Correct: overfitting (high variance) — the model memorized training data, including its noise, and failed to generalize.
Example 9 — Security, Compliance and Governance
"A security team is worried an attacker could embed hidden instructions inside a document that gets retrieved by their RAG application, causing the model to ignore its original instructions. What is this attack called?"
- Eliminate: model poisoning — corrupts training data itself, a different (though related) attack than manipulating retrieved content at inference time.
- Eliminate: data leakage — describes sensitive information surfacing in output, not an attacker's instructions being followed.
- Correct: prompt injection — malicious instructions embedded in input (including retrieved RAG content) attempting to override the system prompt.
Example 10 — Fundamentals of AI and ML
"A company needs to score a very large historical dataset overnight, with no requirement for a live, always-on endpoint. Which inference type minimizes cost?"
- Eliminate: real-time inference — requires a persistent endpoint incurring cost even when idle, unnecessary for an overnight job.
- Eliminate: asynchronous inference — designed for large individual payloads processed one at a time via a queue, not the most efficient fit for scoring an entire large dataset together.
- Correct: batch inference — processes the whole dataset together with no live endpoint required, minimizing cost for exactly this offline, non-interactive use case.