Answer:
Datasets with Many-to-Many Relationships stored in DynamoDB should be spread across more than one table
Option (D) is true.
Step-by-step explanation:
DynamoDB is a NoSQL database that stores data in key-value pairs.
This means that each item in a DynamoDB table has a unique key that identifies it.
Many-to-many relationships are difficult to store in a NoSQL database because they require additional data structures to keep track of the relationships between items.
Datasets with many-to-many relationships should be spread across more than one table because this will make it easier to query and update the data.
For example, a dataset that stores information about students and courses could be divided into two tables: one for students and one for courses.
The student table would have a key that is the student's ID, and the course table would have a key that is the course's ID.
Each table would also have a field that stores the IDs of the other items in the relationship.
This would allow you to easily query for all of the courses that a student is taking or all of the students that are taking a particular course.
The other options are not as good because they do not take into account the many-to-many relationship between items.
For example, datasets with time-series data can be stored in a single table if the time is used as the key.
Datasets with similar access patterns can also be stored in a single table if the access patterns are similar enough.
However, datasets with many-to-many relationships will always be more difficult to store and query in a single table.
Therefore,
Datasets with Many-to-Many Relationships.
Option (D) is true.