AWS Certified Developer - Associate (DVA-C02) often gets compared to Solutions Architect Associate, but it's a fundamentally different kind of exam. Where SAA-C03 takes a broad view across architecture, DVA-C02 looks at AWS services through the eyes of a developer who has actually written and deployed code. A carpenter doesn't build a house from a blueprint alone — hands-on experience driving nails in shapes their judgment. This exam is built to favor people who have deployed a Lambda function themselves and actually run into an IAM error before. AWS recommends at least one year of hands-on AWS application development experience before sitting for it, and working through practice questions makes that recommendation obvious fast.
Why This Exam Differs From SAA-C03
An architect draws the overall structure of a building, while the carpenter on-site knows how to actually build it from that drawing. If SAA-C03 is the architect's exam, DVA-C02 is the carpenter's. It fits especially well for backend developers building serverless applications, DevOps engineers configuring their own CI/CD pipelines, and full-stack developers integrating applications through the AWS SDK. Knowing concepts alone isn't enough here — actual hands-on time writing code against the AWS CLI or SDK makes a real difference in how fast you can work through the questions.
Exam Format: 65 Questions, 130 Minutes, and Actual Code Snippets
Like a routine physical, this exam spends 130 minutes running 65 questions across the full breadth of development work. Only 50 are scored; the other 15 are unscored questions AWS is testing for future exams. The passing score is 720 out of 1000, the fee is 150 USD, and certification stays valid for three years. Unlike SAA-C03, IAM policy JSON, SAM templates, and boto3 code snippets show up directly inside question text fairly often, so you need separate practice reading code and spotting exactly what's wrong with it.
Domain 1: Development with AWS Services (32%)
Like snapping LEGO bricks together into a working shape, this domain covers combining multiple AWS services into an application that actually runs. It carries the highest weight, so it can't be treated lightly. The essentials are writing Lambda functions and configuring environment variables and layers, DynamoDB data modeling and query optimization, event-driven architecture using SQS, SNS, and EventBridge, and calling services through the AWS SDK. Five related posts cover this domain: Lambda Function Development and Configuration, DynamoDB Data Modeling and Queries, Data Store Integration and Caching Strategy, Event-Driven Architecture Patterns, and AWS SDK and Messaging/Streaming Development.
Domain 2: Security (26%)
A bank doesn't hand its vault key to just anyone, and this domain covers keeping the credentials and data your application touches safe. The essentials are correctly granting IAM roles and policies at the code level, user authentication and authorization through Cognito, encrypting data at rest and in transit with KMS, and keeping sensitive values out of your code using Secrets Manager and Systems Manager Parameter Store. Three related posts cover this domain in depth: IAM Authentication and Cognito, Encryption Implementation and Key Management, and Sensitive Data and Secrets Management.
Domain 3: Deployment (24%)
Just as a move can carry everything at once or in stages, this domain covers strategies for shipping new code without downtime. The essentials are the difference between Blue/Green and Canary deployments, building CI/CD pipelines with CodePipeline and CodeBuild, managing deployment artifacts through SAM and CloudFormation, and wiring in test automation tools. Four related posts cover this domain: Deployment Strategies and Release Management, Deployment Artifacts and Configuration Management, Configuring a CI/CD Pipeline, and Test Automation and the Development Environment.
Domain 4: Troubleshooting and Optimization (18%)
Just as a car's dashboard warns you about engine trouble before it becomes serious, this domain covers observing how an application actually behaves and diagnosing what's wrong. It carries the lowest weight, but distributed tracing with CloudWatch Logs and X-Ray, performance tuning around Lambda cold starts and memory settings, and publishing custom metrics show up often as hands-on scenario questions. Three related posts cover this domain: Observability and Code Instrumentation, Logs, Metrics, and Trace Analysis, and Lambda and Application Performance Optimization.
A Study Order for Beginners, and Common Mistakes
Walking an unfamiliar city without a map means retracing the same streets twice. If you already develop software but AWS is new to you, start with Domain 1 (development) and get hands-on with Lambda and DynamoDB through the console and CLI, then move into Domain 2 (security) and write an IAM policy JSON yourself instead of just reading about one. From there, build a CI/CD pipeline in Domain 3 (deployment) all the way through an actual deployment, and finish with Domain 4 (troubleshooting) by watching your own application through CloudWatch and X-Ray. The most common mistake is skimming concepts without ever touching a keyboard — this exam leans unusually heavily on code and config files inside its question text, and without hands-on time writing and deploying a SAM template yourself, reading speed on those questions drops sharply. A second common mistake is assuming every IAM error means missing permissions; the real cause is often a resource policy or trust relationship instead, so reading the full error message all the way through matters more here than it seems.
Exam Key Takeaways
"Run code without managing servers" -- AWS Lambda "Single-digit millisecond latency key-value database" -- DynamoDB "Message queue that decouples components" -- Amazon SQS "Delivers notifications to many subscribers at once" -- Amazon SNS "Routes events based on matching patterns" -- Amazon EventBridge "Grants temporary credentials to a service" -- IAM roles "Never hardcode credentials into application code" -- Secrets Manager, Parameter Store "Shifts traffic to a new version gradually" -- Canary deployment "Cuts over to a fully separate new environment" -- Blue/Green deployment "Traces request flow through a distributed system" -- AWS X-Ray "Startup delay problem on a Lambda function" -- cold start
DVA-C02 tests whether you've actually built something, not just whether you know the concept, so the most reliable next step after reading this guide is opening the AWS console and deploying a Lambda function of your own.