A company has a web-based survey application that uses Amazon DynamoDB. During peak usage, when survey responses are being collected, a Database Specialist sees the…

Question

Options

• AChange the table to use Amazon DynamoDB Streams
• BPurchase DynamoDB reserved capacity in the affected Region
• CIncrease the write capacity units for the specific table
• DChange the table capacity mode to on-demand
• EChange the table type to throughput optimized

• A
  11% (5)
• B
  9% (4)
• C
  78% (36)
• E
  2% (1)

Explanation

ProvisionedThroughputExceededException Explained

Why C and D are correct: A ProvisionedThroughputExceededException means the application is exceeding the allocated read/write capacity on the DynamoDB table. Option C directly resolves this by manually increasing the Write Capacity Units (WCUs), giving the table more throughput to handle peak survey submissions. Option D switches the table to On-Demand capacity mode, which automatically scales to accommodate any traffic level without requiring capacity planning - ideal for unpredictable or spiky workloads like surveys.

Why the distractors are wrong:

• A (DynamoDB Streams) captures item-level changes for event-driven processing - it has nothing to do with resolving throughput errors.
• B (Reserved Capacity) is a billing/cost optimization feature that saves money on already-provisioned capacity; it does not increase throughput limits.
• E (Throughput optimized) is not a valid DynamoDB table type - this terminology belongs to EBS volume types, making it a nonsensical distractor.

Memory Tip: Think "Fix the throttle, not the bill" - Reserved Capacity saves money but won't stop throttling. To fix throttling, you must either raise the capacity (C) or remove the ceiling entirely with On-Demand (D).

No community discussion yet for this question.