AWS Certified Data Analytics Specialty 2021 - Hands-On! - Amazon DynamoDB Provisioned Throughput

The video tutorial explains how to compute provisioned throughput in DynamoDB, focusing on read and write capacity units (RCU and WCU). It covers the differences between strongly consistent and eventually consistent reads, and provides examples of calculating RCU and WCU. The tutorial also addresses throttling issues, such as hot keys, and suggests solutions like exponential backoff and using DynamoDB Accelerator (DAX). Finally, it demonstrates how to configure DynamoDB tables, including using the capacity calculator and setting up autoscaling.

What is the purpose of provisioning read and write capacity units in DynamoDB?

• To calculate storage costs

• To manage user access levels

• To ensure data is stored securely

• To define the throughput for reads and writes

How can you temporarily exceed the provisioned throughput in DynamoDB?

• By using a different partition key

• By enabling multi-region replication

• By increasing the table size

• By using burst credits

If you write 10 objects per second, each 2 KB in size, how many WCUs are needed?

• 5 WCUs

• 20 WCUs

• 15 WCUs

• 10 WCUs

What is the difference between strongly consistent reads and eventually consistent reads?

• Eventually consistent reads require more RCUs

• Strongly consistent reads are cheaper

• Eventually consistent reads may return outdated data

• Strongly consistent reads are faster

How many RCUs are needed for 10 strongly consistent reads per second of 6 KB each?

• 10 RCUs

• 15 RCUs

• 25 RCUs

• 20 RCUs

What is a hot key in the context of DynamoDB?

• A key that is used for partitioning

• A key that is used for encryption

• A key that is rarely used

• A key that is frequently accessed

What is the purpose of DynamoDB Accelerator (DAX)?

• To increase storage capacity

• To provide caching for faster reads

• To enhance security features

• To reduce write latency