Quick Answer
The answer is write-through caching. This strategy ensures data freshness by synchronously writing data to both the ElastiCache for Redis cluster and the underlying database in a single transaction, so every cache update reflects the latest database state without any stale reads. On the AWS Certified Data Engineer Associate DEA-C01 exam, this scenario tests your understanding of how write-through caching directly solves the freshness requirement that lazy loading fails to guarantee—a common trap is confusing write-through with write-behind, which prioritizes performance over consistency. Remember the memory tip: “Write-through writes to both, so freshness follows.”
This DEA-C01 practice question tests your understanding of data store management. 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.
An e-commerce application uses Amazon ElastiCache for Redis to cache product catalog data. The cache currently uses lazy loading. The team wants to ensure that frequently accessed product data is always fresh. Which caching strategy should they implement?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "always"
Why it matters: Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
Write-through caching
Write-through updates cache directly on writes, ensuring data is always fresh.
Set a TTL of 5 minutes for all cached items
Why wrong: TTL does not guarantee freshness if data changes within the TTL window.
Use database read replicas to serve data
Why wrong: Read replicas are for database scaling, not caching.
Lazy loading with TTL
Why wrong: Lazy loading may serve stale data until TTL expires.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Write-through caching
Write-through caching ensures that data is written to the cache simultaneously with the database, guaranteeing that frequently accessed product data is always fresh. This strategy eliminates stale reads by synchronously updating the cache on every write, which directly addresses the requirement for freshness without relying on expiration or lazy population.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Write-through caching
Why this is correct
Write-through updates cache directly on writes, ensuring data is always fresh.
Clue confirmation
The clue word "always" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Set a TTL of 5 minutes for all cached items
Why it's wrong here
TTL does not guarantee freshness if data changes within the TTL window.
Use database read replicas to serve data
Why it's wrong here
Read replicas are for database scaling, not caching.
Lazy loading with TTL
Why it's wrong here
Lazy loading may serve stale data until TTL expires.
Common exam traps
The trap here is that candidates often assume lazy loading with a short TTL is sufficient for freshness, but the exam tests the understanding that only write-through (or write-behind) strategies guarantee synchronous cache updates without relying on expiration windows.
Detailed technical explanation
In write-through caching, the application writes data to both the database and the ElastiCache Redis cluster within the same transaction, typically using Redis SET commands. This ensures cache coherence at the cost of increased write latency, but for read-heavy workloads with frequent access to the same keys, it eliminates the need for invalidation logic and guarantees that the cache reflects the latest database state. A real-world scenario is an e-commerce product detail page where inventory or pricing changes must be immediately visible to all users.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Data Store Management — study guide chapter
Learn the concepts, then practise the questions
Data Store Management practice questions
Targeted practice on this topic area only
All DEA-C01 questions
1,786 questions across all exam domains
AWS Certified Data Engineer Associate DEA-C01 study guide
Full concept coverage aligned to exam objectives
DEA-C01 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise DEA-C01 questions linked to Data Ingestion and Transformation.
Practise DEA-C01 questions linked to Data Operations and Support.
Practise DEA-C01 questions linked to Data Security and Governance.
Practise DEA-C01 questions linked to Data Store Management.
Practise DEA-C01 questions linked to DEA-C01 fundamentals.
Practise DEA-C01 questions linked to DEA-C01 scenario.
Practise DEA-C01 questions linked to DEA-C01 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Data Store Management — This question tests Data Store Management — Read the scenario before looking for a memorised answer..
The correct answer is: Write-through caching — Write-through caching ensures that data is written to the cache simultaneously with the database, guaranteeing that frequently accessed product data is always fresh. This strategy eliminates stale reads by synchronously updating the cache on every write, which directly addresses the requirement for freshness without relying on expiration or lazy population.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "always". Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
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 →
Last reviewed: Jun 11, 2026
This DEA-C01 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 DEA-C01 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.