Question 530
A read-heavy application repeatedly queries the same session data and would benefit from low-latency in-memory access. What is the most appropriate next step?
Explanation
Correct Answer
An in-memory cache can reduce repeated backend reads without replacing the durable source of record.
Incorrect Answers
An in-memory cache can reduce repeated backend reads without replacing the durable source of record. That alternative applies to a different situation: A heterogeneous database migration needs schema and code conversion as well as moving the stored data between platforms.
An in-memory cache can reduce repeated backend reads without replacing the durable source of record. That alternative applies to a different situation: A company plans to migrate a production database into AWS while keeping source changes flowing through a staged cutover.
An in-memory cache can reduce repeated backend reads without replacing the durable source of record. That alternative applies to a different situation: A mobile game needs predictable key-value access to millions of player profiles without requiring relational joins.






AWS Certified Cloud Practitioner CLF-C02 Practice Tests