AWS Certified Developer - Associate Study Guide

The AWS Certified Developer - Associate credential validates the skills needed to design, build, and maintain applications on Amazon Web Services. It targets software developers who already write code for a living and want formal proof that they can translate that skill into a cloud-native context — working with managed services, writing to AWS APIs and SDKs, and building applications that are secure, scalable, and cost-aware from the start.

This certification sits at the associate tier, one step above the foundational Cloud Practitioner credential but distinct from the operations-focused SysOps Administrator path. It is built for people who spend their days in an IDE rather than a server console: backend engineers, full-stack developers, and anyone responsible for shipping application code that runs on AWS infrastructure.

Why It Matters

For a working developer, this certification is one of the fastest ways to signal cloud fluency to employers and clients without needing years of infrastructure experience. Because AWS remains the dominant cloud provider across enterprise and startup environments alike, holding this credential can open doors to roles explicitly requiring AWS experience, support a case for a raise or promotion, and make a resume stand out in a crowded applicant pool.

Beyond the resume line, preparing for the exam forces a developer to learn AWS services more rigorously than typical on-the-job trial and error would. Candidates come away with a working mental model of how compute, storage, messaging, and identity services fit together — knowledge that pays off directly in day-to-day application design decisions, code reviews, and architecture discussions long after the exam is passed.

The AWS Certified Developer - Associate (DVA-C02) exam is a timed, proctored assessment designed to be completed within a single sitting. Understanding its structure ahead of time helps candidates pace themselves and avoid surprises on exam day.

• The exam contains 65 questions, presented as multiple choice and multiple response items.
• Of those questions, 50 are scored, while 15 are unscored questions AWS uses to evaluate future exam content and do not count toward the candidate's result.
• Candidates are given 130 minutes to complete the exam, which works out to roughly two minutes per question when the full time is used.
• The minimum passing score is 720 on a scaled range of 100 to 1,000, so raw correct-answer counts do not map directly to the reported score.
• The exam costs 150 USD to register.
• Once earned, the credential is valid for 3 years before recertification is required.

Scheduling and Delivery

Exams are offered through Pearson VUE, and candidates schedule their appointment through Pearson VUE's scheduling system via their AWS Certification account. There are two delivery options: sitting the exam at a physical Pearson VUE test center, or taking it remotely as an OnVUE online proctored exam from a private space that meets the proctoring requirements.

Most online-proctored exam appointments are available 24 hours a day, 7 days a week, which gives candidates considerable flexibility in choosing a test time. If plans change, each exam appointment can only be rescheduled twice, and candidates can reschedule up to 24 hours before the scheduled exam time — waiting any longer typically forfeits the registration fee, so it pays to confirm availability well before the deadline.

The exam guide defines 4 content domains, each covering a distinct slice of what a developer needs to know to build and run applications on AWS. Understanding how heavily each domain is weighted helps prioritize study time toward the areas most likely to appear on the exam.

Domain 1: Development with AWS Services (32%)

Content Domain 1: Development with AWS Services accounts for 32% of scored content, making it the single largest domain. It covers writing code that interacts with core AWS services such as compute, storage, and database offerings, using the AWS SDKs, and applying appropriate design patterns for cloud-native applications, including serverless architectures and event-driven designs.

Domain 2: Security (26%)

Content Domain 2: Security accounts for 26% of scored content. This domain focuses on implementing authentication and authorization mechanisms, managing sensitive data and encryption, and applying secure coding and credential-management practices when an application talks to AWS resources.

Domain 3: Deployment (24%)

Content Domain 3: Deployment accounts for 24% of scored content and covers preparing application artifacts for deployment, understanding deployment strategies such as blue/green and canary releases, and working with continuous integration and delivery tooling on AWS.

Domain 4: Troubleshooting and Optimization (18%)

Content Domain 4: Troubleshooting and Optimization accounts for 18% of scored content. It emphasizes root-causing application issues using logging and monitoring tools, and optimizing applications for performance and cost once they are running in production.

Together these four domains reflect the full lifecycle of an AWS-hosted application — building it, securing it, shipping it, and keeping it healthy — so a well-rounded study plan should touch all four rather than concentrating narrowly on the highest-weighted domain alone.

