Tables, items, and attributes in AWS - Step-by-Step Execution

Process Flow - Tables, items, and attributes

Create Table

↓

Table Exists

↓

Add Item

↓

Item Contains Attributes

↓

Query or Update Item

↓

Return Results or Modify Attributes

This flow shows how a table is created, items are added with attributes, and then queried or updated.

Execution Sample

AWS

CreateTable(TableName)
PutItem(TableName, Item)
GetItem(TableName, Key)
UpdateItem(TableName, Key, AttributeUpdates)

This code creates a table, adds an item with attributes, retrieves it, and updates attributes.

Process Table

Step	Action	Input	State Change	Output
1	CreateTable	TableName='Users'	Table 'Users' created with no items	Success
2	PutItem	Table='Users', Item={UserID: '123', Name: 'Alice', Age: 30}	Item added to 'Users' table	Success
3	GetItem	Table='Users', Key={UserID: '123'}	No state change	Item returned: {UserID: '123', Name: 'Alice', Age: 30}
4	UpdateItem	Table='Users', Key={UserID: '123'}, AttributeUpdates={Age: 31}	Item attribute 'Age' updated to 31	Success
5	GetItem	Table='Users', Key={UserID: '123'}	No state change	Item returned: {UserID: '123', Name: 'Alice', Age: 31}
6	End	No input	No state change	Process complete

💡 Process ends after item is updated and retrieved with new attribute value.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
Table 'Users'	Does not exist	Exists, empty	Contains 1 item: {UserID: '123', Name: 'Alice', Age: 30}	No change	Item updated: Age=31	No change	Contains updated item
Item	N/A	N/A	{UserID: '123', Name: 'Alice', Age: 30}	Returned same item	{UserID: '123', Name: 'Alice', Age: 31}	Returned updated item	Final updated item

Key Moments - 3 Insights

Why does the table exist but have no items after creation?

After Step 1 in the execution_table, the table is created empty. Items are added later in Step 2.

How does updating an attribute affect the item?

In Step 4, only the specified attribute 'Age' is changed from 30 to 31; other attributes remain the same.

Why does GetItem not change the state?

GetItem (Steps 3 and 5) only reads data; it does not modify the table or items, so state remains unchanged.

Visual Quiz - 3 Questions

Look at the execution_table, what is the Age attribute of the item after Step 2?

A 30

B 31

C Not set

D Null

💡 Hint

Check the 'State Change' column in Step 2 where the item is added with Age 30.

At which step does the Age attribute get updated to 31?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Action' and 'State Change' columns in Step 4 for attribute updates.

If we skip Step 4, what would be the Age attribute after Step 5?

A 31

B 30

C Null

D Undefined

💡 Hint

Refer to variable_tracker and note that without update, Age remains as initially set.

Concept Snapshot

Tables store items, which are like rows.
Items have attributes, like columns with values.
Create a table first, then add items.
You can get or update items by key.
Updates change only specified attributes.
Get operations do not change data.

Full Transcript

This visual execution shows how AWS tables work with items and attributes. First, a table named 'Users' is created empty. Then, an item with UserID '123', Name 'Alice', and Age 30 is added. Getting the item returns its current attributes without changing anything. Updating the item changes the Age attribute to 31. Getting the item again shows the updated Age. This process demonstrates how tables hold items, items have attributes, and how these attributes can be read or updated without affecting other data.

Practice

1. What is the main purpose of a table in AWS DynamoDB?

easy

A. To store items, which are records

B. To run code functions

C. To manage user permissions

D. To host websites

Solution

1. Step 1: Understand the role of a table in DynamoDB

   A table is a container that holds items, which are like rows in a database.

2. Step 2: Identify the correct purpose

   Since tables store items (records), this matches To store items, which are records.

3. Final Answer:

   To store items, which are records -> Option A

4. Quick Check:

   Table = container for items [OK]

Hint: Tables hold records called items [OK]

Common Mistakes:

• Confusing tables with code functions
• Thinking tables manage permissions
• Assuming tables host websites

2. Which of the following is the correct way to define an item attribute in DynamoDB?

easy

A. ("Name", "John", "Age", 30)

B. {"Name": "John", "Age": 30}

C. ["Name", "John", "Age", 30]

D. "Name": "John", "Age": 30

Solution

1. Step 1: Recognize the attribute format

   Attributes are key-value pairs, best represented as JSON objects with keys and values.

2. Step 2: Match the correct syntax

   {"Name": "John", "Age": 30} shows a JSON object with keys "Name" and "Age" and their values, which is correct.

3. Final Answer:

   {"Name": "John", "Age": 30} -> Option B

4. Quick Check:

   Attributes = key-value pairs in JSON [OK]

Hint: Attributes are key-value pairs in JSON format [OK]

Common Mistakes:

• Using arrays instead of key-value pairs
• Using tuples instead of objects
• Omitting braces for JSON objects

3. Given a DynamoDB table with primary key "UserID", what happens if you try to add two items with the same UserID but different attributes?

medium

A. Both items are stored separately

B. The table creates a duplicate primary key

C. An error is thrown and no item is added

D. The second item overwrites the first item

Solution

1. Step 1: Understand primary key uniqueness

   In DynamoDB, the primary key must be unique for each item in the table.

2. Step 2: Effect of duplicate primary key

   If you add an item with an existing primary key, it replaces the old item with the new one.

3. Final Answer:

   The second item overwrites the first item -> Option D

4. Quick Check:

   Duplicate key = overwrite existing item [OK]

Hint: Duplicate primary keys overwrite existing items [OK]

Common Mistakes:

• Thinking both items are stored separately
• Expecting an error on duplicate keys
• Assuming duplicates are allowed

4. You try to insert an item into a DynamoDB table but get an error. The item has no primary key attribute. What is the most likely cause?

medium

A. Missing required primary key attribute in the item

B. Table is full and cannot accept new items

C. Attributes have invalid data types

D. You exceeded the maximum number of attributes

Solution

1. Step 1: Recall primary key requirement

   Every item must have the primary key attribute to be uniquely identified in the table.

2. Step 2: Identify cause of error

   If the item lacks the primary key attribute, DynamoDB rejects it with an error.

3. Final Answer:

   Missing required primary key attribute in the item -> Option A

4. Quick Check:

   Primary key missing causes insert error [OK]

Hint: Every item must include the primary key attribute [OK]

Common Mistakes:

• Assuming table capacity causes insert errors
• Blaming attribute data types without checking keys
• Thinking attribute count limits cause this error

5. You want to design a DynamoDB table to store user profiles. Each user has a unique UserID and may have multiple email addresses. How should you structure the table and items to handle this?

hard

A. Use email as the primary key and ignore UserID

B. Use UserID as the primary key and create a separate item for each email

C. Use UserID as the primary key and store emails as a list attribute inside each item

D. Create multiple tables, one per email address

Solution

1. Step 1: Identify unique identifier

   UserID uniquely identifies each user, so it should be the primary key.

2. Step 2: Store multiple emails

   Since a user can have multiple emails, store them as a list attribute inside the user item.

3. Step 3: Evaluate other options

   Creating separate items per email duplicates UserID or loses uniqueness; using email as key ignores UserID; multiple tables is inefficient.

4. Final Answer:

   Use UserID as the primary key and store emails as a list attribute inside each item -> Option C

5. Quick Check:

   Primary key + list attribute for multiple values [OK]

Hint: Use primary key for user, list attribute for multiple emails [OK]

Common Mistakes:

• Using email as primary key instead of UserID
• Creating multiple items for one user
• Making multiple tables unnecessarily