Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Amazon Exam DVA-C02 Topic 3 Question 44 Discussion

Actual exam question for Amazon's DVA-C02 exam
Question #: 44
Topic #: 3
[All DVA-C02 Questions]

A developer is receiving an intermittent ProvisionedThroughputExceededException error from an application that is based on Amazon DynamoDB. According to the Amazon CloudWatch metrics for the table, the application is not exceeding the provisioned throughput. What could be the cause of the issue?

Show Suggested Answer Hide Answer
Suggested Answer: B

DynamoDB distributes throughput across partitions based on the hash key. A hot partition (caused by high usage of a specific hash key) can result in a ProvisionedThroughputExceededException, even if overall usage is below the provisioned capacity.

Why Option B is Correct:

Partition-Level Limits: Each partition has a limit of 3,000 read capacity units or 1,000 write capacity units per second.

Hot Partition: Excessive use of a single hash key can overwhelm its partition.

Why Not Other Options:

Option A: DynamoDB storage size does not affect throughput.

Option C: Provisioned scaling operations are unrelated to throughput errors.

Option D: Sort keys do not impact partition-level throughput.


DynamoDB Partition Key Design Best Practices

by Erick at Jan 14, 2025, 09:39 PM

Limited Time Offer

25%

Off

Get Premium DVA-C02 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Annamae
2 months ago
This is why I always carry a backup of my backup. You never know when a ProvisionedThroughputExceededException is going to rear its ugly head!
upvoted 0 times
...
Denny
2 months ago
Ah, classic DynamoDB woes. I'd go with C - the table is exceeding the provisioned scaling operations. That would explain the intermittent nature of the problem.
upvoted 0 times
...
Sharen
2 months ago
I don't know, this one's got me stumped. The CloudWatch metrics not showing the issue is throwing me off. Maybe it's a glitch in the system? *laughs* Or maybe they need to invest in some crystal balls.
upvoted 0 times
...
Lyda
3 months ago
Option D is my guess. The sort key could be the culprit if the application is hitting that more heavily than expected.
upvoted 0 times
Myra
2 months ago
But what if it's actually the storage size of the table that's causing the problem?
upvoted 0 times
...
Vashti
2 months ago
I think you might be right. The sort key could be causing the issue.
upvoted 0 times
...
Frederick
2 months ago
It's possible, but we should also check if the table storage size is larger than provisioned.
upvoted 0 times
...
Keena
2 months ago
I think you might be right, the sort key could be causing the issue.
upvoted 0 times
...
...
Malcom
3 months ago
Hmm, this seems like it could be a tricky one. I'm leaning towards option B - the application exceeding capacity on a particular hash key. That could definitely cause some intermittent issues.
upvoted 0 times
Avery
2 months ago
User3: I agree, it's a tough call between those two options.
upvoted 0 times
...
Luz
2 months ago
User2: Maybe, but it could also be option C with the scaling operations.
upvoted 0 times
...
Mendy
2 months ago
User1: I think it might be option B too, the hash key capacity could be the issue.
upvoted 0 times
...
...
Carissa
3 months ago
I'm not sure, but option C could also be a possibility.
upvoted 0 times
...
Sharita
3 months ago
I agree with Nana, option B makes sense.
upvoted 0 times
...
Nana
3 months ago
I think the cause could be option B.
upvoted 0 times
...

Save Cancel