DEA-C01 Data Store Management Practice Question
A data engineer is designing a DynamoDB table for an application that requires strongly consistent reads and supports a global secondary index (GSI). The engineer needs to ensure that queries on the GSI return the most up-to-date data. Which statement about DynamoDB read consistency is correct?
⚠ Common exam trap
The trap here is assuming that GSI reads can be strongly consistent like base table reads, when GSIs are inherently eventually consistent.
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
✓
GSI queries are eventually consistent and cannot be made strongly consistent.
DynamoDB GSIs are updated asynchronously from the base table, so reads from a GSI are eventually consistent and cannot be made strongly consistent. The engineer must either accept eventual consistency or query the base table directly for strongly consistent reads. This is a key design constraint when using GSIs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
GSI queries can be strongly consistent only if the index is created with a specific attribute for versioning.
Why it's wrong here
There is no versioning attribute that enables strong consistency on a GSI. DynamoDB does not provide a mechanism to make GSI reads strongly consistent. Adding a version attribute would not change the asynchronous replication behavior. This option invents a non-existent feature and fails to address the actual consistency model.
- ✗
GSI queries always return strongly consistent data because the index is maintained synchronously.
Why it's wrong here
GSIs are updated asynchronously, so queries on a GSI are eventually consistent and may not reflect the latest writes to the base table. They do not support strongly consistent reads. This option incorrectly claims synchronous maintenance and strong consistency, which is not how DynamoDB GSIs operate in this scenario.
- ✓
GSI queries are eventually consistent and cannot be made strongly consistent.
Why this is correct
DynamoDB GSIs are maintained asynchronously from the base table, so queries on a GSI are eventually consistent and may return stale data. Strongly consistent reads are not supported on GSIs. This is a fundamental limitation, so the engineer must accept eventual consistency or query the base table directly for strong consistency.
- ✗
GSI queries can be strongly consistent if the base table uses on-demand capacity mode.
Why it's wrong here
Capacity mode (provisioned or on-demand) affects throughput and cost, not read consistency. GSIs are always eventually consistent regardless of the base table's capacity mode. This option confuses capacity management with consistency semantics and would not provide the required up-to-date data for GSI queries.
Go deeper
Related to this question
About these practice questions
One of 1,321 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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Amazon Web Services exam blueprint
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.