A company uses Amazon DynamoDB as a data store for multi-tenant data. Approximately 70% of the reads by the company’s application are strongly consistent. The current key schema for the DynamoDB table is as follows: Partition key: OrgID – Sort key: TenantID#Version – Due to a change in design and access patterns, the company needs to support strongly consistent lookups based on the new schema below: Partition key: OrgID#TenantID – Sort key: Version – How can the database specialist implement this change?

Topic #: - All AWS Certified Database - Specialty Questions

A. Create a global secondary index (GSI) on the existing table with the specified partition and sort key.
B. Create a local secondary index (LSI) on the existing table with the specified partition and sort key.
C. Create a new table with the specified partition and sort key. Create an AWS Glue ETL job to perform the transformation and write the transformed data to the new table. Most Voted
D. Create a new table with the specified partition and sort key. Use AWS Database Migration Service (AWS DMS) to migrate the data to the new table.

- Awsexamhub website is not related to, affiliated with, endorsed or authorized by Amazon.
- Trademarks, certification & product names are used for reference only and belong to Amazon.

Suggested Answer:

Share this post

Join the Discussion