- A
Amazon DAX (DynamoDB Accelerator) to cache frequently read items
DAX is an in-memory caching layer specifically built for DynamoDB. It reduces read latency for hot keys by serving cached responses quickly while still reading from DynamoDB when a key is not cached (or when the cached entry expires). This avoids the need to redesign partition keys.
- B
Provision AWS WAF rules to reduce DynamoDB read latency caused by bots
Why wrong: WAF helps protect web/API endpoints by filtering malicious traffic. It does not provide an in-memory cache for DynamoDB reads and does not reduce the DynamoDB access path latency for legitimate application reads.
- C
Enable multi-region writes in DynamoDB Global Tables to speed up reads locally
Why wrong: Global Tables primarily provides replication across regions for availability and regional access. It does not target latency for hot keys within a single region, and it changes replication/write behavior rather than accelerating DynamoDB point reads.
- D
Add more read capacity units to DynamoDB and avoid caching entirely
Why wrong: Increasing read capacity helps throughput and can reduce throttling, but it does not directly reduce per-request latency for repeatedly accessed items. DAX is specifically intended to lower latency via caching for hot-key workloads.
Quick Answer
The answer is Amazon DAX (DynamoDB Accelerator). This is the correct choice because DAX is an in-memory cache designed specifically to reduce DynamoDB read latency for frequently accessed keys, delivering microsecond response times by caching hot items directly between your application and the database. On the SAA-C03 exam, this scenario tests your understanding of caching strategies for read-heavy workloads with hot keys, where you must avoid changing the partition key design—a common trap is to suggest ElastiCache, but DAX is purpose-built for DynamoDB and requires no application code changes for caching. Remember that DAX handles both eventual and strong consistency reads, and it automatically invalidates stale data when the underlying DynamoDB item is updated. Memory tip: think "DAX = DynamoDB's Accelerator for eXpress reads" to recall it solves hot-key latency without redesigning your table.
SAA-C03 Design High-Performing Architectures Practice Question
This SAA-C03 practice question tests your understanding of design high-performing architectures. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.
An application uses DynamoDB to store order status. Reads happen extremely frequently for the same few keys (for example, the most recent orders), and the team wants lower read latency without changing the table’s partition key design. Which AWS service best fits this requirement?
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.
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
Amazon DAX (DynamoDB Accelerator) to cache frequently read items
Amazon DAX (DynamoDB Accelerator) is an in-memory cache that sits between your application and DynamoDB, providing microsecond read latency for frequently accessed items. Because the workload involves extremely frequent reads of the same few keys (hot keys), DAX reduces the load on the DynamoDB table and delivers faster responses without requiring any changes to the partition key design.
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.
- ✓
Amazon DAX (DynamoDB Accelerator) to cache frequently read items
Why this is correct
DAX is an in-memory caching layer specifically built for DynamoDB. It reduces read latency for hot keys by serving cached responses quickly while still reading from DynamoDB when a key is not cached (or when the cached entry expires). This avoids the need to redesign partition keys.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Provision AWS WAF rules to reduce DynamoDB read latency caused by bots
Why it's wrong here
WAF helps protect web/API endpoints by filtering malicious traffic. It does not provide an in-memory cache for DynamoDB reads and does not reduce the DynamoDB access path latency for legitimate application reads.
- ✗
Enable multi-region writes in DynamoDB Global Tables to speed up reads locally
Why it's wrong here
Global Tables primarily provides replication across regions for availability and regional access. It does not target latency for hot keys within a single region, and it changes replication/write behavior rather than accelerating DynamoDB point reads.
- ✗
Add more read capacity units to DynamoDB and avoid caching entirely
Why it's wrong here
Increasing read capacity helps throughput and can reduce throttling, but it does not directly reduce per-request latency for repeatedly accessed items. DAX is specifically intended to lower latency via caching for hot-key workloads.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse throughput scaling (adding RCUs) with latency optimization, or they mistakenly think Global Tables improve read latency within a single region, when in fact DAX is the only option that directly caches hot keys to reduce read latency without altering the table design.
Detailed technical explanation
How to think about this question
DAX uses an in-memory cache with a write-through strategy, meaning writes to DynamoDB are also written to the cache, ensuring consistency for frequently read items. Under the hood, DAX maintains a cluster of nodes that handle cache hits at sub-millisecond latency, while cache misses fall back to DynamoDB with minimal overhead. In real-world scenarios, DAX is especially effective for read-heavy workloads with a skewed access pattern (e.g., the top 5% of keys receiving 95% of reads), where it can reduce read costs by offloading capacity units from the DynamoDB table.
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 — study guide chapter
Learn the concepts, then practise the questions
- →
Design High-Performing Architectures practice questions
Targeted practice on this topic area only
- →
All SAA-C03 questions
1,040 questions across all exam domains
- →
SAA-C03 study guide
Full concept coverage aligned to exam objectives
- →
SAA-C03 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SAA-C03 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Design Secure Architectures practice questions
Practise SAA-C03 questions linked to Design Secure Architectures.
Design Resilient Architectures practice questions
Practise SAA-C03 questions linked to Design Resilient Architectures.
Design High-Performing Architectures practice questions
Practise SAA-C03 questions linked to Design High-Performing Architectures.
Design Cost-Optimized Architectures practice questions
Practise SAA-C03 questions linked to Design Cost-Optimized Architectures.
SAA-C03 VPC practice questions
Practise SAA-C03 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free SAA-C03 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SAA-C03 question test?
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: Amazon DAX (DynamoDB Accelerator) to cache frequently read items — Amazon DAX (DynamoDB Accelerator) is an in-memory cache that sits between your application and DynamoDB, providing microsecond read latency for frequently accessed items. Because the workload involves extremely frequent reads of the same few keys (hot keys), DAX reduces the load on the DynamoDB table and delivers faster responses without requiring any changes to the partition key design.
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 →
Same concept, more angles
1 more ways this is tested on SAA-C03
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An application repeatedly reads the same DynamoDB items with very low latency requirements. The application can tolerate slightly stale data (for example, within a few seconds). You want to improve read latency without changing the existing DynamoDB table schema. Which service is the best choice?
easy- ✓ A.Amazon DAX
- B.Amazon S3 Transfer Acceleration
- C.Amazon EFS
- D.AWS CloudTrail for data plane reads
Why A: Amazon DAX (DynamoDB Accelerator) is an in-memory cache that sits between your application and DynamoDB, providing microsecond read latency for frequently accessed items. Since the application can tolerate slightly stale data (within seconds), DAX's default TTL-based caching is ideal because it reduces read pressure on DynamoDB while serving cached results with significantly lower latency than direct DynamoDB reads.
Last reviewed: Jun 11, 2026
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.