Most working developers with some prior AWS exposure can prepare in roughly six to eight weeks of consistent part-time study. The plan below breaks that time down by topic area rather than a strict calendar, so it can be compressed or stretched depending on prior experience.

Weeks 1-2: Foundations and Development with AWS Services

Start with the highest-weighted domain first. Get hands-on with core compute and storage services, practice writing to their APIs using an AWS SDK, and build at least one small serverless application end to end. Because this domain covers close to a third of the exam, spending disproportionate time here early pays off.

Weeks 3-4: Security

Move into identity and access management, focusing on how applications authenticate to AWS services and how credentials should be handled in code rather than hardcoded. Practice setting up least-privilege permissions and encrypting data both at rest and in transit.

Week 5: Deployment

Study deployment strategies and continuous delivery pipelines. Work through at least one full deployment cycle for a sample application, comparing rolling, blue/green, and canary approaches so the tradeoffs are intuitive rather than memorized.

Week 6: Troubleshooting and Optimization

Focus on reading logs and metrics to diagnose failures, then shift to cost and performance tuning. This domain often rewards practical debugging experience more than pure memorization.

Final Week: Practice and Review

1. Take full-length timed practice exams to build stamina for the 130-minute session.
2. Review every missed question and trace it back to the specific domain and service.
3. Revisit flashcards and glossary terms for services that still feel unfamiliar.
4. Do a final light pass across all four domains rather than cramming any single one.

Throughout the plan, favor hands-on practice over passive reading — building small projects in an AWS account cements concepts far better than reading documentation alone.

Before the Exam

• Confirm delivery details ahead of time — whether testing at a Pearson VUE center or via OnVUE online proctoring — including ID requirements and, for online exams, workspace and connectivity checks.
• Get a full night's sleep and eat beforehand; a 130-minute exam demands sustained focus.
• Arrive or log in early rather than rushing in at the last minute, since check-in and identity verification take time.

During the Exam

• Read each question fully before looking at the answer choices — AWS exam questions are frequently scenario-based, and the correct answer often hinges on a detail buried in the middle of the prompt.
• Flag uncertain questions and move on rather than getting stuck; with 65 questions to complete, spending too long on any one item eats into time needed elsewhere.
• Watch for answer choices that are technically valid AWS services but do not fit the specific constraints described in the scenario, such as cost, latency, or operational overhead requirements.
• Eliminate obviously wrong answers first, even when unsure of the exact right answer — narrowing from four choices to two meaningfully improves the odds of a correct guess.

Common Mistakes to Avoid

• Studying services in isolation instead of understanding how they interact within a typical application architecture.
• Neglecting the Security and Troubleshooting domains in favor of over-preparing for Development, even though each domain contributes meaningfully to the overall score.
• Relying solely on memorized service names without practicing the actual SDK calls and CLI commands referenced in real scenarios.
• Skipping timed practice runs, which can lead to running out of time on exam day even when the underlying knowledge is solid.

Preparing for the AWS Certified Developer - Associate exam does not require expensive bootcamps or paid courses to be effective. A well-organized set of free study resources can cover most of what is needed to build confidence across all four content domains.

Practice Questions

Scenario-based practice questions modeled on the exam's multiple choice and multiple response format are one of the most effective ways to prepare, since they train the specific skill the real exam tests: parsing a realistic application scenario and selecting the best-fit AWS service or configuration under time pressure. Working through practice questions organized by content domain also makes it easy to spot which domain needs more attention before test day.

Flashcards

Flashcards are well suited to the kind of rapid-recall knowledge the exam expects, such as service limits, default configurations, and which service fits which use case. Reviewing flashcards in short, frequent sessions throughout the study period reinforces this recall knowledge more durably than a single long cram session.

Glossary

A glossary of AWS terminology and service names helps close gaps for candidates who are strong developers but newer to AWS-specific vocabulary. Quickly looking up an unfamiliar term while working through practice questions keeps study sessions moving without derailing into lengthy documentation searches.

Used together, these three resource types map naturally onto the study plan above: practice questions to test domain-level readiness, flashcards for spaced recall of specific facts, and a glossary to fill vocabulary gaps as they surface.