CLF-C02 - Cloud Technology and Services (34% of the exam) - Section 3.11
Identify services from other in-scope AWS categories, including application integration with Amazon EventBridge, Amazon SNS and Amazon SQS, plus developer tools, end-user computing and IoT services.
Identify application integration services and their roles: Amazon EventBridge for event-driven routing between services, Amazon SNS for pub/sub notification delivery to multiple subscribers, and Amazon SQS for decoupled message queuing between components. Recognise that AWS also offers developer tools, end-user computing services, and IoT services as in-scope categories at the practitioner level.
lock_openFree sampleCloud Technology and Servicesmedium
A team is comparing Amazon SNS and Amazon SQS for moving messages between components. They need a clear understanding of how the two services differ in how messages reach the receivers. Which statement correctly describes the difference between Amazon SNS and Amazon SQS?
AAmazon SNS lets receivers store messages in a queue, while Amazon SQS pushes the same message out to many subscribers at once.
BAmazon SNS and Amazon SQS both push every message to all receivers, so the only real difference between them is the maximum size of each message.
CAmazon SNS pushes each message to all subscribers immediately, while Amazon SQS holds messages in a queue for consumers to pull when ready.check_circle Correct
DAmazon SNS and Amazon SQS both queue messages for later pull, so the difference is simply that SNS keeps messages for a longer retention period.
Amazon SNS pushes messages to subscribers in a publish and subscribe model, while Amazon SQS queues messages for consumers to pull. SNS delivers a published message to every subscribed endpoint as soon as it arrives using a push model, while SQS stores messages in a queue until a consumer chooses to retrieve them, which is a pull model.
Why A is wrong: This reverses the two services; queuing for later pull is SQS, and pushing one message to many subscribers is SNS, so the description is back to front.
Why B is wrong: SQS does not push to receivers; consumers pull from the queue, and message size is not the defining difference between the two services.
Why C is correct: SNS uses a publish and subscribe push model that fans a message out to subscribers, whereas SQS is a pull-based queue where consumers retrieve messages on their own schedule.
Why D is wrong: SNS is not a queue and does not hold messages for later pull; it pushes to subscribers, so retention period is not what separates the two services.
Answers that look right on this material and are not. Each one is a distractor from a different question in the CLF-C02 bank for this domain.
AWS Lambda, the service that runs short pieces of function code in response to events without any long-running container cluster.
errorWhy it is wrong: Lambda is event-driven function compute and tempting as serverless, but it is not a container orchestration service for clusters.
The AWS Management Console, a browser based interface where a person uploads and reads objects by clicking through pages rather than from code
errorWhy it is wrong: The console is operated by a human in a browser, so it cannot be called from inside a running Python program the way the developer requires.
Amazon EventBridge, an event bus that routes events from many sources to targets using rules that match on the event content
errorWhy it is wrong: EventBridge routes matching events to targets, but it is not the simple point-to-point queue the worker tier needs to pull and process orders one at a time.