The answer is to use the `ConsistentRead` parameter set to `true` for profile queries and `false` for leaderboard queries. This works because DynamoDB supports both strongly consistent reads and eventually consistent reads on the same table, controlled entirely by the `ConsistentRead` parameter in `GetItem`, `Query`, or `Scan` API calls. Setting it to `true` guarantees the most recent write is returned, which is critical for a user’s own profile data, while the default `false` for leaderboard queries delivers lower latency and higher throughput—ideal for read-heavy, non-critical data. On the AWS Certified Database Specialty DBS-C01 exam, this scenario tests your understanding that consistency is a per-request choice, not a table-level setting; a common trap is assuming you need separate tables or DynamoDB Accelerator (DAX) for strong reads. Remember the mnemonic: “Profile is true, leaderboard is false—same table, different calls.”
DBS-C01 Workload-Specific Database Design Practice Question
This DBS-C01 practice question tests your understanding of workload-specific database design. 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 gaming company uses Amazon DynamoDB as the database for user profiles and game state. The application requires strongly consistent reads for the user's own profile, but eventually consistent reads for leaderboard queries. How should the company design the table and queries?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use the ConsistentRead parameter set to true for profile queries and false for leaderboard queries.
DynamoDB supports both strongly consistent reads and eventually consistent reads on the same table, controlled by the `ConsistentRead` parameter in the `GetItem`, `Query`, or `Scan` API calls. Setting `ConsistentRead=true` for profile queries ensures the most up-to-date data, while `ConsistentRead=false` (the default) for leaderboard queries provides lower latency and higher throughput, which is ideal for read-heavy, non-critical data. This design avoids the cost and complexity of multiple tables or additional services.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Create two separate tables: one for strong consistency and one for eventual consistency.
Why it's wrong here
Unnecessary; DynamoDB supports consistency levels per request.
✓
Use the ConsistentRead parameter set to true for profile queries and false for leaderboard queries.
Why this is correct
This allows per-request consistency control.
Related concept
Read the scenario before looking for a memorised answer.
✗
Enable DynamoDB Accelerator (DAX) for strong consistency on all reads.
Why it's wrong here
DAX provides eventual consistency; strong consistency reads must go directly to DynamoDB.
✗
Configure DynamoDB Streams to replicate data to a second table for strong consistency.
Why it's wrong here
Streams are for change data capture, not for consistency control.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume strong consistency requires a separate table or a caching layer like DAX, but DynamoDB natively supports both consistency models on the same table via a simple API parameter, making the other options over-engineered or incorrect.
Detailed technical explanation
How to think about this question
Under the hood, DynamoDB stores data across multiple storage nodes in a leaderless replication model. A strongly consistent read (`ConsistentRead=true`) reads from the leader partition, which has the latest write, while an eventually consistent read reads from any replica, potentially returning stale data. The `ConsistentRead` parameter incurs higher read capacity unit (RCU) consumption (1 RCU per 4 KB for strongly consistent vs. 0.5 RCU per 4 KB for eventually consistent), so using it only when necessary optimizes cost and performance.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Workload-Specific Database Design — This question tests Workload-Specific Database Design — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use the ConsistentRead parameter set to true for profile queries and false for leaderboard queries. — DynamoDB supports both strongly consistent reads and eventually consistent reads on the same table, controlled by the `ConsistentRead` parameter in the `GetItem`, `Query`, or `Scan` API calls. Setting `ConsistentRead=true` for profile queries ensures the most up-to-date data, while `ConsistentRead=false` (the default) for leaderboard queries provides lower latency and higher throughput, which is ideal for read-heavy, non-critical data. This design avoids the cost and complexity of multiple tables or additional services.
What should I do if I get this DBS-C01 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 DBS-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 DBS-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.