DEV Community

ExamCert.App
ExamCert.App

Posted on

My 3-Week DVA-C02 Sprint, Week by Week (What I'd Cut and What I'd Repeat)

AWS Certified Developer – Associate

I passed the AWS Certified Developer – Associate (DVA-C02) with a 841 after three weeks of evening study. Not a heroic all-nighter story — I had a day job writing Python and TypeScript against Lambda and DynamoDB, so a lot of the exam was already muscle memory. But muscle memory is exactly the trap. This exam rewards knowing why AWS wants you to do a thing, not just that your code compiles. Here's how I broke the three weeks down, what actually moved the needle, and what I'd skip if I did it again.

First, the shape of the thing so you're calibrating against reality. DVA-C02 is 65 questions (50 scored, 15 unscored pilots), 130 minutes, multiple choice and multiple response. Passing is 720 on a scaled 100–1000, and it costs $150 USD. Four domains: Development with AWS Services (32%), Security (26%), Deployment (24%), and Troubleshooting and Optimization (18%). Notice Security is the second-biggest slice — bigger than Deployment. If you're a developer who treats IAM as "the thing the platform team handles," that 26% is where you bleed points. I front-loaded my study around that fact.

I ran my whole prep against the DVA-C02 blueprint on ExamCert, which lines the objectives up against practice questions so I wasn't guessing what "Deployment" actually covers on this version. That mattered because DVA-C02 quietly dropped some old SAM/CodeStar trivia and leaned harder into event-driven patterns.

Week 1 — Development + closing the DynamoDB gaps

Domain 1 is a third of the exam and it's the one developers overrate their readiness on. I write Lambda handlers weekly, but the exam probes edges I never touch: the difference between Lambda synchronous invocation (API Gateway, ALB) versus asynchronous (S3 events, SNS) versus poll-based (SQS, Kinesis, DynamoDB Streams), and how each one retries. Async retries twice with jitter and then dumps to a dead-letter queue if you configured one. Poll-based blocks the shard until the batch clears — a classic "why is my Kinesis consumer stuck" question.

DynamoDB ate most of my week. Know this cold:

# Strongly consistent read costs 2x an eventually consistent read
# 1 RCU = 1 strongly consistent read/sec for an item up to 4KB
# 1 WCU = 1 write/sec for an item up to 1KB
Enter fullscreen mode Exit fullscreen mode

I got a question about a hot partition throttling under load — the answer was write sharding by suffixing the partition key, not bumping provisioned capacity. Another wanted me to pick between a GSI and LSI, and the tell was "query on a new attribute after the table already exists" → GSI, because LSIs must be created at table birth. If your DynamoDB is fuzzy, that alone can cost you five questions.

I also drilled the SDK retry/backoff behavior and ExponentialBackoff, plus how the SDK reads credentials in order (env vars → shared config → instance profile). Boring, tested constantly.

By Friday I ran a first timed set of free DVA-C02 practice questions to get a baseline. I scored 68%. Under the passing line, exactly where I expected to be, and useful — it showed me Security was worse than I feared.

Week 2 — Security and Deployment, the underrated middle

This was the heavy week. Security (26%) plus Deployment (24%) is half the exam and it's where most devs are soft.

On the security side, the recurring themes:

  • IAM roles over hardcoded keys, every time. If an answer option contains an access key in a Lambda env var, it's wrong. The exam is almost dogmatic about this.
  • KMS envelope encryption. Understand that KMS encrypts a data key, the data key encrypts your data, and you store the encrypted data key alongside the ciphertext. Questions love the phrase "encrypt large objects efficiently."
  • Cognito user pools vs identity pools. User pools = authentication (who you are, gives you a JWT). Identity pools = authorization to AWS resources (gives you temp AWS credentials). Mixing these up is the single most common Cognito mistake, and there will be Cognito questions.
  • Secrets Manager vs Parameter Store. Automatic rotation → Secrets Manager. Free and simple config → SSM Parameter Store. Cost-sensitive questions want Parameter Store.

Deployment meant living in the CI/CD services. CodeDeploy deployment configs are a reliable question factory — know canary, linear, and all-at-once, and that Lambda/ECS use traffic-shifting while EC2 uses in-place or blue/green. SAM template.yaml structure, the AWS::Serverless::Function resource, and how sam deploy packages artifacts to S3. Elastic Beanstalk deployment policies (all-at-once, rolling, rolling with additional batch, immutable) show up too — immutable is the "zero downtime, safe rollback, but doubles instances" answer.

I re-tested end of week 2: 79%. Over the line but not comfortable. Comfortable for me is 85%+ on practice, because exam nerves and pilot questions eat a few points.

Week 3 — Troubleshooting, and turning 79% into safe

The final domain (18%) is really "do you understand observability." X-Ray tracing — how you instrument a Lambda with the SDK, what a subsegment is, how sampling rules work. CloudWatch Logs Insights queries. Custom metrics via PutMetricData and the fact that high-resolution metrics cost more. The difference between a CloudWatch metric filter and a subscription filter.

But week 3 was less about new content and more about drilling wrong answers until the patterns stuck. I stopped studying by topic and just did full 65-question timed runs, then spent an hour dissecting every miss. My rule: if I couldn't explain in one sentence why the right answer beat the second-best answer, I didn't actually know it. AWS distractors are plausible on purpose.

I'll be honest about the tools question, since it's the one people ask. I didn't pay for Whizlabs or the Tutorials Dojo mega-bundle this time. ExamCert is $4.99 lifetime access, money-back guarantee if you don't pass — not $300 like Whizlabs/Boson — and for a $150 exam that math is easy. I ran a couple hundred questions across the three weeks and the explanations were enough to close my gaps. Your mileage varies, but I'd rather spend the saved money re-sitting than lock $300 into a subscription I'll cancel.

What I'd cut and repeat

Cut: I over-studied EC2 user-data and AMI trivia. It's barely there on DVA-C02. Cut: memorizing every API Gateway integration type — knowing Lambda proxy vs non-proxy was enough.

Repeat: front-loading Security. Repeat the "explain why the second-best answer is wrong" drill — that's what took me from passing-on-paper to actually confident. And repeat doing a cold baseline in week 1, because it kills the false confidence that you already know Lambda.

If you write AWS code daily, three focused weeks is realistic. If you don't, give it five and spend the extra two on Domains 1 and 2. Either way, do timed full-length sets, not topic quizzes — the pacing (2 minutes a question) is its own skill.

Career-wise: this cert is the standard "I can build on AWS, not just talk about it" signal for backend and full-stack roles, and it pairs well with the Solutions Architect Associate. In the US it tends to sit developers in the $110k–$150k band depending on stack and city — the cert won't hand you that number, but it clears résumé filters that otherwise auto-reject.

Book the exam before week 1. A date on the calendar is the only study hack that has ever worked for me.

Top comments (0)