Which design change should the solutions architect recommend?
Add read replicas to the table.
Use a global secondary index (GSI).
Request strongly consistent reads for the table.
Request eventually consistent reads for the table.
Explanations:
Amazon DynamoDB does not support read replicas. Instead, it provides strongly consistent and eventually consistent reads, which manage how data is read rather than how it is replicated. Therefore, adding read replicas is not a valid option for addressing issues with stale reads.
A global secondary index (GSI) allows for additional query patterns but does not address issues of stale data. It primarily facilitates different query access patterns but does not ensure that the latest data is read unless strongly consistent reads are specified.
Requesting strongly consistent reads ensures that the most recent data is returned for each read operation. Strongly consistent reads can be beneficial when it is critical to have the latest updates reflected immediately in query results. This option directly addresses the issue of not returning the latest data.
Eventually consistent reads allow for lower latency but can return stale data. Since the problem stated that users are not receiving the latest data, this option would not resolve the issue and may exacerbate it by potentially returning outdated information.
I organize that the answer is:
Request strongly consistent reads for the table.