Free AWS Certified Developer Associate DVA-C02 Practice Question

In this scenario, employing an eventual consistency model is the correct approach. The application can tolerate some level of latency in reflecting new data (the high scores), which does not necessitate immediate consistency across all nodes. Eventual consistency will allow the system to provide higher read throughput due to the relaxed synchronization requirements, while scores converge to consistency within an acceptable timeframe for the gaming leaderboard context. The option suggesting Read-After-Write consistency is incorrect as it generally targets scenarios where immediate reflection of new data is needed after a write. This is not mentioned as a requirement for the gaming company's leaderboard, where a delay in data propagation is acceptable. A Causal consistency model is also inappropriate, as causal consistency ensures that causally related operations are seen by all processes in the same order but does not necessarily provide the balance required between read performance and eventual consistency for high score updates in different regions. Using Global Secondary Indexes is a feature to enhance database access patterns and is irrelevant to the specific consistency model requirement.