The correct choice is to use DynamoDB UpdateItem with an update expression to modify only the changed attributes. This reduces write costs because DynamoDB charges based on the size of the data written per write request unit; a full-item overwrite consumes WCUs proportional to the entire item size, whereas a partial update writes only the bytes of the changed attributes—often a fraction of the total. On the AWS Certified Database Specialty DBS-C01 exam, this scenario tests your understanding of DynamoDB write capacity optimization for session data, a common real-world pattern. A frequent trap is assuming that any update rewrites the whole item, but UpdateItem with an expression is the cost-efficient alternative. Remember the memory tip: “Update only what’s new, not the whole stew”—partial updates slash write costs and prevent throttling by minimizing consumed capacity.
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 company has a document database workload on Amazon DynamoDB that stores user session data. The application frequently updates session attributes (e.g., last activity timestamp). The current design stores the entire session as a single item and updates the entire item on each session activity. This is causing high write costs and throttling. Which design pattern would reduce write costs and improve performance?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use UpdateItem with an update expression to modify only the changed attributes.
Option B is correct because using UpdateItem with an update expression allows you to modify only the specific attributes that changed (e.g., last activity timestamp) instead of rewriting the entire item. This reduces write consumption to a fraction of the original cost, since DynamoDB charges based on the size of the written data, and partial updates write only the changed attribute bytes. This directly addresses the high write costs and throttling caused by full-item overwrites.
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.
✗
Increase the write capacity units (WCUs) on the table.
Why it's wrong here
Increasing capacity increases cost and does not reduce the write unit consumption per update.
✓
Use UpdateItem with an update expression to modify only the changed attributes.
Why this is correct
Update expressions only write the changed attributes, consuming fewer write capacity units.
Related concept
Read the scenario before looking for a memorised answer.
✗
Implement DynamoDB Accelerator (DAX) to cache the session data.
Why it's wrong here
DAX is a read cache and does not reduce write costs.
✗
Split the session item into multiple items, one per attribute.
Why it's wrong here
Splitting items complicates queries and may increase overall write cost due to multiple item updates.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse scaling solutions (increasing WCUs or adding DAX) with optimization patterns, failing to recognize that the real issue is the write amplification caused by full-item updates rather than insufficient capacity or read performance.
Detailed technical explanation
How to think about this question
Under the hood, DynamoDB's UpdateItem with an update expression uses atomic write operations that only consume write capacity proportional to the size of the updated attributes, not the entire item. For example, updating a single timestamp attribute (e.g., 8 bytes) consumes only 1 WCU (for items up to 1 KB), whereas rewriting a 4 KB session item consumes 4 WCUs. In real-world scenarios with high-frequency session updates, this pattern can reduce write costs by over 90% and eliminate throttling without any capacity increase.
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 UpdateItem with an update expression to modify only the changed attributes. — Option B is correct because using UpdateItem with an update expression allows you to modify only the specific attributes that changed (e.g., last activity timestamp) instead of rewriting the entire item. This reduces write consumption to a fraction of the original cost, since DynamoDB charges based on the size of the written data, and partial updates write only the changed attribute bytes. This directly addresses the high write costs and throttling caused by full-item overwrites.
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.