Back to AWS SNS

Message Delivery Status

5 minutes 5 Questions

Message Delivery Status is a feature that allows you to monitor and troubleshoot delivery issues. This can be useful to verify the delivery of messages to specific endpoints and to help diagnose issues related to message deliveries. With this feature enabled, SNS will write logs to Amazon CloudWatc…

Test mode:
Start practice test
AWS Certified Solutions Architect - Message Delivery Status Example Questions

Test your knowledge of Message Delivery Status

Question 1

An Amazon SNS topic has an HTTPS subscription to your application's endpoint. CloudWatch delivery status shows multiple delivery attempts failing with '500 Internal Server Error' returned by the subscribed endpoint. What should you do to resolve the delivery failures?

Correct Answer: Fix the HTTP/HTTPS subscription endpoint so it successfully processes the request and returns a 2xx response to SNS; SNS will automatically retry 5xx errors.

A 500 Internal Server Error in SNS delivery logs for an HTTP/HTTPS subscription indicates the subscriber's web endpoint failed to handle the request. SNS treats deliveries as successful only when the endpoint returns a 2xx status within the timeout. To resolve the issue, diagnose and correct the subscriber endpoint (application code, configuration, and capacity) so it can parse the SNS message and respond with 2xx. SNS automatically retries 5xx responses with exponential backoff, so recreating the topic, changing the message format arbitrarily, or checking general internet connectivity will not fix an application-side 500 error.

Question 2

A solution architect needs to monitor the delivery status of messages from an SNS Topic to SQS subscribers. What should be done to monitor the message delivery status?

Correct Answer: Enable CloudWatch Metrics for SNS

CloudWatch Metrics for SNS can be used to monitor the delivery status of messages sent to subscribers. Other options either don't provide the required data or introduce unnecessary complications.

Question 3

An application is sending messages to an SQS queue, but some messages are being marked as 'Message too large'. What should be done to handle this issue?

Correct Answer: Configure Amazon S3 to store large message payloads

The SQS message size limit cannot be increased. Storing message payloads on Amazon S3 avoids this limitation, as only metadata is sent in the SQS message while the payload is stored in S3. Other options either don't solve the problem or introduce unrelated changes.

More Message Delivery Status questions
15 questions (total)
Start 15 question test