An application stores its data in a DynamoDB table. The application team finds that they have a new access pattern where the application has to perform strongly consistent queries on an attribute that’s not the partition key. How can the team solve this problem?

Answer options:

A.Create a new DynamoDB table.
B.Create a new GSI.
C.Create a new LSI.
D.Create a DynamoDB Accelerator (DAX) cluster.

Answer: A
Option A is CORRECT because the requirement is to perform strongly consistent queries on a new partition key. In this scenario, a new DynamoDB table must be created as GSI only supports eventual consistency.
Option B is incorrect because Global Secondary Indexes do not support strongly consistent reads (but only eventual consistency reads).
Option C is incorrect because Local Secondary Indexes use the same partition key as the base table.
Option D is incorrect because DynamoDB Accelerator is a caching solution for DynamoDB and is not suitable for use in this case. As a caching solution, it only allows queries on the same partition key as the base table.
Reference:
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/SecondaryIndexes.html