DynamoDB and NoSQL Foundations Challenge Quiz

1. Data Modeling in NoSQL

   In the context of NoSQL data modeling, which approach is most efficient for querying user order history in a single request, assuming each user has thousands of orders?

   1. Denormalizing order data within each user record
   2. Using a highly normalized relational schema
   3. Splitting orders into multiple tables by year
   4. Storing each order in a separate file on disk
   5. Aggregating order IDs in a query-time loop

2. Partition Key Selection

   When designing a table to store sensor data where each sensor generates millions of records daily, which is the best reason for choosing a composite primary key with a sensor ID partition key and a timestamp sort key?

   1. It enables efficient queries on a single sensor’s time series data
   2. It limits duplicate data by design
   3. It reduces storage costs by compressing the partition key
   4. It automatically enforces referential integrity between sensors
   5. It prevents eventual consistency issues on write operations

3. Global Secondary Indexes

   Which statement best describes a scenario where a global secondary index is essential in a table storing product catalog data?

   1. You need to query products by category regardless of the partition key
   2. You want to enforce uniqueness of product names
   3. You only require queries on primary key attributes
   4. You need to store large binary files as attributes
   5. You are optimizing bulk write throughput

4. Eventual Consistency Implications

   Given a high-traffic application using eventual consistency for reads, what is a potential risk if two clients read the same item immediately after an update?

   1. Clients may observe stale data until full replication occurs
   2. Table schema will become inconsistent
   3. Data will be permanently lost from the system
   4. Write throughput will be throttled for those clients
   5. Clients will always observe the most recent update

5. Conditional Writes in NoSQL

   If you want to prevent overwriting an existing attribute in a NoSQL item unless it matches a specific value, which mechanism should you use?

   1. Conditional expressions in write operations
   2. Batch get requests
   3. Manual sorting of attributes
   4. Read-after-write consistency
   5. Incremental backup configuration