Question

A developer's Lambda function reads customer profile items from a DynamoDB table using Query. Each item is roughly 40 KB and contains many nested attributes, but the function only needs the customer's name and email for a notification workflow. CloudWatch shows the function is consuming far more read capacity than expected and DynamoDB read costs are high. Which change most effectively reduces the consumed read capacity for these queries?

Accepted Answer

Add a ProjectionExpression to the Query request that returns only the name and email attributes.

Answer

Switch the Query to a Scan operation with a FilterExpression on name and email.

Answer

Enable a strongly consistent read on the Query to reduce the number of retries.

Answer

Increase the Limit parameter on the Query to fetch more items per request.