Why data protection is essential in DynamoDB - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a DynamoDB table named 'Users'.

DynamoDB

aws dynamodb create-table --table-name [1] --attribute-definitions AttributeName=UserId,AttributeType=S --key-schema AttributeName=UserId,KeyType=HASH --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5

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

ACustomers

BOrders

CUsers

DProducts

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong table name like 'Customers' or 'Orders'.

Leaving the table name blank.

The table name must be 'Users' as specified in the instruction.

2fill in blank

medium

Complete the code to add an item with UserId '123' to the 'Users' table.

DynamoDB

aws dynamodb put-item --table-name Users --item '{"UserId": {"S": "[1]"}}'

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

A001

B123

Cabc

Dxyz

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different UserId value.

Forgetting to put quotes around the UserId.

The UserId must be '123' as specified to add the correct item.

3fill in blank

hard

Fix the error in the code to get an item with UserId '123' from the 'Users' table.

DynamoDB

aws dynamodb get-item --table-name Users --key '{"UserId": {"[1]": "123"}}'

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

ABOOL

BN

CB

DS

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'N' which is for numbers.

Using 'B' which is for binary data.

The key type for UserId is string, so it must be 'S'.

4fill in blank

hard

Fill both blanks to update the 'Email' attribute of user '123' in the 'Users' table.

DynamoDB

aws dynamodb update-item --table-name Users --key '{"UserId": {"S": "123"}}' --update-expression "set [1] = :e" --expression-attribute-values '{":e": {"[2]": "[e-mail]"}}'

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

AEmail

BS

CN

DUserEmail

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong attribute names like 'UserEmail'.

Using wrong data types like 'N' for string values.

The attribute to update is 'Email' and its type is string 'S'.

5fill in blank

hard

Fill all three blanks to delete the item with UserId '123' from the 'Users' table.

DynamoDB

aws dynamodb delete-item --table-name [1] --key '{"UserId": {"[2]": "[3]"}}'

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

AOrders

BUsers

CS

D123

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong table names like 'Orders'.

Using wrong key types or values.

The table is 'Users', the key type is string 'S', and the UserId is '123'.

Practice

1. Why is data protection essential when using DynamoDB?

easy

A. It keeps your data safe and private from unauthorized access.

B. It makes your database run faster.

C. It automatically deletes old data.

D. It increases the size of your database.

Solution

1. Step 1: Understand the purpose of data protection

   Data protection is about keeping data safe and private, preventing unauthorized access.

2. Step 2: Identify the correct benefit in DynamoDB context

   Among the options, only keeping data safe and private matches the purpose of data protection.

3. Final Answer:

   It keeps your data safe and private from unauthorized access. -> Option A

4. Quick Check:

   Data protection = safety and privacy [OK]

Hint: Data protection means keeping data safe and private [OK]

Common Mistakes:

• Confusing data protection with performance improvements
• Thinking data protection deletes data automatically
• Assuming data protection increases database size

2. Which of the following is the correct way to enable encryption at rest in DynamoDB?

easy

A. Set EncryptionEnabled = true in the table creation parameters.

B. Use EnableEncryption = 'yes' in the AWS CLI command.

C. Add EncryptData: true in the item attributes.

D. Specify SSESpecification: { Enabled: true } when creating the table.

Solution

1. Step 1: Recall DynamoDB encryption syntax

   Encryption at rest is enabled by setting SSESpecification: { Enabled: true } during table creation.

2. Step 2: Check each option for correctness

   Only Specify SSESpecification: { Enabled: true } when creating the table. uses the correct syntax recognized by DynamoDB.

3. Final Answer:

   Specify SSESpecification: { Enabled: true } when creating the table. -> Option D

4. Quick Check:

   Encryption at rest = SSESpecification enabled [OK]

Hint: Look for SSESpecification with Enabled true [OK]

Common Mistakes:

• Using incorrect parameter names like EncryptionEnabled
• Trying to encrypt individual items instead of the table
• Using string values instead of boolean true

3. Consider this DynamoDB table with encryption enabled and IAM access control. What happens if a user without permission tries to read data?

medium

A. The request is denied due to lack of permissions.

B. The user can read the data without restrictions.

C. The data is returned but encrypted and unreadable.

D. The table automatically deletes the data.

Solution

1. Step 1: Understand IAM access control in DynamoDB

   IAM policies control who can access the table. Without permission, access is denied.

2. Step 2: Analyze the options based on access control

   Only The request is denied due to lack of permissions. correctly states that unauthorized requests are denied.

3. Final Answer:

   The request is denied due to lack of permissions. -> Option A

4. Quick Check:

   IAM access control denies unauthorized users [OK]

Hint: No permission means access denied, not encrypted data [OK]

Common Mistakes:

• Thinking data is returned but unreadable
• Assuming unauthorized users can read data
• Believing data is deleted automatically

4. You wrote this IAM policy to allow read access to a DynamoDB table but users still get AccessDenied errors. What is the likely problem?

{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Action": "dynamodb:GetItem",
    "Resource": "arn:aws:dynamodb:us-east-1:123456789012:table/MyTable"
  }]
}

medium

A. The Resource ARN is missing the index name.

B. The Action should include dynamodb:Query and dynamodb:Scan for read access.

C. The Effect should be Deny instead of Allow.

D. The Version date is incorrect.

Solution

1. Step 1: Identify required actions for read access

   Read access often requires multiple actions like GetItem, Query, and Scan.

2. Step 2: Check the policy actions

   The policy only allows GetItem, so Query and Scan requests will be denied.

3. Final Answer:

   The Action should include dynamodb:Query and dynamodb:Scan for read access. -> Option B

4. Quick Check:

   Read access needs GetItem, Query, Scan [OK]

Hint: Include all read actions: GetItem, Query, Scan [OK]

Common Mistakes:

• Assuming GetItem alone grants full read access
• Changing Effect to Deny by mistake
• Ignoring the need for multiple actions

5. You want to protect sensitive customer data in DynamoDB by encrypting it and restricting access. Which combination of features should you use?

hard

A. Disable encryption but restrict access with IP address filtering.

B. Use client-side encryption only and allow open access to the table.

C. Enable server-side encryption and use IAM policies for access control.

D. Store data in plain text and rely on backups for protection.

Solution

1. Step 1: Identify best practices for data protection in DynamoDB

   Encrypting data and controlling access are key to protecting sensitive information.

2. Step 2: Evaluate each option

   Enable server-side encryption and use IAM policies for access control. combines encryption and IAM access control, which is the recommended approach.

3. Final Answer:

   Enable server-side encryption and use IAM policies for access control. -> Option C

4. Quick Check:

   Encryption + access control = strong data protection [OK]

Hint: Combine encryption with access control for best protection [OK]

Common Mistakes:

• Relying only on client-side encryption without access control
• Disabling encryption and trusting IP filtering alone
• Storing sensitive data in plain text