Answer – A and D
The AWS Documentation mentions the following
Because a Scan operation reads an entire page (by default, 1 MB), you can reduce the impact of the scan operation by setting a smaller page size. The Scan operation provides a Limit parameter that you can use to set the page size for your request. Each Query or Scanrequest that has a smaller page size uses fewer read operations and creates a "pause" between each request.
If possible, you should avoid using a Scan operation on a large table or index with a filter that removes many results. Also, as a table or index grows, the Scan operation slows. The Scan operation examines every item for the requested values and can use up the provisioned throughput for a large table or index in a single operation. For faster response times, design your tables and indexes so that your applications can use Queryinstead of Scan. (For tables, you can also consider using the GetItem and BatchGetItem APIs.)
The other options are incorrect as these would slow down the query performance
For more information on the best practices for DynamoDB, please visit the url
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-query-scan.html