SQS queue concept in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding SQS Message Visibility Timeout

What happens to a message in an AWS SQS queue when a consumer receives it but does not delete it before the visibility timeout expires?

A The message becomes visible again in the queue and can be received by other consumers.

B The message is permanently deleted from the queue automatically.

C The message is moved to a dead-letter queue immediately.

D The message is duplicated and sent to all consumers.

💡 Hint

Think about what visibility timeout means for message processing.

When a message is received, it becomes invisible for a set time (visibility timeout). If the consumer does not delete it in that time, the message becomes visible again for other consumers to process.

❓ service_behavior

intermediate

SQS Message Retention Period Behavior

If an SQS message is not deleted, how long will it remain in the queue before it is automatically removed?

A Messages are retained for a default of 4 days, configurable up to 14 days.

B Messages remain indefinitely until deleted manually.

C Messages are deleted after 1 hour automatically.

D Messages are deleted immediately after being received.

💡 Hint

Check the default and maximum retention period for SQS messages.

SQS messages have a retention period that defaults to 4 days but can be configured up to 14 days. After this period, messages are deleted automatically.

❓ Architecture

advanced

Designing for High Throughput with SQS

You need to design an architecture using SQS to handle a very high volume of messages with minimal delay. Which approach best supports this requirement?

A Use a single standard queue with a single consumer to avoid message duplication.

B Use a single standard SQS queue with multiple consumers processing messages in parallel.

C Use multiple FIFO queues with one consumer each to distribute load.

D Use a single FIFO SQS queue with one consumer to maintain order.

💡 Hint

Consider the difference between standard and FIFO queues and how parallelism affects throughput.

Standard queues support nearly unlimited throughput and allow multiple consumers to process messages in parallel, which reduces delay. FIFO queues guarantee order but have lower throughput limits.

❓ security

advanced

Securing Access to an SQS Queue

Which method is the most secure way to restrict access to an SQS queue so that only a specific AWS Lambda function can send and receive messages?

A Use a queue policy that allows access from any AWS service.

B Make the queue public and rely on Lambda's internal security.

C Attach an IAM policy to the Lambda function role allowing only that function to access the queue.

D Use a security group to restrict network access to the queue.

💡 Hint

Think about how AWS controls permissions for services and resources.

IAM policies attached to the Lambda function's execution role can restrict which resources the function can access. Queue policies can also restrict access, but attaching a precise IAM policy to the Lambda role is the most secure and direct method.

✅ Best Practice

expert

Handling Poison Messages in SQS

You have an SQS queue processing messages, but some messages cause processing failures repeatedly. What is the best practice to handle these 'poison messages' to avoid blocking the queue?

A Increase the visibility timeout indefinitely for all messages.

B Manually monitor and delete failed messages from the main queue.

C Delete messages immediately after receiving them, regardless of processing success.

D Configure a dead-letter queue (DLQ) and set a maximum receive count to move failing messages to the DLQ.

💡 Hint

Consider how SQS supports handling messages that fail processing multiple times.

Dead-letter queues allow you to isolate messages that fail processing repeatedly by moving them after a set number of receives. This prevents them from blocking the main queue and allows separate analysis or reprocessing.