AWS DVA-C02 Study Plan: Lambda, Eventing, and Troubleshooting in 30, 60, and 90 Days

This page answers the question most candidates actually have: “How do I structure my DVA-C02 prep?” Below are three realistic schedules (30 / 60 / 90 days) based on the current official weighted domains and the chapterized online guide for this exam.

Use the plan that matches your available time, but anchor it to real implementation reps. Each week should include one short build, one troubleshooting pass, one timed drill set, and one miss-log review. The loop is: study chapter -> do a small build -> run timed questions -> log misses -> revisit the weak chapter or appendix.

Best way to use this plan

Treat DVA-C02 as a judgment exam, not a service-name exam. The strongest loop is:

1. learn one chapter
2. build or debug one small AWS path
3. run focused questions
4. convert misses into short rules
5. re-drill the same lane within 48-72 hours

If you only read, your async, IAM, and deployment mistakes usually repeat.

How long should you study?

There is no single right number, but most candidates land in a range based on background:

Choose a plan based on hours per week:

Use the current weighted chapters to allocate time

AWS currently weights the guide like this:

If you want one rule: spend ~70% learning and 30% practice early, then invert it to ~30% learning and 70% practice in the final one or two weeks.

Minimum hands-on baseline before timed sets

Try to keep one small runnable workload alive while you study. For DVA-C02, that baseline should include:

• a Lambda path behind API Gateway with one synchronous flow and one asynchronous event source
• at least one DynamoDB table with a partition-key decision you can explain
• one IAM or KMS denial you diagnose on purpose
• one deployment workflow where you can explain what makes rollback safe and low blast radius

30-Day Intensive Plan

Target pace: ~10-15 hours/week (1.5-2.5 hrs/day). Goal: cover the official domains quickly, then rely on drills and mocks to harden instincts.

Checkpoint before exam day: you can explain why a solution is correct in one sentence, not just recognize a familiar service name.

60-Day Balanced Plan

Target pace: ~6-9 hours/week. Goal: learn each domain, then loop back for spaced repetition and mixed practice.

90-Day Part-Time Plan

Target pace: ~3-5 hours/week. Goal: slow repetition and stickiness while building consistent practice habits.

How to use timed practice without turning it into guesswork

Use timed practice to test judgment, not to replace the explanation layer:

1. Start with Resources so you know the current AWS scope and exam wording.
2. Review the matching section in the online guide before you run timed questions.
3. Use the Cheat Sheet for high-confusion service and pattern separation.
4. Tag every miss as development, security, deployment, or troubleshooting.
5. Turn repeated misses into one-sentence rules such as async Lambda needs idempotent handlers or service access and KMS key access are separate permission lanes.
6. Re-run the weak area 48-72 hours later until the same failure mode stops repeating.

Last-week compression plan

Suggested practice progression

• Early phase: 20-25 question section drills to learn pattern recognition fast.
• Middle phase: 30-40 question mixed sets to transfer reasoning across services.
• Final phase: full mocks (65 questions / 130 minutes) plus deep review of every miss.

Target before exam day: consistent ~75-80% on mixed sets, with stable performance across all four weighted domains, especially Security and Troubleshooting and Optimization.