A service performs many repeated read requests for the same DynamoDB items. The reads are latency-sensitive, but the application can tolerate slightly stale data. Which AWS service is the best fit to reduce read latency?

Amazon S3 Select

S3 Select queries data within S3 objects to reduce data transfer size. It does not provide low-latency caching for DynamoDB item reads and does not sit in front of DynamoDB like a managed accelerator.

Amazon SQS FIFO queue

SQS FIFO provides ordering and exactly-once processing semantics for messaging. It does not cache or accelerate database reads and has no role in reducing DynamoDB read latency.

AWS Lambda provisioned concurrency

Provisioned concurrency prevents Lambda cold starts by keeping execution environments warm. It does not change the latency of DynamoDB read operations themselves, nor does it cache DynamoDB data.

What does this SAA-C03 question test?

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) — Amazon DAX is the best fit because it is purpose-built to accelerate DynamoDB. DAX caches frequently accessed items in memory and serves many repeated read requests directly from the cache, reducing end-to-end latency. Since DAX may return slightly stale results from its cache (and can be tuned with TTL behavior), it aligns with the requirement that the application can tolerate minor staleness. S3 Select applies to querying S3 data, not DynamoDB reads, and would require a different storage and access model. SQS FIFO is for ordered message delivery and cannot reduce database latency. Lambda provisioned concurrency addresses function startup latency, not DynamoDB access latency or caching.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.