A developer is writing an application, which stores data in an Amazon DynamoDB table. The developer wants to query the DynamoDB table by using the partition key and a different sort key value. The developer needs the latest data with all recent write operations. How should the developer write the DynamoDB query?

Question

Accepted Answer

B. Add a local secondary index (LSI) during table creation. Query the LSI by using strongly An LSI shares the base table's partition key but allows a different sort key, enabling queries with the desired alternate sort key. Because LSIs are stored within the same partition as the base table, they support strongly consistent reads, which ensures all recent write operations are visible and the developer retrieves the most up-to-date data.

Answer

A. Add a local secondary index (LSI) during table creation. Query the LSI by using eventually An LSI with eventually consistent reads may return stale data that does not reflect the latest write operations, failing the requirement for the newest data.

Answer

C. Add a global secondary index (GSI) during table creation. Query the GSI by using eventually A GSI uses a separate distributed storage model and does not support strongly consistent reads; queries against a GSI are always eventually consistent.

Answer

D. Add a global secondary index (GSI) during table creation. Query the GSI by using strongly A GSI does not support strongly consistent reads, so querying it cannot guarantee that the latest write operations are reflected in the results.

A developer is writing an application, which stores data in an Amazon DynamoDB table. The developer wants to query the DynamoDB table by using the partition key and a different sort key value. The dev

Question

Options

How the community answered

Why each option

Community Discussion