Certified Solutions Architect Decoupling with SQS and SNS Flashcards
7 cards from real AWS practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Certified Solutions Architect Decoupling with SQS and SNS flashcards as text
A team wants to replay all past SNS notifications to a newly added SQS subscriber. Which statement is correct about SNS replay capability?
Answer: SNS does not support replay; messages must be sourced from an archive such as Kinesis or S3
SNS is a push-based, stateless service with no message replay capability; to replay events, store them in S3, Kinesis, or another durable store.
An application publishes 5,000 messages per second to an SNS topic. Which SNS topic type supports this throughput while preserving strict message ordering?
Answer: FIFO SNS topic
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.
A Lambda function is subscribed to an SQS queue. The function fails processing a batch. What determines which messages are retried?
Answer: Only messages explicitly returned in the batchItemFailures response are retried
When reportBatchItemFailures is enabled, Lambda retries only the message IDs listed in the batchItemFailures response, leaving successfully processed messages deleted.
What is the maximum retention period for messages stored in an Amazon SQS queue?
Answer: 14 days
SQS can retain messages for a configurable period between 1 minute and 14 days; the default is 4 days.
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?
Answer: SNS topic with email and SQS subscriptions (fan-out)
The SNS fan-out pattern allows a single publish to simultaneously deliver to multiple endpoints including email subscribers and SQS queues.
Which SQS attribute controls how many times a message can be received before being sent to the dead-letter queue?
Answer: MaxReceiveCount in the RedrivePolicy
The RedrivePolicy's maxReceiveCount defines how many delivery attempts SQS allows before moving the message to the configured dead-letter queue.
An architect is designing a system where an SQS queue must receive messages from SNS topics in a different AWS account. What is required?
Answer: An SQS resource-based policy granting the cross-account SNS topic permission to SendMessage
The SQS queue needs a resource policy explicitly granting the cross-account SNS topic's ARN permission to call sqs:SendMessage.