AWS Certified Generative AI Developer – Professional (AIP-C01) study guide
What the AIP-C01 exam tests, domain by domain, and how to tell the right answer from the nearly right one. Each topic links to fuller study notes and free practice questions.
Last checked against the official exam guide and AWS documentation · How we write our content
About the AIP-C01 exam
The AWS Certified Generative AI Developer – Professional exam checks whether you can put foundation models into real applications on AWS: retrieval-augmented generation (RAG) over company data, agents that call tools, prompts that stay consistent, safety and privacy controls, and the monitoring, cost tuning and evaluation that production needs. AWS aims it at people with 2 or more years of building production applications on AWS or with open-source tools, general AI/ML or data engineering experience, and 1 year of hands-on generative AI work.
It is a developer exam, not a data science one. AWS lists model development and training, advanced ML techniques, and data and feature engineering as out of scope. You need to know how to choose, call, ground, guard, scale and test models, not how to build them.
| Questions | 75: 65 scored and 10 unscored, which aren’t marked |
| Time | 180 minutes |
| Question types | Multiple choice (one answer from four) and multiple response (two or more from five or more) |
| Score | Scaled from 100 to 1,000; 750 to pass |
| Scoring model | Compensatory: you need to pass overall, not in each domain |
| Guessing | An unanswered question counts as wrong, and there is no penalty for a wrong answer, so answer everything |
Check the official certification page for the current price, languages and booking options before you book.
What the exam really tests
Questions describe a team, an application and a set of requirements, then offer four answers that all sound reasonable. The best answer meets every requirement, including the qualifier, using managed features rather than custom code. A few themes run through the whole exam:
- Ground answers in your data. Knowledge bases, vector stores, chunking, embeddings, metadata filters, hybrid search and reranking.
- Build agents safely. Tools and MCP, Amazon Bedrock AgentCore, memory, stopping conditions, scoped permissions and human approval.
- Guard every request. Amazon Bedrock Guardrails, prompt injection defenses, PII protection, grounding checks and audit logging.
- Spend tokens wisely. Smaller models for simple work, prompt caching, batch inference, service tiers and cross-Region inference.
- Measure quality. Bedrock evaluations, LLM-as-a-judge, RAG and agent evaluations, quality gates and troubleshooting.
Services that changed after the exam guide was written
The exam guide was published before several AWS changes in 2026, and some services it names now take no new customers. Our questions follow AWS’s current recommendations, because a real project starting today couldn’t use the closed services:
| In the exam guide | Status since July 30, 2026 | Use instead for new work |
|---|---|---|
| Amazon Bedrock Agents (now Agents Classic) | Closed to new customers | Amazon Bedrock AgentCore with a framework such as Strands Agents |
| Amazon Kendra | Closed to new customers | Amazon Bedrock Knowledge Bases, including the fully managed knowledge base |
| Amazon Q Business | Closed to new customers | Amazon Quick |
| SageMaker AI Clarify, Model Monitor, Ground Truth and Augmented AI | Closed to new customers | Amazon Bedrock evaluations, AgentCore Evaluations, CloudWatch, and Step Functions for human review |
Amazon Bedrock Prompt Flows is now called Amazon Bedrock Flows. The real exam may still mention the older names, so recognize them, but don’t pick a closed service for a new build when a current one fits.
How to read a question
- Read the last sentence first to find the qualifier: least operational overhead, most cost-effective, lowest latency, most secure, fewest code changes.
- List the hard constraints: data residency, latency, budget, who may see which documents, how fresh the data must be, existing tools.
- Eliminate answers that build custom code where a managed feature exists, send data where it may not go, or solve a different problem (fine-tuning to add fresh facts, for example).
- Between the last two, pick the one that meets every requirement with the fewest moving parts.
Pace yourself: 180 minutes for 75 questions is about 2 minutes 24 seconds each. Flag long scenarios and come back.
How the domains add up
Foundation Model Integration, Data Management, and Compliance is the largest domain at 31%, followed by Implementation and Integration at 26%. Together they are more than half the exam, so RAG, prompts and agents deserve most of your time. AI Safety, Security, and Governance is 20%, Operational Efficiency and Optimization 12%, and Testing, Validation, and Troubleshooting 11%. The domains overlap: a troubleshooting question often turns on chunking, and a cost question on model choice.
Domain 1: Foundation Model Integration, Data Management, and Compliance 31%
The largest domain, at 31% of scored content. It covers designing generative AI solutions and proofs of concept, choosing foundation models and switching between them without code changes, staying available through cross-Region inference and fallbacks, fine-tuned models and their lifecycle, validating and preparing text, image, audio and tabular data, vector stores and metadata, keeping a knowledge base in sync with its sources, chunking, embeddings, hybrid search and reranking, query rewriting, exposing retrieval as a tool, and managing, testing and chaining prompts.
GenAI solution design, proofs of concept and the Well-Architected Generative AI Lens
Pick a GenAI architecture from business constraints: prompting, RAG, fine-tuning or an agent, plus an integration pattern. Know how to scope a Bedrock proof of concept that measures quality, latency and cost, and how the Well-Architected Generative AI Lens guides the review.
Study notes and 2 free questions on GenAI solution design, proofs of concept and the Well-Architected Generative AI LensChoosing foundation models for a use case
Choose a foundation model by matching the use case to context window, modality, language, tool use and structured output, then benchmark the finalists on your own data. Know how Region availability and Legacy lifecycle status can rule a model out before any quality comparison starts.
Study notes and 1 free question on Choosing foundation models for a use caseSwitching models and providers without code changes (AppConfig, gateways, inference profiles)
Switch models without a code release by keeping the model ID in configuration, calling one request shape through the Converse API, and tracking cost with application inference profiles. Know how AppConfig gradual rollouts with CloudWatch alarm monitors make a model change safe and reversible.
Study notes and 1 free question on Switching models and providers without code changes (AppConfig, gateways, inference profiles)Cross-Region inference and resilient model access
Keep a GenAI application available while respecting data residency, using geographic or global cross-Region inference, retries with backoff, a fallback model and graceful degradation. Know how throttling, Regional model availability and Step Functions Retry and Catch combine into one resilient design.
Study notes and 1 free question on Cross-Region inference and resilient model accessFine-tuning, LoRA adapters and custom model lifecycle (Bedrock, SageMaker AI, Model Registry)
Decide when fine-tuning, distillation or a custom imported model beats RAG, and manage the custom model lifecycle with versioning, approval and retraining. Know LoRA adapters for cheap domain variants, SageMaker Model Registry approval, Bedrock Custom Model Import and why a Legacy base model forces a replacement plan.
Study notes and 1 free question on Fine-tuning, LoRA adapters and custom model lifecycle (Bedrock, SageMaker AI, Model Registry)Validating data quality before it reaches a model (Glue Data Quality, Lambda checks)
Stop bad data before it reaches a model by running Glue Data Quality rules and Lambda checks at ingestion, quarantining failures and alerting on them. Know which checks suit a RAG corpus, a fine-tuning dataset or live records, and how freshness, completeness and duplicate detection protect answer quality.
Study notes and 2 free questions on Validating data quality before it reaches a model (Glue Data Quality, Lambda checks)Processing images, audio, documents and tables for FMs (Bedrock Data Automation, Transcribe)
Turn images, audio, video, documents and tables into text or structured data a model can use. Know when Bedrock Data Automation, Amazon Transcribe, Textract, a multimodal model or a foundation model parser fits, and how Step Functions runs these steps at scale.
Study notes and 1 free question on Processing images, audio, documents and tables for FMs (Bedrock Data Automation, Transcribe)Formatting and enriching input for model requests (Converse API, Comprehend, normalization)
Shape what goes into a model request: the system prompt and message roles in the Converse API, conversation history, entity enrichment with Comprehend, and deterministic normalization in Lambda. Know which step belongs before the model call, and how SageMaker AI endpoint payloads differ from Bedrock requests.
Study notes and 1 free question on Formatting and enriching input for model requests (Converse API, Comprehend, normalization)Choosing and scaling vector stores (OpenSearch, Aurora pgvector, S3 Vectors, managed knowledge bases)
Choose a vector store by data location, scale and cost: a managed knowledge base, OpenSearch, Aurora PostgreSQL with pgvector, or S3 Vectors for huge, rarely queried sets. Know how index type and embedding dimensions drive memory and recall.
Study notes and 1 free question on Choosing and scaling vector stores (OpenSearch, Aurora pgvector, S3 Vectors, managed knowledge bases)Document metadata and filtering for precise retrieval
Use document metadata and query-time filters to return precise, permitted and recent chunks from a knowledge base. Know the .metadata.json sidecar format, explicit and implicit filters, and how tenant and access attributes carry into retrieval so the model cannot widen them.
Study notes and 1 free question on Document metadata and filtering for precise retrievalConnecting data sources and keeping vector stores current
Connect enterprise sources to a knowledge base and keep the vector store current: built-in connectors or a custom export to S3, incremental sync that handles changed and deleted documents, direct ingestion for near-real-time updates, and event-driven triggers. Know when each refresh method fits.
Study notes and 1 free question on Connecting data sources and keeping vector stores currentChunking strategies (fixed-size, hierarchical, semantic, custom Lambda)
Chunking splits documents into pieces before embedding, and the strategy decides whether retrieval finds the right passage with enough context. Know fixed-size with overlap, hierarchical parent and child chunks, semantic chunking, custom Lambda splitting, and when no chunking fits.
Study notes and 1 free question on Chunking strategies (fixed-size, hierarchical, semantic, custom Lambda)Choosing and generating embeddings (Titan, Cohere, Nova multimodal)
An embedding model turns text or images into vectors, and the model, dimension and distance metric set retrieval quality and storage cost. Know Titan Text Embeddings V2 dimensions, Cohere multilingual options, Nova Multimodal Embeddings, and why a model change forces full re-embedding.
Study notes and 1 free question on Choosing and generating embeddings (Titan, Cohere, Nova multimodal)Semantic, hybrid search and reranking
Hybrid search combines keyword and semantic matching, and a reranker model reorders the top candidates by relevance. Know when exact terms still matter, why you retrieve more than you pass to the model, how score thresholds help, and where OpenSearch fits.
Study notes and 1 free question on Semantic, hybrid search and rerankingQuery expansion, decomposition and rewriting
Query transformation rewrites, splits or expands a question before retrieval. Know decomposition for multi-part questions, rewriting follow-ups with history, synonym expansion, HyDE, agentic retrieval across knowledge bases, and the added latency of each model call.
Study notes and 1 free question on Query expansion, decomposition and rewritingExposing retrieval to models as tools (function calling, MCP)
Retrieval can be a tool a model calls only when needed, or a shared MCP service. Know Retrieve versus RetrieveAndGenerate, tool schema design, when AgentCore Gateway exposes an existing search API, and why access filters must come from the caller, not the model.
Study notes and 1 free question on Exposing retrieval to models as tools (function calling, MCP)Prompt templates, versioning and governance (Bedrock Prompt Management)
Prompt management treats prompts as governed assets with variables, versions, variants and approvals. Know Bedrock Prompt management, storing prompts in Git or S3 with review, what CloudTrail and invocation logs can prove, and where central role instructions belong.
Study notes and 1 free question on Prompt templates, versioning and governance (Bedrock Prompt Management)Conversation memory and clarification flows
Conversation context keeps follow-ups working within the context window without mixing users' data. Know DynamoDB history with TTL, AgentCore Memory short-term and long-term memory, summarizing old turns, per-user namespaces, and Step Functions clarification flows.
Study notes and 1 free question on Conversation memory and clarification flowsTesting prompts for regressions and edge cases
Prompt testing catches regressions before users do, using golden datasets, format checks and metric alarms. Know CI golden test runs, Lambda JSON validation, A/B comparison on one dataset, Bedrock evaluations, and detecting format drift when a model version changes.
Study notes and 1 free question on Testing prompts for regressions and edge casesPrompt engineering techniques (few-shot, chain-of-thought, structured output)
Prompt techniques shape a model's output without retraining: few-shot examples, step-by-step reasoning, tagged sections, structured output and role instructions, improved over time with evaluation results. Know which technique fixes which failure and where structured outputs and JSON schemas fit.
Study notes and 1 free question on Prompt engineering techniques (few-shot, chain-of-thought, structured output)Prompt chains and flows (Amazon Bedrock Flows, Step Functions)
Prompt chains split a complex task into several model steps, with code or conditions between them. Know Amazon Bedrock Flows for visual and API workflows, Step Functions with the Bedrock integration for retries and parallel branches, pre- and post-processing Lambda steps, and when one prompt is the better choice.
Study notes and 1 free question on Prompt chains and flows (Amazon Bedrock Flows, Step Functions)
Domain 2: Implementation and Integration 26%
At 26%, this domain is about building and connecting the application. It covers agents (Strands Agents and Amazon Bedrock AgentCore), reasoning patterns, safeguards that stop runaway agents, multi-model coordination, human review, tools and MCP servers, choosing between on-demand, Provisioned Throughput and SageMaker AI endpoints, hosting open-weight models on GPUs, model cascading and routing, event-driven integration with enterprise systems, secure access, hybrid and edge deployments, CI/CD and GenAI gateways, synchronous, asynchronous and batch calls, streaming, retries and fallbacks, front ends and developer tools.
Building agents (Strands Agents, AgentCore Runtime, multi-agent patterns)
Agents on AWS are built on Amazon Bedrock AgentCore, which runs agents from any framework, such as Strands Agents, with isolated sessions and agent-to-agent (A2A) support. Know when to use AgentCore Runtime, supervisor patterns, A2A between teams, and the managed harness versus code.
Study notes and 2 free questions on Building agents (Strands Agents, AgentCore Runtime, multi-agent patterns)Agent reasoning patterns (ReAct, planning, Step Functions orchestration)
Agent reasoning patterns decide how a model works through a task: an open loop of reason, act and observe, a plan executed step by step, or a fixed workflow in Step Functions. Know when autonomy helps, when an auditable workflow is required, and how reflection and parallel steps fit in.
Study notes and 1 free question on Agent reasoning patterns (ReAct, planning, Step Functions orchestration)Agent safeguards (stopping conditions, timeouts, IAM boundaries, AgentCore Policy)
Agent safeguards stop runaway loops, slow tools and over-privileged actions. Know stopping conditions, timeouts and circuit breakers, least-privilege IAM for tool roles, AgentCore Policy enforced at the Gateway, human confirmation for destructive actions, and per-session budgets.
Study notes and 1 free question on Agent safeguards (stopping conditions, timeouts, IAM boundaries, AgentCore Policy)Coordinating several models (specialists, ensembles, routing)
Coordinating several models means routing each task to the model that does it best, or combining several models' outputs. Know specialist routing by task type, ensemble voting, small-model triage with escalation, judge models for picking the best candidate, and deterministic aggregation.
Study notes and 1 free question on Coordinating several models (specialists, ensembles, routing)Human review and approval in AI workflows
Human review adds a person where model output is uncertain, risky or needs correction. Know how Step Functions task tokens pause a workflow for approval, how confidence thresholds route outputs to reviewers, and how to handle reviewers who never respond.
Study notes and 1 free question on Human review and approval in AI workflowsTool integration and MCP servers (Lambda, ECS, AgentCore Gateway)
Tool integration gives a model actions and data through MCP servers on Lambda, ECS or AgentCore Gateway. Know when a stateless Lambda server fits versus a stateful ECS service, how Gateway turns APIs into tools, and how AgentCore Identity handles third-party OAuth.
Study notes and 2 free questions on Tool integration and MCP servers (Lambda, ECS, AgentCore Gateway)Choosing how to deploy models (on-demand, Provisioned Throughput, SageMaker AI endpoints)
Deployment choice decides how a model is served: on-demand Bedrock for spiky traffic, Provisioned Throughput for steady high volume, SageMaker AI endpoints for open-weight models you control, and batch processing for jobs that can wait. Know each option's cost pattern.
Study notes and 1 free question on Choosing how to deploy models (on-demand, Provisioned Throughput, SageMaker AI endpoints)Hosting LLMs on containers and GPUs (SageMaker AI, EKS, model loading)
Self-hosting an LLM on GPUs means sizing memory for weights and the KV cache, splitting large models across GPUs, cutting cold starts, and shrinking models with quantization. Know when SageMaker AI endpoints beat EKS, and when a managed Bedrock option avoids hosting.
Study notes and 1 free question on Hosting LLMs on containers and GPUs (SageMaker AI, EKS, model loading)Model cascading and routing to the right model
Model cascading sends each request to the right model, from a fixed routing config to intelligent prompt routing, Step Functions branching and escalation when a small model is unsure. Know which routing method fits the scenario, and the latency and quality costs of cascades.
Study notes and 1 free question on Model cascading and routing to the right modelEvent-driven integration with enterprise systems (EventBridge, API Gateway, Lambda)
Generative AI features usually start from business events, such as CRM updates, SaaS webhooks or files that land on premises, and must reach models without rewriting legacy systems. Know when to use EventBridge, API Gateway, SQS, AppFlow and an API facade, and how each one handles retries, timeouts and decoupling.
Study notes and 1 free question on Event-driven integration with enterprise systems (EventBridge, API Gateway, Lambda)Secure access to models and data (federation, RBAC, least privilege)
Secure generative AI access combines IAM policies that limit models and guardrails, federated identity for people, and document permissions enforced during retrieval. Know Identity Center, Cognito authorizers, tag-based access control and the bedrock:GuardrailIdentifier condition key.
Study notes and 1 free question on Secure access to models and data (federation, RBAC, least privilege)Hybrid and edge GenAI for data residency (Outposts, Wavelength, Local Zones)
Hybrid and edge generative AI designs keep data, processing or latency in a specific place while still using AWS services. Know when Outposts keeps data on premises, how Local Zones and Wavelength serve low latency users, how to reach Bedrock privately from on premises, and how to redact data before a cloud call.
Study notes and 1 free question on Hybrid and edge GenAI for data residency (Outposts, Wavelength, Local Zones)CI/CD and GenAI gateway architectures (CodePipeline, central gateway)
Generative AI pipelines test prompts, models and guardrails as code, gate releases on evaluation results, and roll back when quality alarms fire. Know CodePipeline evaluation stages, infrastructure as code, staged AppConfig rollouts and a central gateway for quotas and usage.
Study notes and 1 free question on CI/CD and GenAI gateway architectures (CodePipeline, central gateway)Synchronous, asynchronous and batch model invocation
Model calls can be synchronous, asynchronous or offline batch, and the right pattern depends on response time, volume and the client's timeout. Know the 29-second REST API integration timeout, SQS and Step Functions for long jobs, WebSocket or polling for results, and batch inference for very large offline datasets.
Study notes and 1 free question on Synchronous, asynchronous and batch model invocationStreaming responses (ConverseStream, WebSockets, response streaming)
Streaming shows model tokens as they are generated, which improves perceived latency for chat and long answers. Know ConverseStream, API Gateway WebSocket APIs for chat clients, Lambda response streaming through function URLs, stop reasons in a stream, and the synchronous and asynchronous guardrail streaming modes.
Study notes and 1 free question on Streaming responses (ConverseStream, WebSockets, response streaming)Handling throttling, retries and fallbacks
Model APIs throttle when quota runs out, so resilient apps retry with backoff and jitter, smooth bursts with queues, fall back to other models and trace each call. Know quota increases versus cross-Region inference, and why tool calls need idempotent retries.
Study notes and 1 free question on Handling throttling, retries and fallbacksBuilding GenAI front ends and business integrations (Amplify, OpenAPI, Bedrock Data Automation)
Managed building blocks speed up generative AI front ends and business integrations: Amplify for chat UIs, OpenAPI contracts, Step Functions for document flows and Bedrock Data Automation for field extraction. Know which one fits a speed, contract or extraction need.
Study notes and 1 free question on Building GenAI front ends and business integrations (Amplify, OpenAPI, Bedrock Data Automation)Developer productivity and troubleshooting tools (Kiro, Amazon Q Developer, Logs Insights)
Developer tools for generative AI include Kiro for spec-driven IDE work, Amazon Q Developer for code and console help, and Logs Insights and tracing for troubleshooting. Know which tool fits each task and how to find failure patterns across invocation logs.
Study notes and 1 free question on Developer productivity and troubleshooting tools (Kiro, Amazon Q Developer, Logs Insights)
Domain 3: AI Safety, Security, and Governance 20%
At 20%, this domain covers keeping inputs and outputs safe with Amazon Bedrock Guardrails and layered controls, reducing hallucinations with grounding checks and structured outputs, defending against prompt injection, isolating workloads with VPC endpoints, IAM and encryption, protecting personal data, governance through model cards, lineage and audit logs, continuous monitoring for misuse and drift, and turning responsible AI principles (transparency, fairness, policy compliance) into working controls.
Filtering harmful input (Bedrock Guardrails content filters and denied topics)
Amazon Bedrock Guardrails screens user input before a model sees it, using content filters, denied topics, word filters and the prompt attack filter. Know which filter fits which kind of harm, how input tags limit scanning to user text, and when the ApplyGuardrail API screens text for any model.
Study notes and 2 free questions on Filtering harmful input (Bedrock Guardrails content filters and denied topics)Preventing harmful or unwanted output
Output safety checks what a model returns before users or downstream systems see it. Know output guardrails with blocked messages, mask versus block actions, streaming filter modes, deterministic query generation instead of free-form SQL, and LLM-as-a-judge toxicity measurement.
Study notes and 1 free question on Preventing harmful or unwanted outputReducing hallucinations (grounding, contextual grounding checks, Automated Reasoning, structured outputs)
Hallucinations are answers the model invents or states without support. Know contextual grounding checks and their thresholds for RAG, Automated Reasoning checks for written rules, JSON schema structured outputs, citations with refusals when retrieval is empty, and human fallback for low confidence.
Study notes and 1 free question on Reducing hallucinations (grounding, contextual grounding checks, Automated Reasoning, structured outputs)Layered safety controls across the request path
Defense in depth stacks safety controls at each step of a GenAI request so one failed layer does not expose the application. Know the order of controls from the edge to the output, how IAM can force guardrail use, how to share guardrails centrally, and how to log and alert on interventions.
Study notes and 1 free question on Layered safety controls across the request pathPrompt injection and jailbreak defense
Prompt injection is untrusted text, typed by a user or hidden in retrieved documents and web pages, that tries to override instructions. Know the Bedrock prompt attack filter with input tags, how to separate instructions from data, least-privilege tools, output encoding, and adversarial testing in the pipeline.
Study notes and 1 free question on Prompt injection and jailbreak defenseIsolating GenAI workloads (VPC endpoints, IAM, Lake Formation)
Network isolation keeps GenAI traffic and data off the public internet. Know Bedrock interface VPC endpoints (PrivateLink), endpoint policies, S3 and Lake Formation controls for RAG data, customer managed KMS keys, and running agents inside a VPC.
Study notes and 2 free questions on Isolating GenAI workloads (VPC endpoints, IAM, Lake Formation)Protecting PII and sensitive data (Guardrails sensitive info filters, Macie, Comprehend)
PII protection keeps personal data out of prompts, answers, logs and training sets. Know Bedrock Guardrails sensitive information filters with block or mask actions, custom regex for internal IDs, Amazon Macie for finding PII in S3, Comprehend PII redaction before fine-tuning, and retention and logging controls.
Study notes and 1 free question on Protecting PII and sensitive data (Guardrails sensitive info filters, Macie, Comprehend)AI governance frameworks (model cards, lineage, approval)
Model governance decides who may approve, deploy and use a model, and records what each model is for and where it fails. Know model cards, approval status in the SageMaker AI Model Registry, data lineage with the Glue Data Catalog, risk tiers that map to required controls, and a central register of models and prompts.
Study notes and 1 free question on AI governance frameworks (model cards, lineage, approval)Audit logging and source traceability (invocation logging, CloudTrail, Data Catalog)
Audit traceability shows who used which model, with which prompt and data, and which source supported each answer. Know invocation logging (off by default), CloudTrail for API calls, Glue Data Catalog source records, stored citations, and S3 Object Lock.
Study notes and 1 free question on Audit logging and source traceability (invocation logging, CloudTrail, Data Catalog)Continuous monitoring for misuse, drift and policy violations
Continuous governance watches a live GenAI system for misuse, quality drift and policy violations, then responds. Know guardrail intervention alarms, scheduled Bedrock evaluations against a baseline, EventBridge and Step Functions remediation, and per-user anomaly detection.
Study notes and 1 free question on Continuous monitoring for misuse, drift and policy violationsTransparency and explainability (citations, reasoning traces)
Transparency lets users and reviewers see where an answer came from, how sure the system is, and that AI produced it. Know citations from RetrieveAndGenerate, agent traces with AgentCore Observability, uncertainty indicators, AI-content disclosure and watermarks, and evidence panels that link claims to sources.
Study notes and 1 free question on Transparency and explainability (citations, reasoning traces)Fairness and bias evaluation
Fairness testing checks whether a GenAI system treats groups differently for the same request. Know counterfactual prompt pairs, LLM-as-a-judge with fairness criteria, prompt variant comparisons, human review for sensitive outputs, fairness metrics in CloudWatch and dataset balance checks before fine-tuning.
Study notes and 1 free question on Fairness and bias evaluationTurning responsible AI policy into controls
A responsible AI policy is a written set of rules, and AIP-C01 asks how to turn each rule into a control the system enforces. Know how to map clauses to guardrail settings and denied topics, pre-release compliance checks, human oversight for high-risk decisions, user disclosure, and versioned controls as code.
Study notes and 1 free question on Turning responsible AI policy into controls
Domain 4: Operational Efficiency and Optimization for GenAI Applications 12%
At 12%, this domain is about running generative AI applications efficiently. It covers token efficiency, choosing cheaper models and service tiers, throughput, quotas and capacity, prompt caching and semantic caching, latency, inference parameters such as temperature and top-p, monitoring with CloudWatch and model invocation logs, agent and tool observability, and keeping vector stores fast and healthy.
Token efficiency (context pruning, prompt compression, response limits)
Token efficiency keeps each request small enough to be cheap and fast without dropping the context the model needs. AIP-C01 asks how to cap response length, prune and summarize conversation history, retrieve fewer and better chunks, and count tokens before sending.
Study notes and 1 free question on Token efficiency (context pruning, prompt compression, response limits)Cost-effective model choice and tiered usage
Cost-effective model choice sends each step to the cheapest model that meets its quality bar, and each request to the right service tier. AIP-C01 asks about tiered model use, distillation, measuring price-performance on your own data, batch and Flex tiers, and cost allocation with application inference profiles.
Study notes and 1 free question on Cost-effective model choice and tiered usageThroughput, quotas and capacity planning
Throughput planning keeps a generative AI workload under model quotas at peak load. AIP-C01 asks how to size tokens-per-minute quotas against request rate, when Provisioned Throughput fits, how to smooth bursts with queues and backoff, and when batch or cross-Region inference helps.
Study notes and 1 free question on Throughput, quotas and capacity planningPrompt caching and semantic caching
Caching reuses earlier work so repeated prompts and answers cost less and return faster. AIP-C01 asks when to use Bedrock prompt caching for a repeated prefix, when a semantic cache or an exact-match cache fits, and how to invalidate cached answers when source documents change.
Study notes and 1 free question on Prompt caching and semantic cachingLatency optimization (streaming, latency-optimized inference, parallel calls)
Latency work makes the first visible response arrive quickly and keeps total time within the user's wait limit. AIP-C01 asks when to stream, when to use latency-optimized inference or the Priority tier, how to run independent subtasks in parallel, and how to cut retrieval time.
Study notes and 1 free question on Latency optimization (streaming, latency-optimized inference, parallel calls)Tuning inference parameters (temperature, top-p, top-k, stop sequences)
Inference parameters control how randomly and how long a model generates text. AIP-C01 asks which setting fits deterministic extraction versus creative variants, how temperature and top-p interact, how stop sequences and token limits end output, and how to A/B test configurations.
Study notes and 1 free question on Tuning inference parameters (temperature, top-p, top-k, stop sequences)Monitoring GenAI applications (CloudWatch, invocation logs, dashboards)
Monitoring GenAI applications combines model metrics, invocation logs and business KPIs in CloudWatch. AIP-C01 asks which metrics to watch for latency, throttling and token use, how to query invocation logs, how to alert on token bursts and spend, and how to build dashboards for business outcomes.
Study notes and 1 free question on Monitoring GenAI applications (CloudWatch, invocation logs, dashboards)Agent and tool observability (AgentCore Observability, tracing)
Agent observability traces each reasoning step and tool call, so you can find wrong tools, loops and slow dependencies. AIP-C01 asks how to instrument agents with OpenTelemetry through AgentCore Observability, which baselines to alert on, how to trace multi-agent work and how to view agents across accounts.
Study notes and 1 free question on Agent and tool observability (AgentCore Observability, tracing)Operating and tuning vector stores
Operating a vector store means keeping queries fast and accurate as data grows. AIP-C01 asks how to monitor latency and recall, tune HNSW parameters for the speed and recall trade-off, scale OpenSearch Serverless capacity, plan shard sizes, and validate chunks loaded into the store.
Study notes and 1 free question on Operating and tuning vector stores
Domain 5: Testing, Validation, and Troubleshooting 11%
At 11%, this domain covers measuring quality and fixing problems. It covers model evaluation with Amazon Bedrock evaluations and LLM-as-a-judge, RAG and retrieval evaluation, agent evaluation with AgentCore Evaluations, user feedback and reporting, quality gates for model and prompt updates, and troubleshooting context-window limits, API errors, inconsistent prompts and poor retrieval.
Evaluating model output quality (Bedrock evaluations, LLM-as-a-judge)
Model evaluation measures output quality on your own prompts before and after a change. AIP-C01 asks when to use Bedrock automatic evaluation, LLM-as-a-judge with custom metrics, or a human evaluation job, and how to compare models on cost and latency alongside quality.
Study notes and 1 free question on Evaluating model output quality (Bedrock evaluations, LLM-as-a-judge)Evaluating RAG and retrieval quality
RAG evaluation checks whether retrieval finds the right chunks and whether answers stay faithful to them. AIP-C01 asks when to use retrieve-only or retrieve-and-generate metrics, how to build a golden question set, and how to compare chunking settings.
Study notes and 1 free question on Evaluating RAG and retrieval qualityEvaluating agents (task completion, tool use, AgentCore Evaluations)
Agent evaluation scores whether an agent completes the task, picks the right tools and reasons well across steps. AIP-C01 asks when to use batch evaluation on scripted scenarios, online evaluation of sampled live sessions with AgentCore Evaluations, and A/B tests of two agent versions.
Study notes and 1 free question on Evaluating agents (task completion, tool use, AgentCore Evaluations)User feedback, annotation and reporting
Human feedback turns user reactions and reviewer ratings into data you can act on. AIP-C01 asks how to capture thumbs up or down tied to a request ID, run an annotation workflow with a rubric, build stakeholder dashboards, and turn feedback into regression tests.
Study notes and 1 free question on User feedback, annotation and reportingQuality gates and validation for model and prompt updates
Deployment validation sets quality gates that stop model or prompt changes from reaching users when they regress. AIP-C01 asks about pipeline gates, canary rollouts with CloudWatch alarm rollback, synthetic checks and drift or hallucination thresholds.
Study notes and 1 free question on Quality gates and validation for model and prompt updatesTroubleshooting context limits and API errors
Context and API troubleshooting fixes requests that fail or get cut off by size, quota, service health or access. AIP-C01 asks how to read ValidationException, max_tokens stops, throttling and access errors, and how to fit long documents.
Study notes and 1 free question on Troubleshooting context limits and API errorsTroubleshooting prompts and inconsistent responses
Prompt troubleshooting fixes responses that vary in format, ignore instructions or hallucinate after a change. AIP-C01 asks when to add a schema and examples, when long context pushes instructions out of focus, how to compare prompt versions, and how a golden dataset and output diffs reveal regressions.
Study notes and 1 free question on Troubleshooting prompts and inconsistent responsesTroubleshooting retrieval quality
Retrieval troubleshooting finds why the right document is missing, stale or slow to search. AIP-C01 asks how to diagnose chunk size problems, embedding model mismatch, sync failures, metadata filters that exclude valid documents, lost table structure in parsed PDFs, and slow vector search at scale.
Study notes and 1 free question on Troubleshooting retrieval quality
A 7-week study plan
This plan assumes about an hour on weekdays and a longer, hands-on session at the weekend. Time follows the domain weights: RAG and data (31%) gets two weeks, implementation and agents (26%) gets two, and safety (20%) gets a full week. If you already ship generative AI features on AWS, five weeks may be enough.
| Week | Focus | Do this |
|---|---|---|
| 1 | Baseline and models | Take the free practice exam in timed mode. Then solution design and proofs of concept, choosing foundation models, the Converse API, switching models with AppConfig and inference profiles, cross-Region inference and fallbacks, fine-tuning, LoRA adapters, Custom Model Import and distillation. |
| 2 | Data and retrieval | Data validation with Glue Data Quality, multimodal processing with Bedrock Data Automation, knowledge bases and vector stores (OpenSearch, Aurora pgvector, S3 Vectors, managed knowledge bases), metadata, sync, chunking, embeddings, hybrid search, reranking, query rewriting, retrieval as a tool. |
| 3 | Prompts | Prompt Management, versions and approval, conversation memory, prompt techniques (few-shot, chain-of-thought, structured output), prompt testing, Amazon Bedrock Flows and Step Functions chains. |
| 4 | Agents and tools | Strands Agents, AgentCore Runtime, Gateway, Memory, Identity and Policy, MCP servers on Lambda and ECS, reasoning patterns, stopping conditions, human approval with Step Functions, multi-model routing. |
| 5 | Integration and deployment | On-demand, batch, Provisioned Throughput and service tiers, SageMaker AI endpoints for open-weight models, synchronous and asynchronous patterns, streaming, throttling and retries, event-driven integration, secure access, hybrid and edge, CI/CD and GenAI gateways. |
| 6 | Safety and governance | Guardrails (content filters, prompt attacks, denied topics, PII, contextual grounding, Automated Reasoning), defense in depth, VPC endpoints and encryption, Macie and Comprehend PII, invocation logging and CloudTrail, model cards, transparency and fairness. |
| 7 | Operations, testing and practice | Token efficiency, prompt and semantic caching, latency, inference parameters, CloudWatch monitoring and AgentCore Observability, Bedrock evaluations, RAG and agent evaluations, quality gates, troubleshooting. Then full timed practice exams; review every wrong answer. |
How to use practice questions well
- Practice the length. Do full 75-question sets in 180 minutes.
- Find the qualifier. Many wrong answers work but cost more, add latency, need more code or miss one constraint.
- Read the wrong options. They are usually a real feature solving a neighboring problem, or the right feature set up the wrong way.
- Don’t memorize questions. The real exam won’t reuse them.
- Aim for 80% or more across a few full timed practice exams before you book.
Get hands-on
In a personal account with a budget alert set: create a knowledge base from a few documents in S3 and query it with citations, attach a guardrail with a denied topic and a PII filter, call a model through the Converse API with streaming and tool use, turn on model invocation logging, run a small LLM-as-a-judge evaluation, and deploy a simple Strands agent to AgentCore Runtime. Delete everything afterward.
Frequently asked questions
Is this the same as the AI Practitioner exam?
No. AWS Certified AI Practitioner (AIF-C01) is a foundational exam about concepts and use cases. Generative AI Developer – Professional is a hands-on build exam with long scenarios about architecture, code paths, safety controls, cost and troubleshooting.
Do I need to know machine learning?
Only at the level of using models. Training and feature engineering are out of scope. You do need to know when fine-tuning helps, how parameter-efficient methods such as LoRA work at a high level, and how to deploy, version and retire a customized model.
Which services are no longer right answers?
From July 30, 2026, Amazon Bedrock Agents (Agents Classic), Amazon Kendra, Amazon Q Business, and SageMaker AI Clarify, Model Monitor, Ground Truth and Augmented AI are closed to new customers. AWS App Runner is also in maintenance, and the X-Ray SDKs are in maintenance in favor of OpenTelemetry. Our questions use the current replacements: AgentCore, Bedrock Knowledge Bases, Amazon Quick, Bedrock evaluations and CloudWatch.
Do I need the associate certifications first?
No, AWS has no prerequisites. Developer – Associate or Machine Learning Engineer – Associate knowledge helps, because this exam assumes you know Lambda, API Gateway, Step Functions, IAM and CloudWatch well.
Are the practice questions the real exam questions?
No. Every question on this site is original, written from the public exam guide and checked against AWS documentation. Using real exam questions breaks the AWS Certification Program Agreement.
Test yourself
The free AIP-C01 practice exam has 75 questions with an explanation for every option. No sign-up needed.
Want to be sure you're ready? The 5 full-length practice sets add 375 new questions, none of them in the free exam. One payment of $14.99, no subscription. See the practice sets