AWS Certified Solutions Architect Decoupling with SQS and SNS 3

Question 1

A team wants to replay all past SNS notifications to a newly added SQS subscriber. Which statement is correct about SNS replay capability?

Accepted Answer

SNS does not support replay; messages must be sourced from an archive such as Kinesis or S3

Answer

SNS is a push-based, stateless service with no message replay capability; to replay events, store them in S3, Kinesis, or another durable store.

Question 2

An application publishes 5,000 messages per second to an SNS topic. Which SNS topic type supports this throughput while preserving strict message ordering?

Accepted Answer

FIFO SNS topic

Answer

FIFO SNS topics preserve strict ordering and exactly-once delivery but are limited to 300 publishes/second (or 30,000 with batching), so 5,000/s requires batching or architectural consideration.

Question 3

A Lambda function is subscribed to an SQS queue. The function fails processing a batch. What determines which messages are retried?

Accepted Answer

Only messages explicitly returned in the batchItemFailures response are retried

Answer

When reportBatchItemFailures is enabled, Lambda retries only the message IDs listed in the batchItemFailures response, leaving successfully processed messages deleted.

Question 4

What is the maximum retention period for messages stored in an Amazon SQS queue?

Accepted Answer

14 days

Answer

SQS can retain messages for a configurable period between 1 minute and 14 days; the default is 4 days.

Question 5

A company needs to send a single notification that triggers email delivery AND writes to an SQS queue simultaneously. Which AWS service pattern accomplishes this?

Accepted Answer

SNS topic with email and SQS subscriptions (fan-out)

Answer

The SNS fan-out pattern allows a single publish to simultaneously deliver to multiple endpoints including email subscribers and SQS queues.

AWS Practice Test

AWS Practice Test

AWS Certified Solutions Architect Decoupling with SQS and SNS 3