Home / artificial-intelligence-machine-learning / AWS Certified Generative AI Developer - Professional (AIP-C01) / Cheat Sheet
AWS Certified Generative AI Developer - Professional (AIP-C01)

AIP-C01 Cheat Sheet

AIP-C01 Tests Production GenAI Architecture on Bedrock — Not Prompt Writing Tricks

A professional-level exam for builders shipping GenAI to production: 75 questions in 180 minutes. Shift from 'which model is smartest' to 'which managed Bedrock feature meets every stated constraint'.

Check Your Readiness →
Among the harder certs
Avg: Not published by Amazon Web Services
Pass: 750 / 1000
Most candidates understand AWS Certified Generative AI Developer - Professional (AIP-C01) concepts — and still fail. This exam tests how you apply knowledge under pressure.

AIP-C01 Domain Map

Long multi-constraint scenarios: data freshness, latency, cost, Region, compliance and tolerance for custom code all matter, and the right option satisfies every one. The guide names Amazon Bedrock Prompt Flows; AWS now markets it as Bedrock Flows, so expect either name.

  1. 01
    FM Integration, Data Management and Compliance (31%) — model selection, RAG design, vector stores, chunking, prompt governance
  2. 02
    Implementation and Integration (26%) — agents, MCP tools, hosting choices, throttling, GenAI gateways and async patterns
  3. 03
    AI Safety, Security and Governance (20%) — Bedrock Guardrails policies, PII controls, private access, audit logging
  4. 04
    Operational Efficiency and Optimization (12%) — token cost, prompt vs. semantic caching, model tiering, latency levers
  5. 05
    Testing, Validation and Troubleshooting (11%) — Bedrock evaluations, RAG metrics, canary releases, symptom-to-cause tracing

Wrong instinct vs correct approach

Users search a legal RAG assistant by exact case numbers and get irrelevant passages, while conceptual questions work
✕ Wrong instinct

Switch to an embedding model with more dimensions

✓ Correct approach

Embeddings blur exact tokens such as case numbers and SKUs. Enable hybrid keyword plus vector search, add a reranker, and use metadata filtering. Higher dimensions add storage and latency without fixing exact-match recall.

An agent repeatedly calls the same inventory tool and its Bedrock bill spikes overnight
✕ Wrong instinct

Tell the agent in its instructions to stop sooner

✓ Correct approach

Models cannot be trusted to end a ReAct loop. Enforce iteration limits, timeouts and token budgets outside the model, scope the tool role with least-privilege IAM, and alarm on token anomalies so the next runaway loop is caught quickly.

The team must switch the production model to a different provider without a code release
✕ Wrong instinct

Redeploy the Lambda function with the new model ID

✓ Correct approach

Externalize model choice in AWS AppConfig or a GenAI gateway so the model ID changes at runtime. A gateway also centralizes quotas, logging and fallback routing for every team consuming foundation models.

Forty percent of FAQ questions are paraphrases of twenty common ones and cost must drop
✕ Wrong instinct

Enable Bedrock prompt caching on the FAQ prompts

✓ Correct approach

Prompt caching only reuses a repeated prompt prefix; the model still runs. A semantic cache returns a stored answer for similar questions and skips the call entirely. Add expiry so answers about returns policy do not go stale.

Answers stop mid-sentence after the team added more retrieved passages to each prompt
✕ Wrong instinct

Move to a model with stronger reasoning

✓ Correct approach

Truncation points to a low max tokens setting or a prompt crowding the context window. Raise the output cap, prune irrelevant history and passages, then rerun the regression set before changing models.

Know these cold

  • ▸ RAG for changing facts, fine-tuning or LoRA for style and behavior, prompts for quick fixes
  • ▸ Prompt caching cheapens the call; semantic caching skips the call entirely
  • ▸ Streaming cuts time to first token only; total tokens, cost and generation time stay the same
  • ▸ CloudTrail logs who invoked; model invocation logging stores the prompt and response text
  • ▸ Macie finds PII in S3 at rest; Comprehend or Guardrails filters catch it in flight
  • ▸ Mask PII with sensitive information filters when users still need the rest of the answer
  • ▸ Changing the embedding model means re-embedding the whole corpus; never mix vector sets
  • ▸ Throttled calls — ackoff with jitter first, then cross-Region inference, then provisioned throughput
  • ▸ Short stateless MCP tools fit Lambda; heavy or long-running stateful tools belong on ECS
  • ▸ Evaluate retrieval and faithfulness separately; calibrate LLM-as-a-judge scores against human ratings

Can you answer these without checking your notes?

In this scenario: "Users search a legal RAG assistant by exact case numbers and get irrelevant passages, while conceptual questions work" — what should you do first?
Embeddings blur exact tokens such as case numbers and SKUs. Enable hybrid keyword plus vector search, add a reranker, and use metadata filtering. Higher dimensions add storage and latency without fixing exact-match recall.
In this scenario: "An agent repeatedly calls the same inventory tool and its Bedrock bill spikes overnight" — what should you do first?
Models cannot be trusted to end a ReAct loop. Enforce iteration limits, timeouts and token budgets outside the model, scope the tool role with least-privilege IAM, and alarm on token anomalies so the next runaway loop is caught quickly.
In this scenario: "The team must switch the production model to a different provider without a code release" — what should you do first?
Externalize model choice in AWS AppConfig or a GenAI gateway so the model ID changes at runtime. A gateway also centralizes quotas, logging and fallback routing for every team consuming foundation models.

Common Exam Mistakes — What candidates get wrong

Fine-tuning a model to keep up with frequently changing documents

Fine-tuned or LoRA weights freeze knowledge at training time. Policies, catalogs and prices that change weekly belong in Bedrock Knowledge Bases or another RAG pipeline, which also returns citations. Fine-tuning is for tone, format or task behavior, not facts.

Expecting CloudTrail to show what users actually asked the model

CloudTrail records the InvokeModel API call, caller and time, not the prompt body. Turn on Bedrock model invocation logging to CloudWatch Logs or S3 to capture prompts and responses for audit, quality analysis and cost investigations.

Treating a system prompt instruction as an enforceable safety control

Prompt injection can override 'never discuss X'. Enforcement comes from Bedrock Guardrails: denied topics for off-scope advice, sensitive information filters to mask PII, prompt attack detection on input, and contextual grounding checks on output.

Swapping in a larger foundation model when RAG answers miss facts

If retrieval never returns the right passage, no model can use it. Check chunking (hierarchical for precision plus context), hybrid search with reranking for exact IDs, metadata filters, and whether the index mixes vectors from two embedding models.

Buying provisioned throughput for bursty or modest Bedrock traffic

Provisioned throughput bills reserved model units by time, used or not. Variable traffic stays on demand, with SDK exponential backoff and jitter for ThrottlingException and cross-Region inference profiles for extra capacity. Reserve units for steady high volume or custom models.

Resources to help you pass AWS Generative AI Developer - Professional on your first attempt

AIP-C01 rewards picking the managed Bedrock feature that meets every constraint. See where your choices hold up.