AWS Certified Developer Associate DVA-C02 Practice Question
A developer has implemented Amazon ElastiCache for Redis to cache frequently accessed data from an Amazon RDS database for a news application. Shortly after deployment, users report that they are sometimes seeing outdated headlines for several minutes after an editor has updated a story. What is the most likely cause of this issue?
High network latency exists between the application servers and the ElastiCache cluster.
The cache is not being invalidated when the data in the database changes.
The application is configured with an incorrect endpoint for the ElastiCache cluster.
The ElastiCache cluster has insufficient memory, causing frequent data evictions.
The most likely cause is a lack of a proper cache invalidation strategy. When data is cached, it becomes a separate copy from the source of truth (the database). If the data in the database is updated, the old, stale data will remain in the cache until it is explicitly invalidated or its Time-to-Live (TTL) expires. Insufficient cache memory would lead to cache misses, forcing the application to fetch fresh data from the database, not serve stale data. High network latency would slow down responses but not affect data correctness. Using an incorrect endpoint would likely cause connection failures.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are invalidation mechanisms in caching?
Open an interactive chat with Bash
How does Amazon ElastiCache improve application performance?
Open an interactive chat with Bash
What are the differences between stale data and fresh data in caching?
Open an interactive chat with Bash
AWS Certified Developer Associate DVA-C02
Troubleshooting and Optimization
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access