AWS Certified Developer Associate AWS Certified Developer Associate Free Practice Test — 30 Questions
This practice bank explores key topics for the AWS Certified Developer Associate exam, focusing on serverless architectures, microservices, and operational excellence. Questions emphasize disaster recovery strategies using RDS and DynamoDB, data consistency models, and concurrency control with Lambda and DynamoDB. The bank also covers security best practices such as IAM roles and Secrets Manager, troubleshooting with CloudWatch and X-Ray, and deployment strategies including CI/CD. Behavioral questions assess adaptability and conflict resolution. Master these areas to solidify your understanding of building scalable, resilient, and secure AWS applications.
What this AWS Certified Developer Associate AWS Certified Developer Associate practice set measures
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
Disaster Recovery and Data Consistency
The practice bank tests understanding of disaster recovery (DR) architectures for multi-region setups. It covers RDS cross-Region read replicas for minimal data loss and DynamoDB global tables with conflict resolution. The key decision is balancing strong consistency with performance. Asynchronous replication is preferred when a small data loss window is acceptable. In multi-region active-active replication, eventual consistency can cause stale reads; the solution is using DynamoDB Streams with Lambda to compare timestamps and apply the latest update. The bank also highlights the need for a documented manual or automated failover process.
- RDS cross-Region read replicas provide DR with rapid promotion to standalone instance during Region failure.
- DynamoDB global tables use last-writer-wins for conflict resolution; timestamps are critical.
- Asynchronous replication offers lower latency writes but risks small data loss (RPO).
- Use DynamoDB Streams and Lambda to apply custom conflict resolution logic.
Concurrency and Atomic Operations
The bank explores concurrency control in serverless applications using DynamoDB and Lambda. The core challenge is preventing race conditions when multiple Lambda invocations update the same item. DynamoDB conditional expressions with a version attribute (optimistic locking) ensure atomic updates. For inventory decrements, a conditional expression checks stock >= 1 before updating. The practice bank also addresses throttling and error handling: configuring Lambda with reserved concurrency, using SQS as a buffer, and implementing dead-letter queues (DLQ) for unprocessed messages. Understanding Lambda's retry behavior and SQS visibility timeout is essential.
- Optimistic locking via conditional expressions prevents lost updates in DynamoDB.
- Use a version number or timestamp attribute in item for atomic checks.
- Lambda reserved concurrency throttles excess invocations; DLQ captures failed events.
- SQS standard queue with batch polling and Lambda concurrency limits control processing rate.
Security and Secrets Management
The bank covers secure handling of sensitive data. AWS Secrets Manager is favored over Parameter Store for rotating credentials and fine-grained access control. IAM roles with least privilege are attached to Lambda functions (e.g., s3:GetObject for reading images). For third-party API keys and database strings, Secrets Manager provides automatic rotation. IAM Identity Center centralizes user access across AWS accounts and apps. Data encryption: server-side encryption with KMS for S3, HTTPS for API calls, and ensuring data residency by deploying resources within a single region and disabling cross-region replication.
- AWS Secrets Manager stores and rotates secrets automatically; supports fine-grained IAM policies.
- IAM Identity Center (SSO) centralizes access management and simplifies onboarding/offboarding.
- Lambda execution roles should follow least privilege; use resource-based policies for cross-service access.
- Enforce server-side encryption with KMS for S3 objects; use HTTPS for all external API calls.
- Data residency: deploy all resources in required region; disable cross-region replication.
Serverless Performance and Troubleshooting
This section focuses on diagnosing and solving performance issues in serverless applications. The bank emphasizes using CloudWatch Logs, Metrics, and X-Ray for distributed tracing to pinpoint bottlenecks like DynamoDB throttling or high Lambda latency. For DynamoDB performance, auto-scaling adjusts capacity to traffic patterns. Lambda concurrency: provisioned concurrency keeps execution environments warm to avoid cold starts; reserved concurrency limits concurrent executions. When using SQS triggers, the batch size and concurrency settings impact processing rate. The practice bank also tests understanding of Lambda throttling behavior and the role of DLQs for resilience.
- CloudWatch Logs and Metrics identify error spikes; X-Ray traces request paths across services.
- DynamoDB auto-scaling adjusts Read/Write capacity based on actual consumption.
- Provisioned concurrency pre-warms environment; reserved concurrency limits parallel executions.
- SQS-Lambda integration: batch size and concurrency control processing rate; DLQ for failed messages.
- Intermittent timeouts often due to throttled downstream services; check CloudWatch for capacity exhaustion.
Practice AWS Certified Developer Associate AWS Certified Developer Associate with real flashcards
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Static practice bank
Start the 30-question diagnostic
The complete question bank is embedded in this pre-rendered page. There is no database request or second content download when you begin.
A company operates a mission-critical web application on AWS, utilizing Amazon RDS with a Multi-AZ deployment for its relational database. The application is designed to be highly available within its primary AWS Region. However, to mitigate the risk of a complete Region outage, the development team needs to implement a robust disaster recovery strategy that ensures minimal data loss and rapid recovery in a secondary AWS Region. They have already established an Amazon EC2 Auto Scaling group and an Elastic Load Balancer in the secondary Region, ready to host the application tier. What is the most effective strategy to ensure the database component of the application can be recovered and made operational in the secondary Region with minimal disruption?
Study workflow
Turn one AWS Certified Developer Associate AWS Certified Developer Associate attempt into a study plan
- 1
Implement Disaster Recovery for RDS
Create a cross-Region read replica in the secondary region. Ensure the replica lags within acceptable RPO. Document promotion steps: stop replication, convert to standalone instance. Test failover by simulating primary region failure and verifying application connectivity. Automate promotion with Lambda and CloudWatch alarms for faster recovery.
- 2
Apply Optimistic Locking in DynamoDB
Add a version attribute to every item. When reading, capture the version. Before writing, use a conditional expression: "attribute_exists(version) AND version = :currentVersion". If condition fails, retry by re-reading the item. This prevents overwriting changes from other concurrent writers.
- 3
Secure Secrets in Lambda
Store secrets in AWS Secrets Manager. Grant the Lambda execution role permission to read the secret. In code, use the SDK to retrieve the secret at startup or on demand. Enable automatic rotation for database credentials and API keys. Avoid hardcoding secrets; never log them.
- 4
Debug Lambda Performance Degradation
Enable CloudWatch logs and log structured request IDs. Use X-Ray tracing to analyze service bottlenecks. Check Lambda metrics for throttles, duration, and concurrent executions. Correlate with DynamoDB throttling or S3 latency. Increase provisioned concurrency if cold starts cause spikes.
- 5
Set Up a Dead-Letter Queue for SQS Triggered Lambda
Create an SQS DLQ (standard or FIFO matching source queue). In Lambda configuration, specify the DLQ ARN in DeadLetterConfig. Map source queue to DLQ via event source mapping. Test by sending messages that cause errors; verify they move to DLQ. Monitor DLQ depth for sustained failures.
FAQ
Questions about this exam practice page
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
How does DynamoDB handle concurrent updates to the same item?+
DynamoDB supports optimistic locking using conditional expressions. You read the item, modify it, then write back only if a condition (like a version number) is met. If another write changed the item first, the condition fails and you must retry. This prevents lost updates.
What is the difference between Lambda reserved and provisioned concurrency?+
Reserved concurrency limits the maximum number of concurrent executions for a function. Provisioned concurrency pre-provisions a number of execution environments so they are warm and ready to handle requests immediately, reducing cold start latency.
Why use a dead-letter queue (DLQ) with SQS and Lambda?+
A DLQ captures messages that fail to process after multiple retry attempts. This prevents message loss due to transient errors or permanent failures. You can later analyze DLQ messages to debug and reprocess them after fixing the issue.
How can you ensure data residency in AWS?+
Provision all resources (EC2, S3, RDS) within a specific region. Disable cross-region replication. For DynamoDB, avoid global tables if data must stay in one region. Use S3 lifecycle policies to prevent accidental cross-region copy.
What is the best practice for storing database credentials in Lambda?+
Use AWS Secrets Manager to store and automatically rotate credentials. Grant the Lambda execution role permission to read the secret. Retrieve the secret at function startup from Secrets Manager, never hardcode or store in code.
Build the next review session
Browse another free bank or use the study strategy guide to turn your misses into spaced review.