AWS Certified Developer – Associate: preparation and scheduling guide
AWS Certified Developer – Associate validates the ability to develop, test, deploy, and debug AWS Cloud-based applications. It is aimed at people performing a developer role, especially those deciding whether their current hands-on AWS work is broad enough for an Associate-level exam. Use this guide to decide whether to schedule now, identify the skills that need practice first, and build a study plan around the official developer-focused blueprint rather than around isolated service facts.
Confirm the exam version before building a plan
Start with the official exam guide that matches the exam version shown in your AWS Certification Account. The supplied detailed blueprint is for DVA-C02, while the AWS Certification Exam Guides index currently lists AWS Certified Developer – Associate as DVA-C03. That difference matters because AWS periodically reviews and revises exam guides, services, and skills.
For preparation, use the detailed DVA-C02 guide only as the evidence-backed outline available here, then check the current guide and revisions information before booking or buying study materials. AWS states that guide revisions are published at least one month before changes are reflected on an exam. A calendar built around an outdated version can leave useful time spent on the wrong objectives.
Do not assume that a course, question bank, or video title identifies the correct version. Compare its stated code, domains, and service coverage with the official guide. If those do not align, treat it as supplementary learning material rather than your primary exam plan.
What remains clear from the available official material
The detailed DVA-C02 guide describes a developer-role certification focused on developing, testing, deploying, and debugging AWS Cloud-based applications. It also identifies application optimization, CI/CD-based packaging and deployment, code and data security, and application issue resolution as validated capabilities.
AWS’s certification-guide index describes the Associate level as intended for people in specific technical roles who want to validate technical skills and knowledge. The role emphasis here is development and maintenance of AWS applications, not a broad architecture-design or systems-administration assessment.
Decide whether this is the right certification now
This exam fits a developer who can build and maintain AWS-backed applications and wants to validate that work across delivery, security, and troubleshooting. AWS recommends at least one year of hands-on experience developing and maintaining applications with AWS services, so use that recommendation as a readiness signal rather than as an administrative prerequisite.
You are likely on a sensible path if you can work in at least one high-level programming language, understand application lifecycle management, build functional applications, and use development tools. The official guide also recommends the ability to develop and secure applications through AWS service APIs, the AWS CLI, and SDKs, plus the ability to use a CI/CD pipeline to deploy applications on AWS.
Candidates with strong programming skills but little AWS implementation experience should build a small working application before setting a date. Conversely, candidates who mainly administer infrastructure should check whether their experience includes application code, service integrations, deployment behavior, and debugging. The exam is designed for a developer role, not for every technical AWS role.
Know what not to over-study
The DVA-C02 target-candidate description places several jobs outside the expected scope: designing distributed systems, microservices, database schemas and models; designing and creating CI/CD pipelines; administering IAM users and groups; administering servers and operating systems; and designing AWS networking infrastructure. These boundaries do not mean related services never appear. They mean your study should emphasize using application-facing capabilities rather than preparing for a specialist design or administration role.
A common planning error is spending most study time on broad infrastructure design because it feels familiar or because a service is widely used. Reallocate that time toward the developer actions named in the guide: calling services, handling credentials and secrets appropriately, deploying application artifacts through a pipeline, observing failures, and choosing a practical fix.
What the assessment measures
The official blueprint assesses the lifecycle of an AWS application: create and optimize it, deploy it through CI/CD workflows, protect its code and data, then identify and resolve issues. Prepare for decisions that connect these activities rather than for disconnected definitions of AWS products.
The DVA-C02 content outline has four domains: Development with AWS Services, Security, Deployment, and Troubleshooting and Optimization. The exam guide also notes that candidates might encounter emerging technologies and practices relevant to the Developer – Associate role, so learn underlying patterns instead of relying on a static list of memorized screens or commands.
Build each topic into a scenario: an application accepts a request, persists or retrieves data, triggers work, uses permissions, receives configuration, is released through a pipeline, and emits information that helps diagnose a fault. That mental model turns product knowledge into the decision-making skill the guide describes.
Use the domain weights to allocate study time
For the DVA-C02 guide, Content Domain 1: Development with AWS Services represents 32% of scored content. Give this domain the largest initial share of study because it spans the application behaviors that connect the rest of the blueprint.
For the DVA-C02 guide, Content Domain 2: Security represents 26% of scored content. Study security as an implementation concern: how code, data, identities, temporary access, encryption, and secrets affect an application’s behavior.
For the DVA-C02 guide, Content Domain 3: Deployment represents 24% of scored content. Concentrate on packaging, release flow, and use of CI/CD rather than on designing an enterprise pipeline from scratch, which the target-candidate description places outside scope.
For the DVA-C02 guide, Content Domain 4: Troubleshooting and Optimization represents 18% of scored content. Do not postpone it because its weighting is lower. It requires you to recognize symptoms, inspect the right signal, and select a correction that fits the application constraint.
These weightings describe scored content, not a guarantee of a fixed number of questions in a domain. Use them to prioritize your study blocks, then let missed practice questions and weak hands-on tasks determine which block needs another pass.
Build service knowledge around application flows
Study the in-scope services as parts of working application flows, not as a checklist to memorize. AWS says the in-scope list is non-exhaustive and subject to change, which is a reason to learn why a service is used, what it integrates with, and what operational trade-off a developer must recognize.
A productive core flow can combine Amazon API Gateway, AWS Lambda, Amazon DynamoDB, Amazon S3, IAM, Amazon CloudWatch, and AWS X-Ray. This is not an official required architecture; it is a practical study model for connecting request handling, compute, storage, access control, monitoring, and tracing in one coherent exercise.
Add integration and delivery components once the core flow makes sense. Amazon EventBridge, Amazon SNS, Amazon SQS, AWS Step Functions, AWS CodeBuild, AWS CodeDeploy, and AWS CodePipeline are listed in scope. Make notes about the problem each component solves and the evidence you would inspect when application behavior is wrong.
Organize the official service list into useful study clusters
For serverless and application integration, review AWS Lambda, Amazon API Gateway, AWS AppSync, Amazon EventBridge, Amazon SNS, Amazon SQS, and AWS Step Functions. Focus on request and event paths, error handling, asynchronous work, and the security context in which application code runs.
For application data, cover Amazon DynamoDB, Amazon S3, Amazon Aurora, Amazon RDS, Amazon ElastiCache, Amazon Athena, Amazon Kinesis, and Amazon OpenSearch Service. Avoid treating this as a database-design exam. Instead, ask what an application needs to read, write, protect, process, or observe.
For containers and compute, the in-scope list includes Amazon EC2, AWS Elastic Beanstalk, Amazon ECR, Amazon ECS, and Amazon EKS. For developer preparation, distinguish application packaging and deployment concerns from deep operating-system administration or container-platform design.
For developer workflow, examine AWS Amplify, AWS CloudShell, AWS CodeArtifact, AWS CodeBuild, AWS CodeDeploy, AWS CodePipeline, AWS CDK, AWS CloudFormation, the AWS CLI, and Amazon Q Developer. Do not assume every listed service receives equal emphasis; use the detailed task statements in the applicable official guide to choose depth.
For security and operations, include Amazon Cognito, IAM, AWS KMS, AWS Secrets Manager, AWS STS, AWS WAF, AWS AppConfig, AWS CloudTrail, Amazon CloudWatch, AWS Systems Manager, and AWS X-Ray. The value of this grouping is practical: it links identity, protected values, configuration, audit records, metrics, logs, and traces to application behavior.
Practice the developer decisions behind each domain
Hands-on practice is most useful when every lab answers a developer question: how does the application authenticate, receive configuration, deploy a revision, recover from a failure, or reveal the cause of an error? A lab that merely creates resources is less valuable than one that requires you to verify and correct behavior.
Keep a short decision log while practicing. For each exercise, record the requirement, the AWS service or feature used, the permission or configuration involved, the signal that confirms success, and a likely failure mode. This becomes targeted revision material and exposes gaps that passive reading can hide.
Use only authorized learning materials and your own practice environment. Material claiming to contain live or leaked questions is not a sound way to develop the documented skills, and it can distract from understanding the reasoning needed for multiple-choice and multiple-response decisions.
Development with AWS Services practice
Create one small service-backed feature and follow it end to end. For example, implement an API operation, invoke application logic, store or retrieve an object or record, and return an outcome that a client could use. Then explain what would change if the work needed to be asynchronous or coordinated across multiple steps.
The objective is not to reproduce a particular solution from memory. It is to recognize which service interaction meets a stated application requirement and where credentials, input validation, error handling, or observability belong in the flow.
Security practice
Treat security as code and configuration the application relies on. Practice identifying the identity used by a workload, the permissions it needs, the data it must protect, and the safe mechanism for handling sensitive configuration. Include IAM, AWS STS, AWS KMS, AWS Secrets Manager, and Amazon Cognito in this work because each is on the official in-scope list.
A frequent mistake is studying policies as isolated syntax. Instead, ask whether an application can perform its required action, whether the permission scope is appropriate for that action, and whether credentials or sensitive values are being handled in a way that fits the requirement.
Deployment practice
Use a CI/CD pipeline as a developer would use it: move an application change toward deployment, recognize the artifact and stage involved, and identify what evidence indicates a failed release. AWS lists AWS CodeBuild, AWS CodeDeploy, and AWS CodePipeline as in scope, alongside infrastructure and development tools such as AWS CloudFormation, AWS CDK, and AWS CodeArtifact.
Do not expand this into a full pipeline-design project unless it supports your learning. The official target-candidate description says designing and creating CI/CD pipelines is out of scope. Your emphasis should be packaging and deploying through a pipeline and responding sensibly when the delivery path does not behave as intended.
Troubleshooting and optimization practice
Break a working feature deliberately in a controlled practice account, then use Amazon CloudWatch and AWS X-Ray to investigate. Change one relevant input, permission, configuration value, or deployment artifact at a time so that you can connect a symptom to the correct evidence and correction.
The common trap is jumping to a service change without identifying the fault domain. First decide whether the symptom points to request handling, permissions, configuration, data access, asynchronous processing, or deployment. Then choose the service signal that can confirm or reject that hypothesis.
Follow a staged study roadmap
A reliable roadmap starts with a baseline, builds one connected application model, then alternates focused study with retrieval practice. The order below is a practical recommendation, not an AWS-prescribed timetable; adjust the pace according to your existing AWS experience and the version of the exam you intend to take.
Do not schedule solely because you have completed a course. Schedule when you can explain why an answer is right, identify why plausible alternatives fail the stated requirement, and reproduce key application workflows without step-by-step prompts.
Reserve a final review period for the official guide, missed-topic notes, and a version check. This is where you remove stale assumptions, close gaps in domain coverage, and confirm appointment details rather than starting a large new subject.
Stage 1: establish a baseline and map gaps
Read the target-candidate description, content outline, service references, and out-of-scope boundaries in the applicable official guide. Make four columns for Development with AWS Services, Security, Deployment, and Troubleshooting and Optimization. Under each, rate whether you can explain the task, perform a simple implementation, and troubleshoot a failure.
Prioritize gaps that affect several workflows. For example, weak understanding of IAM, SDK and API use, deployment artifacts, or CloudWatch and X-Ray can impair multiple domains. A focused repair in one of these areas generally has more value than collecting superficial facts about many services.
Stage 2: create a connected core application
Build or diagram a small application flow using services that are in scope, then narrate its lifecycle from a client request through processing and storage to monitoring. Include a deployment path and at least one security decision. Keep the design intentionally modest so that the learning stays centered on application behavior.
At the end of this stage, test yourself without notes: identify the runtime identity, where configuration or secrets would be accessed, what produces observability data, and what a failed deployment could affect. If you cannot explain those links, repeat the exercise with fewer components rather than adding more services.
Stage 3: rotate through focused domain drills
Study Development with AWS Services first because Content Domain 1: Development with AWS Services is 32% of scored content in the DVA-C02 guide. Follow it with Security, where Content Domain 2: Security is 26% of scored content, then deployment and troubleshooting drills that use the same application flow.
During each drill, use a three-part cycle: learn an official task and relevant service behavior, perform or trace a small implementation, then answer scenario-style questions from authorized resources. Review every incorrect response by naming the missing condition in the scenario, not merely by copying the correct choice.
Stage 4: integrate, review, and decide on scheduling
Run mixed review sessions after focused drills. A mixed set forces you to decide whether a scenario is primarily a security, deployment, development, or troubleshooting problem before selecting a solution. That classification step reduces careless errors when several plausible AWS services appear in one question.
Use section-level feedback cautiously if you take practice assessments or later receive exam feedback; the official guide specifically advises caution in interpreting section-level feedback. Treat it as a direction for further review, not as a precise diagnosis of every missed task.
Prepare for the question format and time limit
Expect multiple-choice and multiple-response items, and read the response instruction before evaluating options. AWS describes multiple-choice questions as having one correct response and three distractors; multiple-response questions have two or more correct responses from five or more options.
The official DVA-C02 guide states that the exam has 65 questions in total: 50 questions affect the score and 15 are unscored. The unscored questions are not identified, so give every question the same disciplined attention instead of trying to detect which item may not count.
AWS lists 130 minutes for the exam. Practice working through scenario wording at a controlled pace, flagging only questions that need a second look, and preserving time for a final check of multiple-response selections. Speed without accurate reading is a poor trade-off on questions built around conditions and constraints.
Use a repeatable option-elimination method
First identify the action the question asks for: develop, secure, deploy, diagnose, or optimize. Next underline constraints such as least privilege, application code, asynchronous processing, deployment workflow, or visibility into a failure. Only then compare each option against all stated conditions.
For multiple-response items, evaluate every option independently. Do not stop after finding two answers that seem plausible. A response can be generally useful yet fail the requirement because it addresses the wrong layer, grants unsuitable access, omits a necessary application change, or does not solve the stated symptom.
AWS says unanswered questions are scored as incorrect and there is no penalty for guessing. If time is running short, make your best selection rather than leaving an item blank. This is a test-taking recommendation based on the official scoring rule, not a substitute for preparation.
Plan registration and delivery without last-minute uncertainty
AWS lists Pearson VUE testing centers and online-proctored testing as available options for this exam. Choose based on the setting in which you can meet the applicable appointment requirements and concentrate reliably, then verify the current rules in your AWS Certification Account before committing to a date.
AWS states that appointments can be scheduled through an AWS Certification Account with Pearson VUE. It also says most online-proctored appointments are available 24 hours a day, seven days a week. Availability is not a reason to book prematurely; select a date after confirming the current exam code and after finishing at least one mixed-domain readiness review.
AWS lists the exam cost as USD 150 and notes that additional pricing information is available for foreign-exchange rates. Check the official scheduling path for the current amount, appointment availability, policies, and any location-specific details before paying.
Language and result details
AWS lists English, Japanese, Korean, Brazilian Portuguese, Simplified Chinese, and Latin American Spanish as available languages for this exam. Confirm the language displayed for the particular appointment rather than assuming that every location or delivery option presents the same availability.
For the detailed DVA-C02 guide, results are reported as a scaled score of 100–1,000, and the minimum passing score is 720. This score information belongs to that supplied guide, so confirm the equivalent information in the current guide for the version shown when you schedule.
A short booking checklist
Before selecting an appointment, confirm the current exam code, read the matching official exam guide, choose your delivery option, verify language availability, and review the appointment instructions supplied through the official scheduling process. Keep your preparation plan and the current guide together so that a version change is noticed early.
The day before the appointment, do not attempt to learn an entire new service category. Revisit your decision log, the four domains, common workflow links, and errors from authorized practice. The best final review is specific: it should target the conditions you still confuse, not repeat material you already handle confidently.
Avoid study habits that create false confidence
The most damaging preparation mistake is replacing application reasoning with isolated service memorization. The official scope spans development, security, deployment, and troubleshooting, so an answer often depends on how services interact and on the constraint in the question, not simply on recognizing a product name.
Another mistake is treating the in-scope list as exhaustive or fixed. AWS explicitly says it is non-exhaustive and subject to change. Use it to organize study, but return to the current official guide for the applicable task statements and revisions before the exam.
Finally, distinguish role-level familiarity from readiness. Knowing how to use a service in one project is valuable, but exam readiness requires you to recognize alternative approaches, security implications, deployment behavior, and diagnostic signals under varied requirements.
Common corrections to make now
If your notes list services but not decisions, rewrite each note as a requirement and outcome. For example, record what a component receives, what it produces, what permission it needs, and what signal helps diagnose a problem. This makes revision closer to the official application-focused capabilities.
If you are spending nearly all of your time in one domain, rebalance. Development may deserve the largest share under the DVA-C02 weighting, but Security, Deployment, and Troubleshooting and Optimization are substantial parts of the official outline and should appear throughout your practice.
If every practice error feels like a surprise, categorize it. Was the error caused by missing service knowledge, overlooking a constraint, confusing a developer task with an architecture or administration task, or misreading a multiple-response instruction? Each cause has a different remedy.
Make the next preparation decision
Your next step is to verify the active exam version, compare your experience with the official target-candidate description, and create a four-domain gap list. If the gaps are mostly vocabulary, begin focused study. If they involve building, deploying, securing, or debugging a simple AWS application, prioritize hands-on practice before setting a firm appointment.
Once the foundation is in place, study from the current official guide, use the in-scope service list to structure practice, and schedule through the official AWS Certification process when your readiness review is consistent. This approach keeps the preparation tied to documented capabilities instead of to unverified claims about question content.
AWS certification guides can change as AWS keeps exams aligned with current roles, services, and features. Rechecking the guide close to scheduling is therefore a practical final control, especially where the supplied official sources show different Developer – Associate exam codes.
Conclusion
AWS Certified Developer – Associate preparation should center on the work of an AWS application developer: implement service integrations, secure code and data, use CI/CD deployment workflows, and investigate application problems. Verify the current exam code first, use the matching official guide as the source of truth, and turn every weak topic into a small scenario or hands-on task. When you can reason across all four domains rather than recall services in isolation, scheduling becomes a better-informed decision.
