A development team is refactoring and migrating a legacy application to AWS services. The legacy application uses a relational SQL-based database. The team intends to use a NoSQL DynamoDB database in AWS. What is the first action the team should take when designing the application data model for DynamoDB?

Answer options:

A.Map relational SQL tables to DynamoDB tables.
B.Convert SQL table DDL to DynamoDB table schemas.
C.Identify database query access patterns.
D.Identify data capacity requirements.

Answer: C
Option A is incorrect because data models from relational to non-relational databases do not map tables one-to-one. Relational data models focus on entity relationships. By contrast, non-relational data models focus on keeping related data together. In general, it is desirable to have as few DynamoDB tables as possible. Well-designed applications utilize a single-table design model.
Option B is incorrect because modeling data from the relational data model to the non-relational data model would not convert SQL table DDL’s directly to DynamoDB schemas. Relational data models focus on entity relationships. By contrast, non-relational data models focus on keeping related data together.
Option C is CORRECT because the first and most important step in designing a DynamoDB application is to identify the data query access patterns that the application utilizes and model the database based on those patterns.
Option D is incorrect because data capacity requirement is not an important consideration when designing DynamoDB applications.
Reference:
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-general-nosql-design.html