Lambda trigger on stream events in DynamoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the event source for the Lambda trigger.

DynamoDB

EventSourceArn: [1]

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

Aarn:aws:sqs:region:account-id:queue_name

Barn:aws:s3:::bucket_name

Carn:aws:dynamodb:region:account-id:table/TableName/stream/label

Darn:aws:lambda:region:account-id:function:FunctionName

Attempts:

3 left

💡 Hint

Common Mistakes

Using an S3 bucket ARN instead of a DynamoDB stream ARN.

Using the Lambda function ARN as the event source.

Using an SQS queue ARN instead of a DynamoDB stream ARN.

The event source ARN must point to the DynamoDB stream ARN to trigger the Lambda on stream events.

2fill in blank

medium

Complete the code to specify the batch size for the Lambda event source mapping.

DynamoDB

BatchSize: [1]

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

A10

B100

C1000

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Setting batch size too high causing timeouts.

Setting batch size too low causing inefficient processing.

The batch size defines how many records the Lambda function receives in one batch. 100 is a common default for DynamoDB streams.

3fill in blank

hard

Fix the error in the code to enable the Lambda trigger on the DynamoDB stream.

DynamoDB

StartingPosition: [1]

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

ATRIM_HORIZON

BBEGINNING

CLATEST

DEARLIEST

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'BEGINNING' or 'EARLIEST' which are invalid for DynamoDB streams.

Using 'LATEST' when you want to process all existing records.

The correct starting position for DynamoDB streams is 'TRIM_HORIZON' to start from the oldest available record.

4fill in blank

hard

Fill both blanks to create a Lambda event source mapping with enabled status and correct batch size.

DynamoDB

EventSourceArn: [1], BatchSize: [2]

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

Aarn:aws:dynamodb:region:account-id:table/TableName/stream/label

B50

C100

Darn:aws:s3:::bucket_name

Attempts:

3 left

💡 Hint

Common Mistakes

Using an S3 ARN instead of DynamoDB stream ARN.

Choosing batch size too small or too large.

The event source ARN must be the DynamoDB stream ARN and batch size 100 is a good choice for processing.

5fill in blank

hard

Fill all three blanks to configure a Lambda trigger with event source ARN, batch size, and starting position.

DynamoDB

EventSourceArn: [1], BatchSize: [2], StartingPosition: [3]

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

Aarn:aws:dynamodb:region:account-id:table/TableName/stream/label

B100

CTRIM_HORIZON

DLATEST

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'LATEST' as starting position when wanting to process all records.

Using incorrect ARN or batch size.

Use the DynamoDB stream ARN, batch size 100, and starting position 'TRIM_HORIZON' to process all stream records from the beginning.