# Amazon DynamoDB

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/amazon-dynamodb

> Amazon DynamoDB is a fully managed NoSQL database service provided by Amazon Web Services (AWS) that offers fast and predictable performance with seamless scalability for applications that need consistent, single-digit millisecond latency at any scale.

Practice exams covering Amazon DynamoDB: [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional), [MLA-C02 (beta) AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## Free Amazon DynamoDB tools

- [DynamoDB JSON to JSON Converter](https://blowstack.com/tools/dynamo-db-converter): Convert DynamoDB JSON to plain JSON and back, and get the code to write the items.
- [DynamoDB Item Size and RCU/WCU Calculator](https://blowstack.com/tools/dynamodb-item-size-calculator-and-capacity-simulator): Calculate the size of an item and the RCUs and WCUs it consumes.
- [DynamoDB Expression Builder](https://blowstack.com/tools/dynamodb-expression-builder): Build key condition, filter and update expressions with their placeholders.
- [DynamoDB TTL and AWS Timestamp Converter](https://blowstack.com/tools/dynamodb-ttl-converter): Convert TTL epoch timestamps to dates and back, and catch values that never expire.
- [DynamoDB Pricing and Capacity Calculator](https://blowstack.com/tools/dynamodb-pricing-calculator): Estimate a table's monthly cost, on-demand and provisioned side by side.
- [DynamoDB Emulator](https://blowstack.com/tools/dynamodb-emulator): Try tables, Query, Scan and indexes on a simulated DynamoDB in your browser, with the partitions and capacity each request uses.

## 13 key features of Amazon DynamoDB

Amazon DynamoDB offers a fully managed, scalable NoSQL database with seamless integration with AWS services, global data replication, event-driven programming, built-in security, high performance, enterprise-level transaction support, along with backup and adaptive capacity features.

1. **Fully Managed NoSQL Database**: Amazon DynamoDB is a fully managed NoSQL database service that provides fast and predictable performance with seamless scalability.
2. **Scalability**: DynamoDB allows you to scale your databases up or down without downtime or performance degradation, accommodating for spikes in traffic and ensuring efficiency with provisioned and on-demand capacity modes.
3. **Integrated with AWS**: DynamoDB is deeply integrated with other AWS services, such as Lambda, Elastic MapReduce, Data Pipeline, and more, facilitating complex applications and workflows.
4. **Global Tables**: DynamoDB's Global Tables feature enables you to have fully replicated tables across different AWS regions, offering low-latency access to data for geographically distributed applications.
5. **Event-Driven Programming**: With DynamoDB Streams, you can enable event-driven programming and trigger AWS Lambda functions in response to data changes, which facilitates real-time processing and analytics.
6. **Built-in Security**: DynamoDB offers built-in security features such as encryption at rest, fine-grained access control using AWS IAM, and VPC Endpoints to keep data secure and regulate access.
7. **High Performance and Durability**: The service is designed for high performance with single-digit millisecond response times and built-in fault tolerance, replicating data across multiple zones for high availability and data durability.
8. **Enterprise-Ready**: DynamoDB supports ACID transactions, enabling multiple get and put operations across one or more tables in a single, atomic transaction, which is integral for enterprise-level applications requiring complex transactions.
9. **Backup and Restore**: DynamoDB allows you to easily create backups of your tables for archiving or restore your data to any point in time over the last 35 days, which helps in disaster recovery and compliance.
10. **Adaptive Capacity**: This feature automatically adjusts to your applicationâs traffic patterns to maintain steady and predictable performance, providing seamless handling of uneven workloads and hot keys.
11. **Time to Live**: Time to Live (TTL) automatically deletes items from a DynamoDB table after a specified duration.
12. **Global Secondary Indexes**: Global secondary indexes let applications query a table using partition and sort keys that differ from the table's own partition and sort keys.
13. **Provisioned Capacity Auto Scaling**: DynamoDB uses AWS Application Auto Scaling to dynamically adjust provisioned throughput capacity in response to traffic patterns.

## Where Amazon DynamoDB is used

Amazon DynamoDB is utilized for a variety of use cases including gaming leaderboards, IoT data storage, web session storage, e-commerce shopping carts, and mobile backends, thanks to its high scalability, performance, and ease of management.

1. **Gaming Leaderboards**: Amazon DynamoDB is used for creating high-performance, scalable gaming leaderboards that can handle high throughput and massive storage needs for real-time player rankings.
2. **IoT Data Storage**: It serves as a repository for the vast amounts of data generated by IoT devices, providing fast, flexible, and reliable storage that can accommodate the rapid growth and unpredictable nature of IoT data streams.
3. **Session Storage for Web Applications**: DynamoDB offers a fast and stateless session storage solution for web applications, allowing for low-latency data access, seamless scalability, and simplified management of session data.
4. **E-commerce Shopping Carts**: Online retailers leverage DynamoDB to manage shopping cart data, ensuring quick response times and consistent performance during spikes in customer traffic or large-scale sales events.
5. **Mobile Backends**: Developers use DynamoDB to power the backend of mobile applications, taking advantage of its fully managed features, built-in security, and the ability to handle large volumes of low-latency data access requests.

## How Amazon DynamoDB is priced

Amazon DynamoDB offers a range of pricing models including Provisioned Throughput, On-Demand Capacity, Reserved Capacity, Data Transfer, and charges for additional features like Streams and Global Tables.

- **Provisioned Throughput Pricing**: This pricing model allows customers to specify the number of reads and writes per second that their application requires. Customers pay for the throughput they provision in terms of read capacity units (RCUs) and write capacity units (WCUs).
- **On-Demand Capacity Pricing**: With on-demand capacity, there is no need to provision throughput in advance. Customers pay for the read and write requests they actually consume on a per-request basis.
- **Reserved Capacity Pricing**: Customers can reserve capacity for their DynamoDB tables and benefit from significant savings over the standard provisioned throughput pricing. This option requires a one-time upfront payment for a term of one or three years, in exchange for a lower rate on the specified capacity during the term.
- **Data Transfer Pricing**: Data transfer in AWS DynamoDB is free for incoming data and for data transfer between DynamoDB and other AWS services within the same region. Outgoing data transfers are charged beyond the free tier limit.
- **Additional Feature Pricing**: DynamoDB charges for additional features such as DynamoDB Streams, backup and restore capabilities, and global tables. These features are priced separately from the capacity costs, based on the amount of data processed or stored.
- **Data Storage Pricing**: Storage charges depend on the table class and the continuously measured size of the table. Billable size includes the raw data bytes and per-item storage overhead that depends on the enabled features.
- **Database Savings Plans**: Database Savings Plans can reduce DynamoDB costs by up to 18% in exchange for committing to a consistent amount of usage over a one-year term.
- **Warm Throughput Pre-Warming Pricing**: Proactively increasing warm throughput incurs a one-time fee at the regional rate of one RCU for each unit increase in read warm throughput and one WCU for each unit increase in write warm throughput. The charge applies to both Standard and Standard-IA tables.
- **Vector Search Pricing**: Vector indexing and similarity search are charged separately from the underlying table. Vector writes are billed by GB written into the index, including projected non-vector attributes; searches are billed by GB processed and returned; vector index storage is billed per GB-month.
- **Change Data Capture Pricing**: Change data capture to Amazon Kinesis Data Streams or AWS Glue is billed at one CDC unit for each write of up to 1 KB. Destination Kinesis Data Streams or AWS Glue charges also apply.
- **Amazon S3 Export Pricing**: Full exports are charged by the size of the table data and local secondary indexes exported; incremental exports are charged by the data processed from PITR backups. Filtering has no additional charge. An export selecting a single partition key value with a key condition is charged on matched data, subject to a 10 MB minimum per export. S3 storage and PUT request charges also apply.
- **Amazon S3 Import Pricing**: Imports from Amazon S3 are charged based on the uncompressed source file size. S3 storage and GET request charges also apply.
- **DynamoDB Accelerator Pricing**: DynamoDB Accelerator (DAX) clusters incur hourly charges based on the nodes used; cache hits can offset part of this cost by reducing reads from DynamoDB tables.
- **Bulk Put Items Pricing**: Bulk put items is billed by GB written to the table and its secondary indexes, with rates depending on the target table class and the Standard or Accelerated performance tier. Vector index writes are billed separately at the vector bulk put rate and support the Standard tier only. Billing has a 1 KB minimum per item, applied independently to the base table and each index write.

## Services Amazon DynamoDB works with

- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: AWS Lambda allows you to run code in response to changes in your DynamoDB tables. You can configure triggers to run your Lambda functions whenever item-level changes in the table occur.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Amazon DynamoDB can export table data to Amazon S3 for backup and archiving purposes. The integration also allows importing data from S3 into DynamoDB tables.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Amazon CloudWatch monitors DynamoDB, providing metrics and logs for tables. You can set alarms based on thresholds for activities such as read/write capacity.
- **[Amazon API Gateway](https://blowstack.com/tools/cloud-services-hub/amazon-api-gateway)**: DynamoDB can serve as the backend for API Gateway REST APIs through AWS service integrations. Request and response mappings let an API read or write table items without an intervening Lambda function.
- **[Amazon Athena](https://blowstack.com/tools/cloud-services-hub/amazon-athena)**: DynamoDB tables can be queried with SQL through Athena's DynamoDB federated query connector. Queries can join DynamoDB records with data in other supported sources.
- **[Amazon CloudSearch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudsearch)**: DynamoDB tables can supply documents for a CloudSearch search domain through CloudSearch's DynamoDB data-loading workflow. This loads table data for indexing rather than continuously replicating subsequent changes.
- **[Amazon Cognito](https://blowstack.com/tools/cloud-services-hub/amazon-cognito)**: DynamoDB applications can use temporary AWS credentials issued through Cognito identity pools. IAM policies can restrict each authenticated user's access to particular tables, operations, or items identified by their partition keys.
- **[Amazon DevOps Guru](https://blowstack.com/tools/cloud-services-hub/amazon-devops-guru)**: DynamoDB tables can be monitored by DevOps Guru for operational anomalies, such as unusual throttling or latency. Its insights correlate resource behavior and provide recommendations for investigating problems.
- **[Amazon EMR](https://blowstack.com/tools/cloud-services-hub/amazon-emr)**: DynamoDB tables can be read and written by Hive jobs on EMR using the DynamoDB connector. This supports bulk processing and transfers between DynamoDB and other data stores accessible to the cluster.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: DynamoDB Streams can be used as an EventBridge Pipes source to filter, optionally enrich, and deliver item-change events to a target. Sending those events to an EventBridge event bus enables routing and fan-out to multiple consumers.
- **[Amazon Kinesis Data Streams](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-streams)**: DynamoDB can publish item-level changes directly to a Kinesis data stream for downstream processing. Separately, Kinesis Client Library applications use DynamoDB tables to coordinate workers and store leases and checkpoints.
- **[Amazon Managed Service for Apache Flink](https://blowstack.com/tools/cloud-services-hub/amazon-managed-service-for-apache-flink)**: DynamoDB tables can receive results from Managed Service for Apache Flink applications through the Flink DynamoDB sink connector. For example, an application can write continuously updated aggregates into a table for low-latency application reads.
- **[Amazon Managed Streaming for Apache Kafka](https://blowstack.com/tools/cloud-services-hub/amazon-managed-streaming-for-apache-kafka)**: DynamoDB data can be replicated into MSK topics using the DynamoDB source connector for Kafka Connect. The connector supports loading table data and capturing subsequent changes for Kafka consumers.
- **[Amazon OpenSearch Service](https://blowstack.com/tools/cloud-services-hub/amazon-opensearch-service)**: DynamoDB's zero-ETL integration with OpenSearch Service uses OpenSearch Ingestion to load table data and replicate subsequent changes. This makes DynamoDB records available for full-text search and analytics without adding search workloads to the table.
- **[Amazon QuickSight](https://blowstack.com/tools/cloud-services-hub/amazon-quicksight)**: DynamoDB data can be visualized in QuickSight through Athena's DynamoDB federated query connector. QuickSight uses Athena queries to build datasets and dashboards from the table's records.
- **[Amazon Redshift](https://blowstack.com/tools/cloud-services-hub/amazon-redshift)**: DynamoDB zero-ETL integrations replicate table data into Redshift for SQL analytics. Initial data loading and ongoing change replication let analytical workloads operate separately from production DynamoDB requests.
- **[Amazon SageMaker](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker)**: DynamoDB offers a zero-ETL integration with SageMaker Lakehouse that replicates table data and subsequent changes for analytics and machine learning. This makes operational data available in the lakehouse without maintaining a custom extraction pipeline.
- **[Amazon SageMaker Data Wrangler](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker-data-wrangler)**: DynamoDB tables can be imported into SageMaker Data Wrangler for data preparation. The import workflow uses a DynamoDB export to S3, allowing transformations without consuming the table's read capacity.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: DynamoDB supports VPC endpoints so workloads can access the service without an internet gateway or NAT device. Gateway endpoint policies can restrict which DynamoDB resources and operations are accessible through the endpoint.
- **[AWS Amplify](https://blowstack.com/tools/cloud-services-hub/aws-amplify)**: DynamoDB tables provide persistent storage for Amplify Data backends. Amplify can provision the tables, GraphQL API, and authorization rules needed to expose application models to clients.
- **[AWS AppSync](https://blowstack.com/tools/cloud-services-hub/aws-appsync)**: DynamoDB is a native AppSync data source for GraphQL resolvers. Resolvers can perform reads, writes, queries, and transactions against tables while applying API authorization rules.
- **[AWS Audit Manager](https://blowstack.com/tools/cloud-services-hub/aws-audit-manager)**: DynamoDB configuration and activity can contribute automated evidence to Audit Manager assessments through supported AWS API, AWS Config, and CloudTrail evidence sources. This helps document controls such as table encryption and backup protection.
- **[AWS Auto Scaling](https://blowstack.com/tools/cloud-services-hub/aws-auto-scaling)**: DynamoDB uses Application Auto Scaling to adjust provisioned read and write capacity for tables and global secondary indexes. Target-tracking policies can maintain a chosen utilization level, while scheduled actions prepare capacity for predictable traffic.
- **[AWS Backup](https://blowstack.com/tools/cloud-services-hub/aws-backup)**: DynamoDB tables can be protected by AWS Backup plans with centralized schedules and retention policies. Advanced DynamoDB backup features support capabilities such as cross-account and cross-Region backup copies.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: DynamoDB tables and global tables can be provisioned as CloudFormation resources. Templates can define indexes, capacity settings, encryption, streams, and recovery settings alongside the applications that use them.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: DynamoDB integrates with CloudTrail to record management API activity and, when configured, table-level data events. These records support investigations into actions such as table configuration changes or item access.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: DynamoDB resource configurations can be recorded and evaluated by AWS Config. Managed rules can check settings such as encryption, point-in-time recovery, and automatic scaling.
- **[AWS Data Pipeline](https://blowstack.com/tools/cloud-services-hub/aws-data-pipeline)**: DynamoDB tables can be sources or destinations in Data Pipeline workflows. DynamoDB-specific data nodes and activities support tasks such as exporting table data to S3 or importing data into a table.
- **[AWS Database Migration Service (AWS DMS)](https://blowstack.com/tools/cloud-services-hub/aws-database-migration-service-(aws-dms))**: DynamoDB is a supported DMS migration target. DMS can load source database records into DynamoDB tables and apply ongoing changes, using mapping rules to shape the target items.
- **[AWS Direct Connect](https://blowstack.com/tools/cloud-services-hub/aws-direct-connect)**: DynamoDB public endpoints can be reached over a Direct Connect public virtual interface. This lets on-premises applications send DynamoDB traffic over a dedicated network connection rather than their internet connection.
- **[AWS Elastic Beanstalk](https://blowstack.com/tools/cloud-services-hub/aws-elastic-beanstalk)**: DynamoDB tables can be declared in Elastic Beanstalk configuration files as supporting environment resources. Elastic Beanstalk provisions those tables with the environment, allowing the application and its database infrastructure to be deployed together.
- **[AWS Fault Injection Service](https://blowstack.com/tools/cloud-services-hub/aws-fault-injection-simulator-(aws-fis))**: DynamoDB global tables support Fault Injection Service experiments that temporarily pause replication between Regions. These experiments test how applications handle delayed replication and regional failover conditions.
- **[AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue)**: DynamoDB tables can be discovered by Glue crawlers and read or written by Glue ETL jobs. The DynamoDB export connector uses table exports to S3 for large extractions without consuming read capacity.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: DynamoDB uses IAM policies to authorize table, index, stream, and item operations. Fine-grained conditions can restrict access by partition key or attribute, and table resource policies can grant access to specified principals.
- **[AWS IoT Core](https://blowstack.com/tools/cloud-services-hub/aws-iot-core)**: DynamoDB tables can receive device messages through IoT Core rules using DynamoDB or DynamoDBv2 rule actions. A rule can transform an incoming message and store it as an item without custom ingestion code.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: DynamoDB uses KMS keys to encrypt table data at rest, including indexes, streams, and backups. Choosing a customer managed key gives control over key policies and the key's lifecycle.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: DynamoDB supports PrivateLink interface endpoints for private access through endpoint network interfaces. Clients use the endpoint-specific DNS name, enabling access from connected networks without using DynamoDB's public endpoint.
- **[AWS Resilience Hub](https://blowstack.com/tools/cloud-services-hub/aws-resilience-hub)**: DynamoDB tables can be included in Resilience Hub application assessments. Resilience Hub evaluates their configuration against recovery objectives and recommends improvements to backup and regional resilience.
- **[AWS Resource Groups and Tag Editor](https://blowstack.com/tools/cloud-services-hub/aws-resource-groups-and-tag-editor)**: DynamoDB tables can be organized into tag-based resource groups and have their tags managed through Tag Editor. This supports grouping tables by application, owner, or environment for operational management.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: DynamoDB configurations are checked by Security Hub security controls for protections such as point-in-time recovery and automatic scaling. Failed checks produce findings that can be reviewed alongside other security issues.
- **[AWS Security Token Service (AWS STS)](https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts))**: DynamoDB accepts requests signed with temporary credentials issued by STS. Assumed roles and session policies let applications receive time-limited access to selected tables and operations instead of using long-lived credentials.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: DynamoDB has an optimized Step Functions integration for getting, putting, updating, and deleting items directly from workflow states. Workflows can use these operations to track processing status without a Lambda function for each database request.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: DynamoDB maintenance tasks can be automated with Systems Manager Automation runbooks. AWS-provided runbooks support operations such as creating table backups and enabling point-in-time recovery.
- **[AWS Trusted Advisor](https://blowstack.com/tools/cloud-services-hub/aws-trusted-advisor)**: DynamoDB tables are covered by Trusted Advisor checks for capacity and resilience practices. Recommendations can identify opportunities to improve capacity configuration or enable protection such as point-in-time recovery.
- **[AWS X-Ray](https://blowstack.com/tools/cloud-services-hub/aws-x-ray)**: DynamoDB requests made through X-Ray-instrumented AWS SDK clients appear as downstream calls in distributed traces. These trace segments help identify database request latency, errors, and throttling within an application's request path.

## Amazon DynamoDB exam questions

Real practice exam questions on Amazon DynamoDB, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

An online retailer needs to store shopping carts and retrieve each cart by its unique cart ID. Traffic varies sharply during promotions. The retailer wants a serverless NoSQL key-value database that provides single-digit millisecond performance without requiring database instance management. Which solution best meets these requirements?

**Correct answer:** Amazon DynamoDB with on-demand capacity

**Explanation:** Amazon DynamoDB is a serverless NoSQL database that supports key-value access and single-digit millisecond performance. On-demand capacity automatically accommodates changing request traffic without requiring database instance management or provisioned throughput planning.

### Question 2 (MLA-C02 (beta))

**Question:**

A company ingests training observations into an Amazon DynamoDB table in provisioned capacity mode. Each observation creates one new item of 2.4 KiB by using a nontransactional write. The table has no secondary indexes, and writes are evenly distributed across partition keys.

An upcoming scheduled data collection event will increase ingestion from 200 to 2,000 observations per second almost immediately and sustain that rate for 30 minutes. The table currently has 1,000 provisioned write capacity units (WCUs). The ML engineer must prepare capacity before the event so that peak ingestion consumes no more than 75% of provisioned write capacity, without relying on burst capacity or reactive scaling. Applicable service quotas allow the required increase.

Which capacity plan meets these requirements with the least provisioned write capacity during the event?

**Correct answer:** Increase the table to 8,000 WCUs before the event and return it to its normal capacity afterward.

**Explanation:** DynamoDB rounds each 2.4-KiB item up to 3 KiB for write capacity calculations, so peak ingestion requires 2,000 × 3 = 6,000 WCUs. To keep utilization at or below 75%, the table needs at least 6,000 / 0.75 = 8,000 provisioned WCUs. Increasing capacity before the event avoids dependence on reactive scaling.

### Question 3 (SAP-C03)

**Question:**

A sports media company stores immutable match summaries in Amazon DynamoDB. An API running across multiple Availability Zones serves the summaries through a shared Amazon ElastiCache for Valkey cache. Each newly published summary receives thousands of reads within seconds. The first reads after publication currently miss the cache and cause a spike in DynamoDB read traffic.

Each publication request includes a unique summary ID and an immutable payload. Publishers retry timed-out requests with the same ID and payload. A notification service starts directing readers to a summary only after the publication API returns success. The company can accept increased publication latency, but a successful publication must mean that the summary is durably stored and already available in the cache. Cache entries might expire or be evicted later, so reads must still support cache misses. The database and cache do not support a shared transaction.

Which implementation meets these requirements, including when a cache operation fails after a database write succeeds?

**Correct answer:** Conditionally insert the summary into DynamoDB, then synchronously populate ElastiCache before returning success. If the cache operation fails, leave the request retryable. On retry, verify that an existing DynamoDB item has the same payload and attempt cache population again before returning success. Continue loading from DynamoDB on read misses.

**Explanation:** This implements write-through caching in the application: persistence and cache population must both complete before publication succeeds. The stable summary ID supports idempotent retries, but an existing database item does not cause cache population to be skipped. A cache failure does not require rolling back the durable item. Cache-aside reads handle later expiration or eviction.

### Question 4 (SOA-C03)

**Question:**

A company uses an Amazon DynamoDB global table with replicas in two AWS Regions. Point-in-time recovery is enabled on both replicas. A faulty deployment corrupts application data, and the corrupted writes propagate to both Regions before engineers stop all application writes.

The company identifies a safe recovery timestamp within the retained recovery window and accepts losing all changes after that timestamp. Service must resume in both Regions within a 90-minute RTO. The company does not want to maintain an additional global table between incidents.

Recovery exercises show that restoring one table to the safe timestamp, adding a replica in the other Region, validating both tables, and updating both regional applications takes 70 minutes. Required permissions and service quotas are already configured.

Which recovery procedure should a CloudOps engineer use?

**Correct answer:** Restore one replica to the safe timestamp as a new table, add a global table replica in the other Region, validate the recovered deployment, and configure both applications to use the new tables before resuming writes.

**Explanation:** DynamoDB point-in-time recovery creates a new, independent table rather than restoring the original global table topology. Adding a replica establishes the replacement global table. Validating and switching both applications before resuming writes avoids using the corrupted originals. The tested 70-minute workflow meets the 90-minute RTO without maintaining an additional global table between incidents.

### Question 5 (AIP-C01)

**Question:**

A manufacturer runs a sourcing assistant that uses Amazon Bedrock Converse and stores conversation history in Amazon DynamoDB. A buyer can fork an existing negotiation into a what-if conversation to explore a different supplier. The fork must inherit the negotiation context as it existed when the fork was created. The main negotiation can continue independently, and its subsequent changes must not silently alter the what-if conversation.

All relevant messages fit within the model's context window. What-if messages must remain available for audit but must not influence the main negotiation unless the buyer explicitly accepts a proposed change. Acceptance must carry forward only the selected change, not rejected alternatives discussed in the what-if conversation.

Which conversation-memory design meets these requirements?

**Correct answer:** Give each fork a separate conversation identifier and record its parent's immutable message boundary. Build its model context from parent history through that boundary plus its own messages. On explicit acceptance, append only the selected change to the main negotiation's context; retain the fork transcript separately for audit.

**Explanation:** The recorded boundary preserves the inherited context at fork creation, while separate branch messages prevent cross-conversation contamination. Explicitly transferring only the selected change updates the main negotiation without importing rejected alternatives. Retaining the separate transcript satisfies audit requirements.

### Question 6 (DEA-C01)

**Question:**

A collaboration platform is designing an Amazon DynamoDB table to store team memberships. The application must list user IDs and membership roles for a team, and list team IDs and membership roles for a user. Each page of either list must be retrieved with one Query request, without scans or additional item reads. After a membership creation or deletion completes successfully, subsequent reads in either direction must reflect the change. Teams can have hundreds of thousands of members, and users can belong to many teams.

Which data model best meets these requirements?

**Correct answer:** Store reciprocal membership items: one with partition key TEAM#<teamId> and sort key USER#<userId>, and another with partition key USER#<userId> and sort key TEAM#<teamId>. Include the role in both items. Create or delete both items with TransactWriteItems, and use strongly consistent table queries for both access patterns.

**Explanation:** Reciprocal items denormalize the relationship to support both access patterns directly through the table's primary key. Each strongly consistent Query can return the requested IDs and roles without additional reads. Transactional writes ensure that both representations are created or deleted atomically, and separate membership items avoid unbounded growth within a single item.

### Question 7 (DOP-C02)

**Question:**

A company uses an Amazon DynamoDB table with a global secondary index (GSI) to process event registrations. The table must remain in provisioned capacity mode. Independent target tracking policies manage write capacity for the table and the GSI at 70% utilization. Their maximum capacities are sufficient for peak traffic, but their minimum capacities support only normal traffic.

At 09:00 UTC each weekday, registration traffic increases within seconds and remains high for 20 minutes. Monitoring shows write throttling on both the table and the GSI before automatic scaling catches up. Partition keys are evenly distributed, and no service quotas are being reached. Load tests have established the write capacity required for each resource during the event.

A DevOps engineer must have sufficient capacity available before registration opens, retain demand-based scaling, and allow capacity to decrease after the event without maintaining custom scaling code. Which solution meets these requirements?

**Correct answer:** Create recurring Application Auto Scaling scheduled actions for the table and GSI write-capacity scalable targets. Raise each minimum to its load-tested event capacity sufficiently before 09:00 UTC, and restore the normal minimums after the event. Retain target tracking and maximums that accommodate the raised minimums.

**Explanation:** Scheduled actions can raise minimum provisioned capacity before a predictable surge, avoiding reliance on reactive scaling for the initial demand. Table and GSI write capacities are managed independently, so both need scheduled capacity floors. Restoring the normal minimums afterward allows the retained target tracking policies to scale capacity down as demand falls.

### Question 8 (DVA-C02)

**Question:**

An AWS Lambda function processes tag-assignment events for assets. Each event contains an assetId and one tag string. An Amazon DynamoDB table stores one item per asset, including its assigned tags and other asset attributes. The same event can be delivered multiple times, and different tags for the same asset can be processed concurrently.

The developer must ensure that each tag appears only once, that concurrent assignments do not lose tags, and that existing asset attributes are preserved. The tags do not require ordering.

Which implementation meets these requirements?

**Correct answer:** Store tags as a string set. Use UpdateItem with ADD tags :incomingTags, where :incomingTags is a string set containing the incoming tag.

**Explanation:** DynamoDB atomically adds the incoming values to the existing set. Adding an existing member has no additional effect, so repeated deliveries do not create duplicates. Concurrent additions are preserved, and the update does not replace other asset attributes.

### Question 9 (SAA-C03)

**Question:**

A company uses an Amazon DynamoDB table for warehouse operations. For the past 6 months, the table has required 500 read capacity units (RCUs) and 200 write capacity units (WCUs), except during a daily import from 01:00 to 03:00 UTC that requires 5,000 RCUs and 2,000 WCUs. The import starts immediately at full throughput. This schedule and capacity requirement will remain unchanged for the next year, and requests are evenly distributed across partition keys.

Testing shows that reactive scaling from the lower capacity settings causes throttling when the import begins. The application cannot tolerate this throttling. A pricing analysis confirms that provisioning capacity for the measured low-demand and import periods costs less than using on-demand capacity mode.

Which solution meets the requirements at the LOWEST ongoing throughput cost?

**Correct answer:** Use provisioned capacity with scheduled scaling. Raise capacity to 5,000 RCUs and 2,000 WCUs sufficiently before 01:00 UTC, and return it to 500 RCUs and 200 WCUs after the import completes.

**Explanation:** The repeatable schedule allows capacity increases to complete before demand rises. Scheduled reductions eliminate unnecessary peak capacity during the rest of the day. This meets the no-throttling requirement and uses the lower-cost provisioned approach identified by the pricing analysis.

## Practice Amazon DynamoDB in a full exam

Questions on Amazon DynamoDB in each practice exam, with every answer option and an explanation for each:

- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 35 questions
- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 31 questions
- [DVA-C02](https://blowstack.com/practice-exams/aws-certified-developer-associate): 29 questions
- [AIP-C01](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional): 23 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 19 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 15 questions
- [MLA-C02 (beta)](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate): 9 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 7 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 3 questions

## What is Amazon DynamoDB

Amazon DynamoDB is a fully managed NoSQL database service that provides fast and predictable performance with seamless scalability. Built to address the limitations of traditional database systems, it offers developers the flexibility of storing and retrieving any amount of data and serving any level of request traffic. DynamoDB is designed to maintain high performance and efficiency even as it scales to accommodate immense datasets and high throughput.

At the core of Amazon DynamoDB is its fully managed nature, which means users do not need to worry about operational tasks such as hardware or software provisioning, setup and configuration, replication, software patching, or cluster scaling. It has a minimal learning curve, enabling developers to start creating new database tables and begin storing data almost instantly. The management console or alternatively, the AWS CLI or SDK offers an intuitive interface for creating and interacting with these tables.

DynamoDB local is a downloadable version of DynamoDB for developing and testing DynamoDB applications locally.

ExtendDB is an open source implementation of the DynamoDB API with pluggable storage backends. It lets applications use the DynamoDB programming model on laptops, in on-premises data centers, and at disconnected edge sites where the managed service is unavailable, without rewriting application code.

DynamoDB can handle more than 10 trillion requests per day and can support peaks of more than 20 million requests per second, making it a suitable backbone for large-scale mobile, web, gaming, ad tech, IoT, and many other applications. It is designed for durability and fault tolerance, automatically replicating data across multiple AWS Availability Zones to ensure reliability and safety.

For global tables, multi-Region strong consistency allows applications to read the same data from any Region and build zero recovery point objective applications.

Global table replicas can belong to a single AWS account or multiple AWS accounts, with at most one replica table per AWS Region.

One of the noteworthy features of Amazon DynamoDB is its flexible data model. It supports key-value and document data structures, meaning one can use the same service for different applications as needs evolve. Keys identify items, and these items can have one or more attributes, making it a great fit for a variety of data models. DynamoDB supports ACID (Atomicity, Consistency, Isolation, Durability) transactions. This brings a level of reliability to applications that require complete and total accuracy for every transaction. In addition to ACID transactions, it provides consistent, single-digit millisecond response times at any scale. It means applications remain responsive at all times, providing a smooth and predictable user experience.

Bulk put items writes data from Amazon S3 directly into an existing DynamoDB table as a managed, asynchronous operation without consuming the table's read or write capacity.

DynamoDB vector search adds vector indexing and similarity search to tables for retrieval-augmented generation and agentic AI applications without a separate vector database. It is available only in on-demand capacity mode and supports both Standard and Standard-IA table classes.

DynamoDB Accelerator (DAX) is a caching service that provides sub-millisecond response times for read operations.

Another important aspect is the DynamoDB Streams feature, which captures any changes to the items in the tables. The stream data can be used for various needs, such as triggering workflows or alerts when data changes or replicating data across tables or even outside of DynamoDB.

Cost is another realm where DynamoDB presents its strengths. It offers a pay-per-use model with no upfront costs or long-term commitments, which can be a cost-effective option for startups and large enterprises alike. On-demand capacity or provisioned throughput modes are available to control costs while managing performance.

Warm throughput is the number of read and write operations a table can instantaneously support. Tables and secondary indexes have warm throughput values by default, and those values automatically adjust as provisioned throughput or on-demand consumption increases.

Provisioned capacity is subject to regional account quotas and per-table quotas. Quota increases can be requested through AWS Support, but obtaining an increase is not instantaneous.

DynamoDB also offers two table classes: Standard, the default and recommended choice for most workloads, and Standard-Infrequent Access (Standard-IA), suited to infrequently accessed data where storage is the dominant cost. Both classes offer similar performance.

All in all, Amazon DynamoDB's integration with other AWS services, its high availability and durable nature, its security features, including encryption at rest, and its ease of use have established it as a critical component in the ecosystem of web and mobile applications, where performance and scalability are necessary to handle massive scale and rapid growth.

## Learn Amazon DynamoDB in lessons

27 short lessons on Amazon DynamoDB in 8 certification courses.

- CLF-C02: Amazon DocumentDB and Amazon DynamoDB: choosing a NoSQL database (Premium), https://app.blowstack.com/lessons/amazon-documentdb-and-amazon-dynamodb-choosing-a-nosql-database-clf-c02
- MLA-C02 (beta): Amazon ElastiCache vs Amazon DynamoDB: choosing a state store (Premium), https://app.blowstack.com/lessons/amazon-elasticache-vs-amazon-dynamodb-choosing-a-state-store-mla-c02
- SAP-C03: Amazon DynamoDB: access-pattern-driven data modeling (Premium), https://app.blowstack.com/lessons/amazon-dynamodb-access-pattern-driven-data-modeling-sap-c03
- SOA-C03: Amazon DynamoDB: throughput capacity and scaling (Premium), https://app.blowstack.com/lessons/amazon-dynamodb-throughput-capacity-and-scaling-soa-c03
- AIP-C01: Amazon DynamoDB: conversation history data modeling (Premium), https://app.blowstack.com/lessons/amazon-dynamodb-conversation-history-data-modeling-aip-c01
- DEA-C01: Amazon DynamoDB: access-pattern-driven data modeling (Premium), https://app.blowstack.com/lessons/amazon-dynamodb-access-pattern-driven-data-modeling-dea-c01

## Concepts related to Amazon DynamoDB

- [Conversation Memory](https://blowstack.com/tools/cloud-concepts-hub/conversation-memory): Conversation memory is the application-managed retention and reuse of prior interactions so an AI assistant can maintain context across turns or sessions.
- [ACID Transactions](https://blowstack.com/tools/cloud-concepts-hub/acid-transactions): ACID transactions group data operations into a reliable unit of work with atomicity, consistency, isolation, and durability guarantees.
- [Eventual Consistency](https://blowstack.com/tools/cloud-concepts-hub/eventual-consistency): Eventual consistency is a distributed-data model in which replicas may temporarily return different values but converge if updates stop and replication completes successfully.
- [Idempotency](https://blowstack.com/tools/cloud-concepts-hub/idempotency): Idempotency is the property that repeating an operation with the same intent has the same intended effect as performing it once.
- [Key-Value Data Model](https://blowstack.com/tools/cloud-concepts-hub/key-value-data-model): The key-value data model stores each value under a unique key so applications can retrieve, update, or delete it directly.
- [Point-in-Time Recovery](https://blowstack.com/tools/cloud-concepts-hub/point-in-time-recovery): Point-in-Time Recovery restores a database or other supported data store to its recoverable state at a selected time within a retained recovery window.
- [Database Indexing](https://blowstack.com/tools/cloud-concepts-hub/database-indexing): Database indexing uses auxiliary data structures to locate records efficiently without scanning all stored data.
- [Database Replication](https://blowstack.com/tools/cloud-concepts-hub/database-replication): Database replication copies database data and propagates changes to other database instances or locations to support migration, availability, and read scaling.
- [Statelessness](https://blowstack.com/tools/cloud-concepts-hub/statelessness): Statelessness is a design principle in which a processing instance does not depend on locally retained client or workflow state from previous requests.
- [Backpressure](https://blowstack.com/tools/cloud-concepts-hub/backpressure): Backpressure is feedback from a constrained downstream component that causes upstream components to slow or pause production.
- [Data Partitioning](https://blowstack.com/tools/cloud-concepts-hub/data-partitioning): Data partitioning divides a dataset into smaller subsets using defined rules so that storage, ingestion, processing, and queries can operate on manageable portions of the data.
- [Database](https://blowstack.com/tools/cloud-concepts-hub/database): A database is an organized collection of data that applications can efficiently store, retrieve, update, and manage.
- [Denormalization](https://blowstack.com/tools/cloud-concepts-hub/denormalization): Denormalization deliberately combines related data or stores redundant values to make common reads require less work.
- [AWS SDKs](https://blowstack.com/tools/cloud-concepts-hub/aws-sdks): AWS SDKs are language-specific software development kits that let applications interact with AWS service APIs through familiar programming interfaces.
- [Checkpointing](https://blowstack.com/tools/cloud-concepts-hub/checkpointing): Checkpointing is the practice of durably saving processing progress and any required execution state so work can resume from a known recovery point.
- [Exponential Backoff](https://blowstack.com/tools/cloud-concepts-hub/exponential-backoff): Exponential backoff is a retry strategy that increases the delay between successive attempts, usually by multiplying the previous delay by a fixed factor.
- [Multi-Agent Orchestration](https://blowstack.com/tools/cloud-concepts-hub/multi-agent-orchestration): Multi-agent orchestration coordinates multiple AI agents, their tools, shared context, and execution flow to complete a task.
- [Pagination](https://blowstack.com/tools/cloud-concepts-hub/pagination): Pagination divides a large result set into smaller responses that clients retrieve through successive requests.
- [Strong Consistency](https://blowstack.com/tools/cloud-concepts-hub/strong-consistency): Strong consistency guarantees that a successful read reflects the latest completed write within the system’s defined consistency scope.
- [Active-Active Architecture](https://blowstack.com/tools/cloud-concepts-hub/active-active-architecture): Active-active architecture runs multiple production environments simultaneously, distributing live traffic across them so healthy environments can continue serving users when another fails.
- [Data Replication](https://blowstack.com/tools/cloud-concepts-hub/data-replication): Data replication is the process of maintaining copies of the same data on multiple storage systems or locations and propagating changes between them.
- [Document Data Model](https://blowstack.com/tools/cloud-concepts-hub/document-data-model): A document data model represents records as self-contained, structured documents containing named fields, nested objects, and arrays.
- [Key Salting](https://blowstack.com/tools/cloud-concepts-hub/key-salting): Key salting adds a controlled extra value to a key so that records sharing a hot key can be distributed across multiple processing or storage partitions.
- [Serverless](https://blowstack.com/tools/cloud-concepts-hub/serverless-and-event-driven-design-principles): Serverless is a cloud operating model in which the provider manages the underlying servers while customers deploy applications or use services without provisioning and maintaining those servers.
- [Sharding](https://blowstack.com/tools/cloud-concepts-hub/sharding): Sharding divides a dataset into horizontal subsets distributed across storage or compute resources so that capacity and workload can scale beyond a single resource.
- [Time to Live](https://blowstack.com/tools/cloud-concepts-hub/time-to-live): Time to Live is a limit on how long data remains valid, reusable, or retained before expiration handling applies.
- [Circuit Breaker](https://blowstack.com/tools/cloud-concepts-hub/circuit-breaker): A circuit breaker is a resilience pattern that temporarily blocks calls to a failing dependency and permits controlled probes before restoring normal traffic.
- [Client-Side Encryption](https://blowstack.com/tools/cloud-concepts-hub/client-side-encryption): Client-side encryption encrypts data in the application or client environment before sending it to a cloud storage or data service.
- [Concurrency Control](https://blowstack.com/tools/cloud-concepts-hub/concurrency-control): Concurrency control coordinates simultaneous access to shared data so that overlapping operations preserve the required consistency and isolation guarantees.
- [Deduplication](https://blowstack.com/tools/cloud-concepts-hub/deduplication): Deduplication identifies repeated representations of the same data and removes or consolidates them according to explicit matching and retention rules.
- [Determinism](https://blowstack.com/tools/cloud-concepts-hub/determinism): Determinism is the property of a computation that produces the same result whenever its inputs, initial state, and execution conditions are the same.
- [Graph Data Model](https://blowstack.com/tools/cloud-concepts-hub/graph-data-model): A graph data model represents entities as nodes and their relationships as edges, making connected data explicit and directly queryable.
- [Intent Classification](https://blowstack.com/tools/cloud-concepts-hub/intent-classification): Intent classification identifies the goal expressed in a user's message and maps it to a defined category that guides the application's next action.
- [OLTP Versus OLAP](https://blowstack.com/tools/cloud-concepts-hub/oltp-versus-olap): OLTP versus OLAP distinguishes databases optimized for frequent operational transactions from systems optimized for large-scale analytical queries.
- [Optimistic Concurrency Control](https://blowstack.com/tools/cloud-concepts-hub/optimistic-concurrency-control): Optimistic Concurrency Control lets concurrent operations proceed independently and validates their assumptions before committing changes.
- [Pay-as-You-Go Pricing](https://blowstack.com/tools/cloud-concepts-hub/pay-as-you-go-pricing): Pay-as-You-Go Pricing is a cloud billing model that charges for measured resource consumption or provisioned capacity rather than requiring infrastructure purchases upfront.
- [Polyglot Persistence](https://blowstack.com/tools/cloud-concepts-hub/polyglot-persistence): Polyglot persistence is the use of different database technologies within an application or system to match distinct data models, access patterns, and operational requirements.
- [Pseudonymization](https://blowstack.com/tools/cloud-concepts-hub/pseudonymization): Pseudonymization replaces identifying data with substitute values so records cannot be attributed to a person without separately protected additional information.
- [Request Signing](https://blowstack.com/tools/cloud-concepts-hub/request-signing): Request signing cryptographically binds an API request to credentials so a receiving service can authenticate the caller and detect changes to protected request components.
- [Semi-Structured Data](https://blowstack.com/tools/cloud-concepts-hub/semi-structured-data): Semi-structured data uses keys, tags, or other markers to organize information without requiring every record to follow the same fixed tabular schema.
- [Skills Matrix](https://blowstack.com/tools/cloud-concepts-hub/skills-matrix): A skills matrix maps people or roles to required competencies and proficiency levels to reveal capability gaps and guide workforce development.
- [Stakeholder Mapping](https://blowstack.com/tools/cloud-concepts-hub/stakeholder-mapping): Stakeholder mapping identifies the people and groups affected by an initiative and assesses their influence, interests, concerns, and engagement needs.
- [Star Schema](https://blowstack.com/tools/cloud-concepts-hub/star-schema): A star schema is an analytical data model that connects a central fact table to descriptive dimension tables through keys.
- [Stateful Processing](https://blowstack.com/tools/cloud-concepts-hub/stateful-processing): Stateful processing retains information across records, requests, or events so that earlier activity can influence later results.
- [Task Planning](https://blowstack.com/tools/cloud-concepts-hub/task-planning): Task planning is the process of turning a goal into actionable steps, selecting suitable tools, and adjusting the steps as new information becomes available.
- [Transaction Isolation](https://blowstack.com/tools/cloud-concepts-hub/transaction-isolation): Transaction isolation controls how concurrent database transactions observe and affect one another’s data.
- [Uniqueness Constraints](https://blowstack.com/tools/cloud-concepts-hub/uniqueness-constraints): Uniqueness constraints are rules that require a column value or combination of column values to occur no more than once within a defined scope.
- [Vertical Scaling](https://blowstack.com/tools/cloud-concepts-hub/vertical-scaling): Vertical scaling changes the capacity of an existing compute resource or database instance by increasing or decreasing its allocated resources rather than changing the number of instances.
- [WebSockets](https://blowstack.com/tools/cloud-concepts-hub/websockets): WebSockets is a communication protocol that enables persistent, bidirectional message exchange between a client and a server over a single connection.
