How to pass the AWS Developer Associate exam (DVA-C02)
Updated
To pass the AWS Certified Developer – Associate exam (DVA-C02), study the four domains in weight order, build and deploy real code against the core services until their behaviour is concrete, and drill scenario questions until you can justify why one implementation beats another — then sit full-length timed mocks until you clear the pass mark consistently. DVA-C02 is a judgment exam written for people who ship application code on AWS: most questions describe an application with a requirement or a failure and ask for the best fix, so preparation has to go beyond knowing what each service is.
Understand what DVA-C02 actually tests
DVA-C02 is a role-based, scenario-driven exam for working developers. A typical question describes an application — a Lambda function timing out, an API that must authenticate users, a deployment that has to roll out without downtime — and asks which implementation best satisfies a stated qualifier ("least operational overhead", "most cost-effective", "minimal code changes"). Several options are usually real, working approaches; only one fits the constraint.
That shape decides how you prepare. You cannot pass by memorising service definitions, because every distractor is a genuine AWS feature used plausibly — just not optimally here. You pass by knowing the developer-facing services deeply enough to weigh them against each other, which is why AWS recommends about a year of hands-on experience building on the platform before sitting it.
Build and deploy real code, not just knowledge
The fastest preparation for a developer exam is doing the developer's job in miniature. On the AWS Free Tier, build a small serverless application end to end: a Lambda function behind API Gateway, reading and writing a DynamoDB table, with a queue decoupling one piece from another, secrets pulled from a secret store rather than hard-coded, and the whole thing defined in a SAM or CloudFormation template and deployed through a pipeline.
That one project touches most of what the exam asks about — packaging, environment variables, IAM permissions, error handling, deployment strategies, logs and traces. When a question later asks why a function cannot reach a resource or how to shift traffic to a new version safely, you will be recalling something you did, not something you read.
Study the four domains in weight order
The exam is organised into four domains and they are not equally weighted — Development with AWS Services carries the most, followed by Security, then Deployment, then Troubleshooting and Optimization. Your study time should mirror that order: the development domain alone covers Lambda, DynamoDB, API Gateway and the messaging services, and it is where the largest share of marks lives.
Do not let the security domain's second place fool you into treating it lightly. It sits unusually high for an associate exam because developers own so much of it in practice — IAM roles and policies, Cognito authentication, KMS encryption, keeping secrets out of code — and its questions punish vague understanding. The current exam guide also leans further into application-level concerns: structured logging, health checks, circuit breakers for third-party calls, and isolating tenant data in multi-tenant designs.
Learn the developer trade-offs, not the definitions
DVA-C02 is built on a recurring set of implementation decisions, and knowing these cold is most of the battle. Learn to choose between the commonly-confused options rather than merely defining each one:
- Decoupling: SQS vs SNS vs EventBridge — queue vs pub/sub fanout vs event routing with rules, and when Step Functions should orchestrate instead.
- Lambda: versions and aliases, layers, environment variables, concurrency controls, and how memory settings drive both performance and cost.
- DynamoDB: partition and sort key design, query vs scan, LSI vs GSI, provisioned vs on-demand capacity, and when Streams trigger downstream work.
- Secrets & config: Secrets Manager vs Systems Manager Parameter Store — rotation and cost on one side, simplicity on the other.
- Identity: Cognito user pools vs identity pools — authenticating users vs granting them AWS credentials — plus IAM roles and STS for service-to-service access.
- Deployment: all-at-once vs canary vs linear traffic shifting, blue/green vs rolling, and which strategy each CI/CD service actually performs.
- Resilience: retries with exponential backoff and jitter, idempotent handlers, dead-letter queues, and caching with ElastiCache or API Gateway.
Drill scenario questions and read every explanation
From early in your preparation, drill practice questions on the domains you have covered — and read the explanation on every option, including the ones you got right. On a judgment exam the explanations are the syllabus: understanding why a plausible implementation is second-best under this constraint is exactly the skill the real questions test.
Review your incorrect answers deliberately. Rebuilding sessions from previously missed questions turns your weakest decisions into your most-rehearsed ones, and per-domain accuracy shows you which of the four areas is leaking marks long before a mock does.
Rehearse with full-length timed mocks, then book
A full-length, timed mock is its own skill: sustaining implementation judgment across the whole sitting, pacing through scenario stems dense with configuration detail, and using flag-and-return so one hard DynamoDB question does not eat the time three easier ones need. Sit your first mock once all four domains are covered, then use the result to drive one more focused revision loop on your weakest domain.
The mocks here are scored on the same scaled system as the real exam, so the pass line means the same thing. Book the real exam when you clear it comfortably and repeatedly — and keep a daily practice habit going right up to exam day, because a long gap between "ready" and "sitting" is where readiness quietly decays.