The correct answer is to create a global secondary index (GSI) on the attributes used in the reporting queries. This works because DynamoDB on-demand tables still face per-partition throughput limits, and frequent Scan operations can overwhelm a single partition, triggering ProvisionedThroughputExceededException errors even without provisioned capacity. By using a GSI, the reporting application can replace inefficient full-table scans with targeted Query operations against the index, which distributes read activity across multiple partitions and eliminates the hot spots causing throttling. On the AWS Certified Data Engineer Associate DEA-C01 exam, this scenario tests your understanding that on-demand mode does not remove partition-level constraints—a common trap is assuming the error means you need to switch to provisioned capacity, which would add cost and complexity. The key insight is that GSIs enable efficient access patterns without changing the table’s capacity mode. Memory tip: “Scans cause strains; GSIs give gains.”
DEA-C01 Data Operations and Support Practice Question
This DEA-C01 practice question tests your understanding of data operations and support. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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 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.
Option B is correct because on-demand tables do not have provisioned throughput, but the error indicates throttling due to per-partition throughput limits. Creating a GSI allows the reporting queries to use a more efficient query pattern, reducing scans and partition hot spots. Option A is incorrect because switching to provisioned capacity would require careful capacity planning and might increase cost. Option C is incorrect because the error is not due to table-level limits but partition-level limits. Option D is incorrect because DAX is a caching layer that can reduce read load but does not address the root cause of inefficient Scan operations.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
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.
Related concept
Static NAT maps one inside address to one outside address.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
What to study next
Got this wrong? Here's your next step.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related DEA-C01 NAT questions on configuration and troubleshooting.
Data Operations and Support — This question tests Data Operations and Support — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Create a global secondary index (GSI) on the attributes used in the reporting queries. — Option B is correct because on-demand tables do not have provisioned throughput, but the error indicates throttling due to per-partition throughput limits. Creating a GSI allows the reporting queries to use a more efficient query pattern, reducing scans and partition hot spots. Option A is incorrect because switching to provisioned capacity would require careful capacity planning and might increase cost. Option C is incorrect because the error is not due to table-level limits but partition-level limits. Option D is incorrect because DAX is a caching layer that can reduce read load but does not address the root cause of inefficient Scan operations.
What should I do if I get this DEA-C01 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related DEA-C01 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.