Sending and receiving messages in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an SQS queue named 'MyQueue'.

AWS

aws sqs create-queue --queue-name [1]

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

AQueue1

BMyQueue

CTestQueue

DSampleQueue

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different queue name than 'MyQueue'.

Omitting the --queue-name option.

The command creates an SQS queue with the specified name. 'MyQueue' is the correct queue name here.

2fill in blank

medium

Complete the code to send a message with body 'HelloWorld' to the queue URL stored in QUEUE_URL.

AWS

aws sqs send-message --queue-url [1] --message-body HelloWorld

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

A$QUEUE_URL

BMyQueueUrl

CQUEUE_URL

DqueueUrl

Attempts:

3 left

💡 Hint

Common Mistakes

Not using the $ sign to reference the variable.

Using the queue name instead of the queue URL.

The variable $QUEUE_URL holds the queue URL. It must be referenced with a $ to expand its value in the shell.

3fill in blank

hard

Fix the error in the code to receive one message from the queue URL stored in QUEUE_URL.

AWS

aws sqs receive-message --queue-url [1] --max-number-of-messages 1

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

AqueueUrl

BQUEUE_URL

CMyQueueUrl

D$QUEUE_URL

Attempts:

3 left

💡 Hint

Common Mistakes

Using the variable name without $.

Using an incorrect variable name.

The queue URL variable must be referenced with a $ sign to expand its value in the shell.

4fill in blank

hard

Fill both blanks to set the visibility timeout to 30 seconds when receiving messages from the queue.

AWS

aws sqs receive-message --queue-url [1] --[2] 30

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

A$QUEUE_URL

Bvisibility-timeout

Cmax-number-of-messages

Dwait-time-seconds

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong option name for visibility timeout.

Not using $ to reference the queue URL variable.

The queue URL must be referenced with $QUEUE_URL. The option to set visibility timeout is --visibility-timeout.

5fill in blank

hard

Fill all three blanks to delete a message from the queue using its ReceiptHandle stored in RECEIPT_HANDLE.

AWS

aws sqs delete-message --queue-url [1] --receipt-handle [2] --region [3]

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

A$QUEUE_URL

B$RECEIPT_HANDLE

Cus-east-1

Dus-west-2

Attempts:

3 left

💡 Hint

Common Mistakes

Not using $ to reference variables.

Using incorrect region names.

Use $QUEUE_URL and $RECEIPT_HANDLE to reference the variables. The region is set to 'us-east-1' as a common default.

Practice

1. What is the main purpose of sending messages in a cloud message queue service like AWS SQS?

easy

A. To put data into a queue so other parts can use it later

B. To delete data permanently from the system

C. To directly update a database record

D. To create a new virtual machine

Solution

1. Step 1: Understand message sending in queues

   Sending messages means placing data into a queue for later use by other parts of the system.

2. Step 2: Identify the purpose of sending messages

   The purpose is to store data temporarily so it can be processed asynchronously, not to delete or update directly.

3. Final Answer:

   To put data into a queue so other parts can use it later -> Option A

4. Quick Check:

   Sending messages = storing data in queue [OK]

Hint: Sending messages means putting data in a queue for later use [OK]

Common Mistakes:

• Confusing sending with deleting data
• Thinking sending updates databases directly
• Assuming sending creates compute resources

2. Which AWS service is primarily used for sending and receiving messages in a queue?

easy

A. Amazon EC2

B. Amazon SQS

C. Amazon RDS

D. Amazon S3

Solution

1. Step 1: Identify AWS services for messaging

   Amazon SQS (Simple Queue Service) is designed for sending and receiving messages in queues.

2. Step 2: Differentiate from other services

   EC2 is for servers, RDS for databases, and S3 for storage, not messaging queues.

3. Final Answer:

   Amazon SQS -> Option B

4. Quick Check:

   Message queue service = Amazon SQS [OK]

Hint: SQS is AWS's queue service for messages [OK]

Common Mistakes:

• Choosing EC2 which is for servers
• Confusing S3 storage with messaging
• Selecting RDS which is a database

3. Consider this AWS CLI command to receive a message from an SQS queue:
aws sqs receive-message --queue-url https://sqs.us-east-1.amazonaws.com/123456789012/MyQueue --max-number-of-messages 1
What will this command do?

medium

A. Create a new queue named MyQueue

B. Send one message to the queue

C. Delete one message from the queue

D. Receive up to one message from the queue

Solution

1. Step 1: Analyze the AWS CLI command

   The command uses receive-message with --max-number-of-messages 1, which means it tries to get up to one message from the queue.

2. Step 2: Understand the effect of the command

   It does not send, delete, or create queues. It only retrieves messages for processing.

3. Final Answer:

   Receive up to one message from the queue -> Option D

4. Quick Check:

   receive-message = get messages [OK]

Hint: receive-message gets messages, send-message puts them [OK]

Common Mistakes:

• Thinking receive-message sends messages
• Confusing receive with delete
• Assuming it creates queues

4. You wrote this code snippet to receive messages from an AWS SQS queue but it returns no messages:

response = sqs.receive_message(QueueUrl=queue_url, MaxNumberOfMessages=5)
messages = response['Messages']
for msg in messages:
    print(msg['Body'])

What is the likely cause of the error?

medium

A. The response has no 'Messages' key if the queue is empty

B. MaxNumberOfMessages must be 1, not 5

C. The queue URL is incorrect or empty

D. You must delete messages before receiving

Solution

1. Step 1: Understand SQS receive_message response

   If the queue is empty, the response does not include the 'Messages' key, causing a KeyError when accessing it.

2. Step 2: Identify the error cause

   Not checking if 'Messages' exists before looping causes failure when no messages are returned.

3. Final Answer:

   The response has no 'Messages' key if the queue is empty -> Option A

4. Quick Check:

   Empty queue means no 'Messages' key [OK]

Hint: Check if 'Messages' key exists before using it [OK]

Common Mistakes:

• Assuming 'Messages' always exists
• Setting MaxNumberOfMessages incorrectly
• Thinking messages must be deleted before receiving

5. You want to build a system that sends messages to an AWS SQS queue and ensures each message is processed exactly once by a receiver. Which combination of features should you use?

hard

A. Standard queue with short polling and no message deletion

B. Standard queue with long polling and message deletion after processing

C. FIFO queue with deduplication and message deletion after processing

D. FIFO queue without deduplication and no message deletion

Solution

1. Step 1: Understand message processing guarantees

   Standard queues can deliver messages more than once; FIFO queues preserve order and support exactly-once processing with deduplication.

2. Step 2: Ensure messages are deleted after processing

   Deleting messages after processing prevents reprocessing the same message.

3. Step 3: Combine features for exactly-once processing

   Use FIFO queue with deduplication and delete messages after processing to guarantee exactly-once delivery.

4. Final Answer:

   FIFO queue with deduplication and message deletion after processing -> Option C

5. Quick Check:

   Exactly-once = FIFO + deduplication + delete [OK]

Hint: Use FIFO queue with deduplication and delete messages after processing [OK]

Common Mistakes:

• Using standard queue for exactly-once needs
• Not deleting messages after processing
• Ignoring deduplication feature