Which table configuration will result in the lowest impact on provisioned throughput for this query?

An application stores payroll information nightly in DynamoDB for a large number of
employees across hundreds of offices. Item attributes consist of individual name, office
identifier, and cumulative daily hours. Managers run reports for ranges of names working in
their office. One query is. “Return all Items in this office for names starting with A through
E”. Which table configuration will result in the lowest impact on provisioned throughput for
this query?

An application stores payroll information nightly in DynamoDB for a large number of
employees across hundreds of offices. Item attributes consist of individual name, office
identifier, and cumulative daily hours. Managers run reports for ranges of names working in
their office. One query is. “Return all Items in this office for names starting with A through
E”. Which table configuration will result in the lowest impact on provisioned throughput for
this query?

A.
Configure the table to have a range index on the name attribute, and a hash index on the
office identifier

B.
Configure a hash index on the name attribute and no range index

C.
Configure the table to have a hash index on the name attribute, and a range index on the
office identifier

D.
Configure a hash index on the office Identifier attribute and no range index



Leave a Reply 6

Your email address will not be published. Required fields are marked *


raysmithvic1978

raysmithvic1978

A

Ahmed

Ahmed

C because the hash will be the name and the range is the office

Ahmed

Ahmed

A correct sorry

Pits - AWS SA

Pits - AWS SA

A Configure the table to have a range index on the name attribute, and a hash index on the
office identifier

Ismail Sajjad

Ismail Sajjad

C

A composite key with UserID as the partition key and the timestamp as the sort key would be best. The other answers offer non-standard key configurations.