DEA-C01 Data Operations and Support Practice Question
A company runs an Amazon DynamoDB table with on-demand capacity. A new reporting application performs frequent Scan operations on the table, causing occasional 'ProvisionedThroughputExceededException' errors. The operations team needs to resolve this with minimal cost. What should they do?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a global secondary index (GSI) on the attributes used in the reporting queries.
Creating a global secondary index (GSI) on the attributes used in the reporting queries allows the reporting application to use Query operations instead of expensive Scan operations. This reduces the read capacity consumption and avoids partition-level throttling, which is the cause of the 'ProvisionedThroughputExceededException' errors. On-demand tables have per-partition throughput limits, and frequent Scans can exceed those limits. Option A is incorrect because increasing the maximum read capacity via AWS Support is not applicable to on-demand tables; on-demand scaling is automatic but per-partition limits still apply. Option B is incorrect because switching to provisioned capacity would require careful capacity planning and would likely increase costs compared to using a GSI. Option C is incorrect because DAX can cache data and reduce read load, but it does not eliminate the inefficiency of Scan operations; the root cause is the Scan itself, which can be avoided by using a GSI to enable efficient queries.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the table's maximum read capacity by requesting a limit increase from AWS Support.
Why it's wrong here
On-demand tables have no configurable limits; throttling is per partition.
- ✗
Switch the table to provisioned capacity and increase the read capacity units.
Why it's wrong here
On-demand tables already handle throughput fluctuations; provisioned capacity may not reduce cost and might still throttle per partition.
- ✗
Enable DynamoDB Accelerator (DAX) to cache the Scan results.
Why it's wrong here
DAX reduces read load but does not eliminate partition-level throttling from Scans.
- ✓
Create a global secondary index (GSI) on the attributes used in the reporting queries.
Why this is correct
GSI enables efficient queries, reducing Scans and avoiding partition-level throttling.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 1,711 original DEA-C01 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DEA-C01 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DEA-C01 exam.