The answer is to add a DynamoDB Accelerator (DAX) cluster in front of the table. DAX is a fully managed, highly available, in-memory cache that reduces DynamoDB read latencies from single-digit milliseconds to microseconds for frequently accessed items, making it the ideal solution for workloads that repeatedly read the same data and can tolerate a few seconds of staleness. This architecture offloads read traffic from the table’s provisioned capacity and requires no application code changes, as DAX handles cache hits transparently. On the SAA-C03 exam, this scenario tests your understanding of when to use DAX versus ElastiCache or DynamoDB Global Tables—the key trap is choosing ElastiCache, which adds operational overhead and isn’t natively integrated with DynamoDB’s API. Remember the mnemonic: “DAX for DynamoDB, microsecond reads, no code tweaks.”
SAA-C03 Design High-Performing Architectures Practice Question
This SAA-C03 practice question tests your understanding of design high-performing architectures. 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.
Exhibit
DynamoDB access pattern report:
- TableName: SessionState
- Read pattern: GetItem on the same 500 keys during active sessions
- Read frequency: 1.2 million reads/minute during peak periods
- Cacheability: yes, stale data up to 5 seconds is acceptable
CloudWatch metrics:
- ConsumedReadCapacityUnits: 92% of provisioned limit
- SuccessfulRequestLatency p95: 7.5 ms
- ThrottledRequests: intermittent during peaks
Application note:
- Writes are comparatively rare and do not need multi-Region replication.
Based on the exhibit, an application repeatedly reads the same DynamoDB items with extremely low latency requirements. The business can tolerate data that is a few seconds stale. Which architecture change best improves read performance?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
DynamoDB access pattern report:
- TableName: SessionState
- Read pattern: GetItem on the same 500 keys during active sessions
- Read frequency: 1.2 million reads/minute during peak periods
- Cacheability: yes, stale data up to 5 seconds is acceptable
CloudWatch metrics:
- ConsumedReadCapacityUnits: 92% of provisioned limit
- SuccessfulRequestLatency p95: 7.5 ms
- ThrottledRequests: intermittent during peaks
Application note:
- Writes are comparatively rare and do not need multi-Region replication.
A
Add a DynamoDB Accelerator (DAX) cluster in front of the table.
DAX is designed for repeated, read-heavy DynamoDB access patterns where a small amount of staleness is acceptable. It can dramatically reduce read latency and offload the table during peak demand.
B
Increase the table's sort key cardinality while keeping the same read pattern.
Why wrong: Changing sort key cardinality does not help if the application repeatedly reads the same items. The bottleneck is repeated reads, not range query design.
C
Switch the table to provisioned mode with auto scaling disabled.
Why wrong: Disabling auto scaling removes an important safety mechanism and does not reduce latency. It may also worsen throttling during peaks if capacity is not manually tuned.
D
Move the session data to Amazon EFS so the application can read it from shared files.
Why wrong: EFS is a file system, not a low-latency key-value cache. Moving the data would change the data model and would not provide the same read performance characteristics as DAX.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Add a DynamoDB Accelerator (DAX) cluster in front of the table.
Adding a DynamoDB Accelerator (DAX) cluster provides an in-memory cache that can reduce read latencies to microseconds for frequently accessed items, while still allowing for eventual consistency and tolerating a few seconds of staleness. DAX is specifically designed for this use case, handling cache hits without any application code changes and offloading read traffic from the DynamoDB table.
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.
✓
Add a DynamoDB Accelerator (DAX) cluster in front of the table.
Why this is correct
DAX is designed for repeated, read-heavy DynamoDB access patterns where a small amount of staleness is acceptable. It can dramatically reduce read latency and offload the table during peak demand.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Increase the table's sort key cardinality while keeping the same read pattern.
Why it's wrong here
Changing sort key cardinality does not help if the application repeatedly reads the same items. The bottleneck is repeated reads, not range query design.
✗
Switch the table to provisioned mode with auto scaling disabled.
Why it's wrong here
Disabling auto scaling removes an important safety mechanism and does not reduce latency. It may also worsen throttling during peaks if capacity is not manually tuned.
✗
Move the session data to Amazon EFS so the application can read it from shared files.
Why it's wrong here
EFS is a file system, not a low-latency key-value cache. Moving the data would change the data model and would not provide the same read performance characteristics as DAX.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may overlook DAX as a specialized caching layer for DynamoDB and instead consider increasing table capacity or changing data models, which do not directly address the need for extremely low latency on repeated reads of the same items.
Detailed technical explanation
How to think about this question
DAX uses a write-through caching strategy where writes to the DynamoDB table are also written to the cache, ensuring that subsequent reads of the same item are served from memory with microsecond latency. The cache is eventually consistent with the table, typically within a few seconds, which aligns with the business requirement for tolerating stale data. In real-world scenarios, DAX can reduce read costs by offloading repeated reads from provisioned read capacity units (RCUs), as cache hits do not consume RCUs.
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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
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.
Design High-Performing Architectures — This question tests Design High-Performing Architectures — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Add a DynamoDB Accelerator (DAX) cluster in front of the table. — Adding a DynamoDB Accelerator (DAX) cluster provides an in-memory cache that can reduce read latencies to microseconds for frequently accessed items, while still allowing for eventual consistency and tolerating a few seconds of staleness. DAX is specifically designed for this use case, handling cache hits without any application code changes and offloading read traffic from the DynamoDB table.
What should I do if I get this SAA-C03 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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 SAA-C03 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 SAA-C03 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.