[{"id":"dynamodbbeginner-001","courseId":"dynamodb-beginner","domain":"data-modeling","topic":"Tables, items and attributes","prompt":"A teammate asks how a DynamoDB table compares with a spreadsheet. Each person's details go in one row, and each detail goes in one column. Which DynamoDB term is the equivalent of one row?","hint":"Think about the unit that groups several attributes together.","explain":"Data in DynamoDB is nested in layers. The outer layer is a collection of records, and each record is built from named fields. Consider which layer holds the fields and which holds the records.","source":"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.CoreComponents.html","interaction":{"type":"single"},"options":[{"id":"a","text":"An item","why":"An item groups several attributes into one record, like a row in a relational table."},{"id":"b","text":"A table","whyNot":"A table is the whole collection of items, the spreadsheet itself rather than one row."},{"id":"c","text":"An attribute","whyNot":"An attribute is one fundamental data element, closer to a single column or field."},{"id":"d","text":"A partition","whyNot":"A partition is internal physical storage DynamoDB uses to place items; it isn't a record you define."}],"answer":"a","explanation":"A table is a collection of items, and each item is a collection of attributes. Items are similar to rows, and attributes are similar to fields or columns.","concept":"A table is a collection of items, and each item is a collection of attributes. Items are similar to rows, and attributes are similar to fields or columns.","rev":1,"updatedAt":"2026-10-26","kind":"scenario","takeaways":["A table holds items, and each item holds attributes."]},{"id":"dynamodbbeginner-002","courseId":"dynamodb-beginner","domain":"data-modeling","topic":"Partition-key-only primary key","prompt":"A People table has one key, PersonID, which is its partition key. A teammate wants two items that share the same PersonID value. Which statement describes what this key design allows?","hint":"Think about how many items one key value can point to when the key has no second part.","explain":"A primary key must identify each record in a table, and it can be a single field or a pair of fields. Think about what a single field must guarantee on its own.","source":"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.CoreComponents.html","interaction":{"type":"single"},"options":[{"id":"a","text":"Each PersonID value can belong to only one item.","why":"With a partition key alone, no two items can have the same partition key value."},{"id":"b","text":"PersonID values can repeat if the other attributes differ.","whyNot":"Uniqueness applies to the key itself, so differing other attributes don't allow a repeat."},{"id":"c","text":"Items sharing a PersonID are stored together, sorted by a second key.","whyNot":"That describes a composite key, which adds a sort key; this table has no sort key."},{"id":"d","text":"PersonID can repeat, because the hash only chooses a storage location.","whyNot":"The hash picks the partition, but it doesn't relax the rule that partition key values are unique here."}],"answer":"a","explanation":"In a table whose primary key is only a partition key, no two items can have the same partition key value. The partition key is hashed to choose where the item is stored.","concept":"In a table whose primary key is only a partition key, no two items can have the same partition key value. The partition key is hashed to choose where the item is stored.","rev":1,"updatedAt":"2026-10-26","kind":"scenario","takeaways":["A partition-key-only primary key must be unique by itself."]},{"id":"dynamodbbeginner-003","courseId":"dynamodb-beginner","domain":"data-modeling","topic":"Composite primary key","prompt":"A Music table uses Artist as the partition key and SongTitle as the sort key. Which TWO statements about this composite primary key are correct?","hint":"Ask whether uniqueness applies to each field alone or to the pair together.","explain":"A key can pair two fields. The second tells apart records that share the first, and it allows a lookup on a range. Consider what must be unique, and what a lookup can start from.","source":"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.CoreComponents.html","interaction":{"type":"multiple","tellCount":true},"options":[{"id":"a","text":"Two items can share an Artist, as long as their SongTitle values differ.","why":"Items may share a partition key value, but each must have a different sort key value."},{"id":"b","text":"Supplying only the Artist value retrieves all songs by that artist.","why":"Given only the partition key value, DynamoDB returns every item that has that value."},{"id":"c","text":"Two items can't share an Artist, because the partition key must be unique.","whyNot":"That rule belongs to a simple key; with a sort key, the partition key can repeat."},{"id":"d","text":"SongTitle must be unique across the whole table, not per artist.","whyNot":"Uniqueness applies to the pair of Artist and SongTitle, so one title can appear under different artists."},{"id":"e","text":"Supplying only the Artist value returns nothing; both key fields are required.","whyNot":"A request on the partition key alone works and returns the songs for that artist."},{"id":"f","text":"Two items can share both Artist and SongTitle if their Price differs.","whyNot":"The pair must be unique; a differing non-key attribute such as Price doesn't allow a repeated key."}],"answer":"ab","explanation":"With a partition key and a sort key, items may share a partition key value but must differ in sort key value. A request that gives only the partition key value retrieves all of its items.","concept":"With a partition key and a sort key, items may share a partition key value but must differ in sort key value. A request that gives only the partition key value retrieves all of its items.","rev":1,"updatedAt":"2026-10-26","kind":"scenario","takeaways":["In a composite key, uniqueness belongs to the pair of fields."]},{"id":"dynamodbbeginner-004","courseId":"dynamodb-beginner","domain":"data-modeling","topic":"Schemaless attributes","prompt":"A Department table is keyed on DepartmentID. Statement to judge: apart from the primary key, each item in the table may have its own set of attributes.","hint":"Consider how much of each item's shape the table definition fixes.","explain":"When you create a table, you name its primary key. Whether other attributes must be declared beforehand is a separate matter, decided by how strictly the database enforces shape.","source":"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.CoreComponents.html","interaction":{"type":"true-false"},"options":[{"id":"a","text":"True","why":"Other than the primary key, attributes aren't declared beforehand, so items can differ from one another."},{"id":"b","text":"False","whyNot":"That would hold only if every item had to match a fixed column list, which DynamoDB doesn't require."}],"answer":"a","explanation":"Other than the primary key, DynamoDB is schemaless: attribute names and data types need not be defined beforehand, and each item can have its own distinct attributes.","concept":"Other than the primary key, DynamoDB is schemaless: attribute names and data types need not be defined beforehand, and each item can have its own distinct attributes.","rev":1,"updatedAt":"2026-10-26","kind":"scenario","takeaways":["Only the primary key is fixed when you create a table."]},{"id":"dynamodbbeginner-005","courseId":"dynamodb-beginner","domain":"data-modeling","topic":"Nested attribute depth","prompt":"A team stores an order as a map that holds lists, which hold more maps. What is the deepest nesting DynamoDB supports for these document types?","hint":"The answer is a fixed number of nesting levels stated in the quotas.","explain":"Document types such as maps and lists can hold other maps and lists, so structures can grow deep. DynamoDB caps that depth separately from the overall size of an item.","source":"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Constraints.html","interaction":{"type":"single"},"options":[{"id":"a","text":"32 levels","why":"DynamoDB supports nested attributes up to 32 levels deep, a documented limit."},{"id":"b","text":"8 levels","whyNot":"Eight is too shallow; DynamoDB documents a deeper limit of 32 levels."},{"id":"c","text":"64 levels","whyNot":"Doubling a figure is a guess; the documented nesting limit is 32 levels."},{"id":"d","text":"No depth limit; only the 400 KB item size applies","whyNot":"The item size cap still applies, but nesting depth is limited separately to 32 levels."}],"answer":"a","explanation":"DynamoDB supports nested attributes up to 32 levels deep. This depth limit is separate from the 400 KB maximum item size.","concept":"DynamoDB supports nested attributes up to 32 levels deep. This depth limit is separate from the 400 KB maximum item size.","rev":1,"updatedAt":"2026-10-26","kind":"scenario","takeaways":["Nesting depth and item size are two separate limits."]}]