easymultiple choiceObjective-mapped

Your application uses ElastiCache Redis as a cache for user profiles stored in DynamoDB. You must ensure that when a profile is updated, subsequent reads see the latest value quickly. Which cache strategy is generally the best fit for this requirement?

Question 1easymultiple choice
Full question →

Your application uses ElastiCache Redis as a cache for user profiles stored in DynamoDB. You must ensure that when a profile is updated, subsequent reads see the latest value quickly. Which cache strategy is generally the best fit for this requirement?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Write to DynamoDB only, and never update or invalidate the Redis cache.

Never invalidating means stale data may persist in cache until it naturally expires. That conflicts with the requirement for quick visibility of updates. This design sacrifices correctness for simplicity.

B

Best answer

Use a cache-aside approach with TTL plus explicit invalidation after writes.

A cache-aside (lazy loading) pattern reads from cache first; if missing/expired, it fetches from the source of truth. After an update, explicitly invalidating or updating the cached entry ensures subsequent reads quickly reflect changes. TTL provides protection against missed invalidations while invalidation accelerates correctness after writes.

C

Distractor review

Cache only for reads, and do not fetch from DynamoDB when a key is missing.

If you do not fetch from DynamoDB on cache misses, you can return empty or incorrect responses. Cache-aside requires falling back to the source of truth. This option would break the functionality under cache misses.

D

Distractor review

Rely on eventual consistency of Redis replication to propagate updates to all nodes.

Redis replication behavior is not a substitute for explicit cache invalidation for application-level correctness. Even if replication converges, stale cached entries may still be returned. Correctness needs a strategy tied to write events.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Use a cache-aside approach with TTL plus explicit invalidation after writes. — Cache correctness after updates is best handled by pairing a cache-aside pattern with explicit invalidation (or cache update) when the underlying data changes. With cache-aside, reads check Redis first and fall back to the source of truth (DynamoDB) on a miss or expiry. After a write, invalidating the specific cached key makes the next read repopulate from DynamoDB quickly. TTL also helps limit the impact of missed invalidations. Why others are wrong: Option A guarantees staleness because updates never affect the cache. Option C breaks reads when Redis misses by preventing fallback to DynamoDB. Option D assumes replication will fix application correctness, but cached entries still need coordinated invalidation. Explicit invalidation with cache-aside is the commonly used approach to quickly converge on correct data.

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.

Discussion

Loading comments…

Sign in to join the discussion.