Question 293 of 1,040
Design Secure ArchitecturesmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to add DynamoDB Accelerator (DAX), a fully managed in-memory cache that reduces DynamoDB read latency from milliseconds to microseconds for frequently accessed items. This works because DAX sits between your application and the table, serving cached results for repeated reads without consuming read capacity units, which is ideal when eventually consistent reads are acceptable. On the SAA-C03 exam, this scenario tests your understanding of caching strategies for read-heavy workloads with minimal disruption—the common trap is suggesting a read replica or global table, which require schema changes or cross-region complexity. Remember the key distinction: DAX is for hot data read acceleration, not for write scaling or global distribution. Memory tip: “DAX for data access, not for distance.”

SAA-C03 Design Secure Architectures Practice Question

This SAA-C03 practice question tests your understanding of design secure 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.

A mobile app reads the same product catalog items repeatedly throughout the day. The DynamoDB table is already properly keyed, but read latency is still a problem during sales events. The team can tolerate eventually consistent reads and wants the least disruptive change. What should they add?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "least"

    Why it matters: You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.

Question 1mediummultiple choice
Full question →

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

Enable DynamoDB Accelerator to cache frequently accessed items in memory.

DynamoDB Accelerator (DAX) is a fully managed, in-memory cache that reduces read latency for frequently accessed items by orders of magnitude, from single-digit milliseconds to microseconds. Since the team can tolerate eventually consistent reads, DAX is ideal because it caches read results and serves them without additional DynamoDB read capacity consumption, making it the least disruptive change — no schema changes or application rewrites are required.

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 global secondary index for every frequently viewed product attribute.

    Why it's wrong here

    A GSI helps with alternative query patterns, but it does not function as an in-memory cache for repeated reads of the same items. Creating more indexes also increases write cost and design complexity. The workload already has a good key design, so the real problem is read latency on hot items, not the absence of a query path.

  • Enable DynamoDB Accelerator to cache frequently accessed items in memory.

    Why this is correct

    DynamoDB Accelerator, or DAX, is the best fit for repeated reads of the same items when eventual consistency is acceptable. It provides an in-memory cache in front of DynamoDB and can dramatically reduce read latency for hot catalog items during traffic spikes. Because the table schema is already sound, DAX adds performance without forcing a redesign of keys or access patterns.

    Clue confirmation

    The clue word "least" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Switch the table to on-demand capacity mode to reduce latency.

    Why it's wrong here

    On-demand capacity simplifies scaling, but it does not provide caching or directly reduce per-request latency for repeated reads. It helps absorb traffic variability, yet the underlying read path still goes to DynamoDB. In this scenario, the issue is fast access to hot items, so capacity mode alone is not enough.

  • Move the catalog to Aurora and use a read replica for every region.

    Why it's wrong here

    Migrating to Aurora would introduce a different database model and does not address the immediate problem in the simplest way. Read replicas can help with relational read scaling, but they are not a drop-in optimization for this DynamoDB workload. The question specifically asks for the least disruptive change, and DAX preserves the current architecture.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse throughput scaling (on-demand capacity) with latency reduction, or they over-engineer the solution by migrating to a different database when a simple caching layer (DAX) is the least disruptive and most cost-effective fix.

Trap categories for this question

  • Scenario analysis trap

    On-demand capacity simplifies scaling, but it does not provide caching or directly reduce per-request latency for repeated reads. It helps absorb traffic variability, yet the underlying read path still goes to DynamoDB. In this scenario, the issue is fast access to hot items, so capacity mode alone is not enough.

Detailed technical explanation

How to think about this question

DAX maintains a write-through cache that is eventually consistent with the DynamoDB table, meaning reads from DAX may return stale data until the cache is invalidated or updated. Under the hood, DAX uses a cluster of nodes with a primary node handling writes and replicas serving reads, and it supports both strongly consistent and eventually consistent read modes. In real-world scenarios, DAX is particularly effective for read-heavy workloads like product catalogs, gaming leaderboards, or session stores where latency spikes during flash sales or viral events.

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.

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.

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 Secure Architectures — This question tests Design Secure Architectures — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Enable DynamoDB Accelerator to cache frequently accessed items in memory. — DynamoDB Accelerator (DAX) is a fully managed, in-memory cache that reduces read latency for frequently accessed items by orders of magnitude, from single-digit milliseconds to microseconds. Since the team can tolerate eventually consistent reads, DAX is ideal because it caches read results and serves them without additional DynamoDB read capacity consumption, making it the least disruptive change — no schema changes or application rewrites are required.

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: "least". You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More SAA-C03 practice questions

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

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.