AIP-C01 — AWS Certified Generative AI Developer – Professional Study Plan

How to use this Study Plan

This Study Plan is for candidates preparing for the AWS Certified Generative AI Developer – Professional (AIP-C01) exam from AWS. It is designed for working professionals who need to turn limited study time into a realistic review schedule.

Use the current AWS exam guide as your objective checklist. This plan organizes your preparation around the practical skills a generative AI developer is likely to need: AWS service selection, model invocation, prompt design, retrieval-augmented generation, agents, security, evaluation, deployment, monitoring, troubleshooting, and cost-aware architecture.

The goal is not to read everything. The goal is to practice making correct decisions under timed, scenario-based conditions.

Which plan should you use?

Use the shorter plan only if you already have background knowledge. If you are still confused by core terms such as embeddings, RAG, model evaluation, IAM permissions, prompt injection, vector search, or AWS service selection, use the 30-day or 60/90-day path.

AIP-C01 study lanes

Use these lanes to organize your review. Match them against the current AWS AIP-C01 exam guide and mark each objective as strong, review, or weak.

Diagnostic-first setup

Before you begin any plan, spend one focused session building your baseline.

Do not judge readiness from one practice score. Look for a pattern: fewer repeated mistakes, better scenario reasoning, and enough time left to review flagged questions.

Daily practice rhythm

Use this rhythm for most study days. Shorten the blocks if you have less time, but keep the same order.

For AIP-C01, do not spend all study time reading. You need to practice choosing between similar architecture options, security controls, data patterns, and troubleshooting paths.

Missed-question review method

A missed question is useful only if you convert it into a rule you can reuse.

Create an error log with these columns:

Classify each miss:

Revisit each miss at least twice: once within 24 hours and again several days later.

When to use timed mock exams

Timed mocks are most useful after you have enough coverage to learn from the results. Do not burn all mocks early.

After each mock, review in this order:

1. Questions you missed.
2. Questions you guessed correctly.
3. Questions that took too long.
4. Topics with repeated mistakes.
5. Architecture decisions you could not explain clearly.

7-day final review plan

Use this plan if your exam is within a week and you have already studied most objectives. If you have not started yet, use the 14-day plan as a minimum and postpone if possible.

Final 7-day priorities

Spend the most time on:

• Scenario-based service selection.
• RAG design and troubleshooting.
• Security and data protection decisions.
• Model evaluation and quality improvement.
• Operational failure patterns.
• Cost, latency, and reliability tradeoffs.

Avoid:

• Deep memorization of undocumented limits.
• Building large projects.
• Reading broad documentation without practice.
• Taking a full mock the night before the exam.

14-day focused plan

Use this plan if you know AWS basics and can study consistently for two weeks.

If Day 14 is your exam day, move the second mock to Day 11 and use Day 13 for light review.

30-day balanced plan

Use this plan if you want a realistic workday schedule with enough time for review, practice, and mock exams.

Days 1-7: Baseline and core concepts

Days 8-14: Application patterns, RAG, and agents

Days 15-21: Security, deployment, and operations

Days 22-30: Timed performance and final repair

60/90-day full preparation path

Use the 60-day version if you can study about 8-10 hours per week. Use the 90-day version if you have 4-6 hours per week, are new to AWS generative AI services, or need more hands-on repetition.

60-day path

90-day path

Hands-on review for longer plans

Keep hands-on work small and exam-focused. You are not trying to build a production system during prep. You are trying to understand the decisions.

Useful hands-on or diagramming exercises:

A simple RAG flow to know cold:

source data
  -> clean and split
  -> create embeddings
  -> store vectors with metadata
  -> retrieve relevant chunks
  -> assemble grounded prompt
  -> invoke model
  -> evaluate answer quality, safety, and citations

Be able to troubleshoot each step.

High-yield decision tables

Model and architecture selection

RAG troubleshooting

Security and governance review

Final-week rules

During the final week, your job is to reduce uncertainty, not add complexity.

Follow these rules:

1. Stop adding new material 24-48 hours before the exam.
2. Review misses more than notes. Your error log is the most valuable final resource.
3. Practice timing. Do not let one complex scenario consume too much time.
4. Use scenario keywords. Identify constraints: security, cost, latency, quality, operations, compliance, private data, or human approval.
5. Explain the wrong answers. If you cannot explain why an option is wrong, the concept is not secure yet.
6. Avoid heavy hands-on builds. Use diagrams and decision tables instead.
7. Sleep and logistics matter. A tired candidate makes avoidable reasoning errors.

Exam-readiness checks

You are likely ready when most of these are true:

If several checks are still “No,” spend your remaining time on mixed scenario practice and missed-question repair rather than broad reading.

Practical next step

Choose the shortest plan that honestly fits your current readiness. Start with a diagnostic practice set, build an error log, and schedule your first timed mock. For AIP-C01, the highest-value work is repeated scenario practice: choose the architecture, justify the AWS services, identify the security controls, and explain how you would troubleshoot the failure.