Question 982 of 988
CLF-C02 Cloud Technology and Services Practice Question
A company is refactoring its monolithic e-commerce application into multiple microservices. The order-processing service must send messages to the inventory service to reserve stock. The company needs a fully managed service that can durably store these messages, handle high throughput, and allow the inventory service to poll for messages at its own pace. The company wants to avoid any message loss. Which AWS service should the company use?
⚠ Common exam trap
The trap here is that candidates might choose Amazon SNS because they confuse push-based notifications with durable message queuing, overlooking that SNS does not store messages or allow polling, which is essential for decoupled, loss-free communication.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Amazon Simple Queue Service (SQS)
Amazon SQS is the correct choice because it is a fully managed message queuing service that durably stores messages across multiple Availability Zones, ensuring no message loss. It supports high throughput and allows the inventory service to poll for messages at its own pace using long or short polling, decoupling the order-processing and inventory services.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Amazon Simple Queue Service (SQS)
Why this is correct
Correct. Amazon SQS is a fully managed message queue service designed for decoupling application components. It stores messages durably, supports high throughput, and allows consumers to poll for messages, ensuring no message loss. This fits the requirement perfectly.
- ✗
Amazon Simple Notification Service (SNS)
Why it's wrong here
Amazon SNS is a pub/sub notification service that pushes messages to subscribers, not a queue-based system that allows the inventory service to poll for messages at its own pace. The requirement for durable storage and poll-based consumption demands a message queue, which SNS does not provide. It is tempting because SNS can handle high throughput and is fully managed, making it a correct choice for fan-out notifications to multiple endpoints, but it lacks the message retention and pull mechanism needed here.
When this WOULD be correct
A company needs to send order confirmation emails and SMS alerts to customers when an order is placed. The system must fan out a single message to multiple subscribers (email, SMS, mobile push) simultaneously. Amazon SNS would be the correct choice for this pub/sub notification pattern.
- ✗
Amazon Kinesis Data Streams
Why it's wrong here
Amazon Kinesis Data Streams is unsuitable because it functions as a real-time data stream, not a message queue. While it offers high throughput and durable storage for a retention period, messages are not removed upon consumption by a single service. This means the inventory service would need to manage its own progress, and messages could expire from the stream before processing, risking loss. It is tempting due to its managed nature and high throughput capabilities, but Kinesis is designed for scenarios where multiple consumers process the *same* stream of data, such as real-time analytics or log aggregation, rather than single-consumer message delivery.
When this WOULD be correct
A company needs to ingest and process real-time clickstream data from a website, analyze it with multiple consumer applications (e.g., real-time dashboards, anomaly detection), and retain the data for up to 7 days for replay. Kinesis Data Streams would be the correct choice for this high-throughput, ordered stream processing scenario.
- ✗
Amazon MQ
Why it's wrong here
Amazon MQ is a managed message broker for protocols like AMQP and MQTT, but it lacks the native pull-based polling model required here; the inventory service would need to maintain persistent connections to consume messages, which conflicts with the requirement to poll at its own pace. It is tempting because it offers durable message storage and high throughput for traditional enterprise messaging, making it a correct choice if the inventory service used a standard JMS or AMQP client expecting broker-pushed delivery rather than independent polling.
When this WOULD be correct
A company needs to migrate an existing on-premises application that uses JMS-compatible message brokers (e.g., ActiveMQ or RabbitMQ) to AWS without rewriting the application code. Amazon MQ would be the correct choice because it provides a managed broker that supports standard messaging protocols and JMS APIs.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The CLF-C02 exam frequently reuses these exact scenarios with slightly different constraints.
✓Amazon Simple Queue Service (SQS)Correct answer▾
Why this is correct
Correct. Amazon SQS is a fully managed message queue service designed for decoupling application components. It stores messages durably, supports high throughput, and allows consumers to poll for messages, ensuring no message loss. This fits the requirement perfectly.
✗Amazon Simple Notification Service (SNS)Wrong answer — click to see why▾
Why this is wrong here
SNS is a pub/sub messaging service that pushes messages to subscribers; it does not support polling by consumers. The inventory service needs to poll for messages at its own pace, which SQS provides via long polling. SNS also does not durably store messages for individual consumer retrieval.
★ When this WOULD be the correct answer
A company needs to send order confirmation emails and SMS alerts to customers when an order is placed. The system must fan out a single message to multiple subscribers (email, SMS, mobile push) simultaneously. Amazon SNS would be the correct choice for this pub/sub notification pattern.
Why candidates choose this
Candidates may confuse SNS with SQS because both are messaging services. They might think SNS can store messages for consumers to poll, but SNS is push-based and does not provide message durability for individual consumers.
✗Amazon Kinesis Data StreamsWrong answer — click to see why▾
Why this is wrong here
Amazon Kinesis Data Streams is designed for real-time streaming of large data volumes, not for decoupled message queuing with individual message polling. It requires consumers to process records in order within shards, and does not support independent polling at the consumer's own pace without managing shard iterators.
★ When this WOULD be the correct answer
A company needs to ingest and process real-time clickstream data from a website, analyze it with multiple consumer applications (e.g., real-time dashboards, anomaly detection), and retain the data for up to 7 days for replay. Kinesis Data Streams would be the correct choice for this high-throughput, ordered stream processing scenario.
Why candidates choose this
Candidates may confuse high-throughput message streaming with durable message queuing, or think Kinesis is a general-purpose messaging service. The mention of 'high throughput' and 'durably store' can mislead them into selecting Kinesis over SQS.
✗Amazon MQWrong answer — click to see why▾
Why this is wrong here
Amazon MQ is a managed message broker for ActiveMQ or RabbitMQ, not a fully managed service that durably stores messages with high throughput and polling at the consumer's pace. It requires managing brokers and is not serverless, and it does not guarantee the same level of durability and scalability as SQS for this use case.
★ When this WOULD be the correct answer
A company needs to migrate an existing on-premises application that uses JMS-compatible message brokers (e.g., ActiveMQ or RabbitMQ) to AWS without rewriting the application code. Amazon MQ would be the correct choice because it provides a managed broker that supports standard messaging protocols and JMS APIs.
Why candidates choose this
Candidates may confuse Amazon MQ with a fully managed messaging service, but it is actually a managed broker service that still requires provisioning and scaling of broker instances, unlike the serverless SQS.
Analysis generated from the official CLF-C02blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on CLF-C02
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company runs a web application that processes customer orders. During flash sales, the application's backend servers become overwhelmed because orders are submitted faster than they can be processed. The company needs a fully managed, highly available service that can buffer incoming orders so that the backend can process them at its own pace without losing any data. The service must automatically scale to handle any volume of orders without requiring manual provisioning. Which AWS service meets these requirements?
medium- A.Amazon Simple Notification Service (Amazon SNS)
- ✓ B.Amazon Simple Queue Service (Amazon SQS)
- C.Amazon Kinesis Data Streams
- D.Amazon MQ
Why B: Amazon Simple Queue Service (SQS) is a fully managed, highly available message queuing service that decouples application components. It buffers incoming orders by storing them in a queue, allowing the backend to process messages at its own pace without losing data. SQS automatically scales to handle any volume of messages, eliminating the need for manual provisioning.
Variation 2. A company has a web application that processes customer orders. The frontend web servers run on Amazon EC2 instances and receive order requests from users. The backend order processing system runs on a separate fleet of EC2 instances. The company wants to decouple these two tiers so that order requests are stored reliably until the backend is ready to process them. The solution must handle occasional traffic spikes without losing any messages and must allow the backend to scale independently. Which AWS service should the company use to meet these requirements?
medium- A.Amazon Simple Notification Service (Amazon SNS)
- ✓ B.Amazon Simple Queue Service (Amazon SQS)
- C.Amazon Kinesis Data Streams
- D.AWS Step Functions
Why B: Amazon Simple Queue Service (SQS) is the correct choice because it provides a fully managed message queuing service that enables you to decouple and scale microservices, distributed systems, and serverless applications. SQS reliably stores messages in a queue until the backend order processing system retrieves and processes them, ensuring no messages are lost even during traffic spikes. The backend can independently scale based on the queue depth, and SQS offers at-least-once delivery and exactly-once processing with FIFO queues if needed.
Last reviewed: Jun 11, 2026
This CLF-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CLF-C02 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.