Single-table design methodology in DynamoDB - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main idea behind single-table design in DynamoDB?

Single-table design means storing different types of related data in one table using carefully designed keys and attributes to efficiently query and manage data.

beginner

Why do we use composite primary keys in single-table design?

Composite primary keys combine a partition key and a sort key to organize and access related items efficiently within the same table.

intermediate

How does single-table design improve query performance?

It reduces the number of queries by grouping related data in one table and using keys to fetch multiple related items in a single request.

intermediate

What role do secondary indexes play in single-table design?

Secondary indexes let you query the table using different keys, helping to access data in multiple ways without duplicating tables.

advanced

Name one challenge of single-table design.

It can be complex to plan and maintain because you must carefully design keys and attributes to handle many data types and access patterns.

What does a composite primary key in DynamoDB consist of?

A Primary key and foreign key

B Partition key and secondary index

C Partition key and sort key

D Sort key and global index

A composite primary key combines a partition key and a sort key to uniquely identify items.

Why is single-table design preferred in DynamoDB?

A To store all data in one table for efficient queries

B To separate data into many tables for clarity

C To avoid using indexes

D To use SQL joins easily

Single-table design stores related data in one table to reduce queries and improve performance.

What is a benefit of using secondary indexes in single-table design?

A They allow querying data with different keys

B They delete duplicate data automatically

C They increase table size

D They replace the primary key

Secondary indexes let you query the table using alternative keys without duplicating data.

Which of the following is a challenge of single-table design?

A Requires SQL joins

B Too many tables to manage

C No support for queries

D Complex key design and maintenance

Single-table design requires careful planning of keys and attributes, which can be complex.

In single-table design, how are different item types distinguished?

A By storing them in separate tables

B Using an attribute like 'item type' or prefix in keys

C By using different databases

D By using SQL joins

Different item types are identified by attributes or key prefixes within the same table.

Explain the concept of single-table design in DynamoDB and why it is useful.

Think about how grouping related data helps when you want to get many things at once.

Describe how secondary indexes support single-table design and give an example of their use.

Indexes are like extra ways to find data without changing the main table.