Composite primary key in DynamoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a composite primary key with partition key 'UserId'.

DynamoDB

KeySchema: [{ AttributeName: 'UserId', KeyType: '[1]' }]

Drag options to blanks, or click blank then click option'

APRIMARY

BRANGE

CHASH

DINDEX

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'RANGE' instead of 'HASH' for the partition key.

Using 'PRIMARY' or 'INDEX' which are not valid KeyType values.

The partition key in DynamoDB is defined with KeyType 'HASH'.

2fill in blank

medium

Complete the code to add a sort key named 'OrderId' in the composite primary key.

DynamoDB

KeySchema: [
  { AttributeName: 'UserId', KeyType: 'HASH' },
  { AttributeName: 'OrderId', KeyType: '[1]' }
]

Drag options to blanks, or click blank then click option'

APRIMARY

BINDEX

CHASH

DRANGE

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'HASH' instead of 'RANGE' for the sort key.

Using 'PRIMARY' or 'INDEX' which are not valid KeyType values.

The sort key in DynamoDB is defined with KeyType 'RANGE'.

3fill in blank

hard

Fix the error in the attribute definitions for the composite primary key.

DynamoDB

AttributeDefinitions: [
  { AttributeName: 'UserId', AttributeType: '[1]' },
  { AttributeName: 'OrderId', AttributeType: 'S' }
]

Drag options to blanks, or click blank then click option'

AS

BBOOL

CB

DN

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'N' (number) when the attribute is a string.

Using 'BOOL' which is not valid for key attributes.

Both partition and sort keys must have a valid attribute type. 'S' means string type.

4fill in blank

hard

Fill both blanks to complete the table creation with composite primary key.

DynamoDB

CreateTable({
  TableName: 'Orders',
  KeySchema: [
    { AttributeName: '[1]', KeyType: 'HASH' },
    { AttributeName: '[2]', KeyType: 'RANGE' }
  ],
  AttributeDefinitions: [
    { AttributeName: 'UserId', AttributeType: 'S' },
    { AttributeName: 'OrderId', AttributeType: 'S' }
  ]
})

Drag options to blanks, or click blank then click option'

AUserId

BOrderDate

COrderId

DCustomerId

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping partition and sort key names.

Using attribute names not defined in AttributeDefinitions.

The composite primary key uses 'UserId' as partition key and 'OrderId' as sort key.

5fill in blank

hard

Fill all three blanks to define a composite primary key and attribute types correctly.

DynamoDB

CreateTable({
  TableName: 'Purchases',
  KeySchema: [
    { AttributeName: '[1]', KeyType: 'HASH' },
    { AttributeName: '[2]', KeyType: 'RANGE' }
  ],
  AttributeDefinitions: [
    { AttributeName: '[1]', AttributeType: 'S' },
    { AttributeName: '[2]', AttributeType: 'N' }
  ]
})

Drag options to blanks, or click blank then click option'

ACustomerId

BPurchaseDate

COrderId

DUserId

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatching attribute names between KeySchema and AttributeDefinitions.

Using wrong attribute types for keys.

The partition key is 'CustomerId' with type 'S' (string), and the sort key is 'PurchaseDate' with type 'N' (number).