CLF-C02 Cloud Technology and Services Practice Question
A company runs a microservices-based e-commerce application on AWS. During peak hours, the order processing service often gets overwhelmed because the web frontend sends requests directly to it. This causes delays and occasional failures. The architecture team needs to decouple the frontend from the order processing service by introducing a fully managed, highly available, and durable message queue. The queue must automatically replicate messages across multiple Availability Zones and allow the order processing service to pull messages at its own pace. Which AWS service should the company use?
⚠ Common exam trap
Candidates often confuse SNS (push-based) with SQS (pull-based) because both are messaging services, but the requirement for the consumer to pull messages at its own pace eliminates SNS, which pushes messages immediately to subscribers.
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 Simple Queue Service (SQS) is the correct choice because it is a fully managed, highly available, and durable message queue service that automatically replicates messages across multiple Availability Zones (AZs) to ensure fault tolerance. It decouples the web frontend from the order processing service, allowing the latter to poll and process messages at its own pace, which prevents overload during peak hours. SQS provides at-least-once delivery and supports standard queues with high throughput, making it ideal for this use case.
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 queuing service that decouples application components. It is highly available and durable, automatically replicating messages across multiple Availability Zones. It supports polling mechanisms, allowing the order processing service to consume messages at its own pace.
- ✗
Amazon Simple Notification Service (SNS)
Why it's wrong here
Incorrect. Amazon SNS is a pub/sub messaging service for sending notifications to multiple subscribers (e.g., email, Lambda, HTTP endpoints). It is not a queue; messages are pushed to subscribers immediately and not stored for polling. This does not provide the buffering and polling capability needed to decouple and protect the order processing service.
When this WOULD be correct
A company needs to send order confirmation emails and SMS notifications to customers when an order is placed. The system requires a fully managed service that can fan out messages to multiple subscribers (e.g., email, SMS, and a downstream processing service) simultaneously.
- ✗
Amazon Kinesis Data Streams
Why it's wrong here
Kinesis Data Streams is designed for real-time streaming of large volumes of data for ingestion and processing, not for decoupling a request-response workload with a durable, pull-based message queue. The requirement for automatic replication across multiple Availability Zones and the ability for the order processing service to pull messages at its own pace is met by Amazon Simple Queue Service (SQS), which provides exactly that durable, at-least-once delivery model. Kinesis Data Streams would be tempting because it offers high throughput and persistence, but its records have a 365-day retention limit and are consumed via shard-level iterators, not a simple queue-based pull, making it unsuitable for decoupling a single microservice from its frontend.
When this WOULD be correct
A company needs to ingest and process real-time clickstream data from a website for analytics, requiring the ability to replay data and process it with multiple consumers in near real-time. Kinesis Data Streams would be the correct choice for this streaming data use case.
- ✗
Amazon MQ
Why it's wrong here
Amazon MQ is a managed service for open-source message brokers like ActiveMQ and RabbitMQ, making it a tempting choice for message queuing. However, it is primarily designed for migrating existing applications that require compatibility with these specific protocols, rather than for new cloud-native development. For this scenario, which seeks a fully managed, serverless queue that automatically scales without requiring broker instance provisioning or management, Amazon MQ is unsuitable as it still necessitates choosing and managing broker types and sizes.
When this WOULD be correct
A company needs to migrate an existing on-premises application that uses JMS-compatible message brokers (like 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 JMS and existing protocols.
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 queuing service that decouples application components. It is highly available and durable, automatically replicating messages across multiple Availability Zones. It supports polling mechanisms, allowing the order processing service to consume messages at its own pace.
✗Amazon Simple Notification Service (SNS)Wrong answer — click to see why▾
Why this is wrong here
Amazon SNS is a pub/sub messaging service that pushes messages to subscribers, not a queue that allows the order processing service to pull messages at its own pace. It does not provide durable message storage or automatic replication across multiple AZs for message persistence.
★ When this WOULD be the correct answer
A company needs to send order confirmation emails and SMS notifications to customers when an order is placed. The system requires a fully managed service that can fan out messages to multiple subscribers (e.g., email, SMS, and a downstream processing service) simultaneously.
Why candidates choose this
Candidates may confuse SNS with SQS because both are messaging services, or they might think that SNS can also decouple components, but they overlook the requirement for a queue with pull-based consumption and durable storage.
✗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 decoupling microservices with a simple message queue. It lacks the automatic replication across multiple AZs and the pull-based consumption model that SQS provides for decoupling.
★ When this WOULD be the correct answer
A company needs to ingest and process real-time clickstream data from a website for analytics, requiring the ability to replay data and process it with multiple consumers in near real-time. Kinesis Data Streams would be the correct choice for this streaming data use case.
Why candidates choose this
Candidates may confuse Kinesis as a message queue because it can buffer and deliver messages, but its focus on real-time streaming and data retention makes it seem like a durable queue, leading to incorrect selection.
✗Amazon MQWrong answer — click to see why▾
Why this is wrong here
Amazon MQ is a managed message broker service for Apache ActiveMQ and RabbitMQ, but it does not automatically replicate messages across multiple Availability Zones by default; it requires a multi-AZ deployment configuration. Additionally, it is not as fully managed and durable as SQS for simple queueing needs.
★ When this WOULD be the correct answer
A company needs to migrate an existing on-premises application that uses JMS-compatible message brokers (like 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 JMS and existing protocols.
Why candidates choose this
Candidates may confuse Amazon MQ with a fully managed queue service, not realizing that SQS is simpler and more suitable for decoupling microservices with automatic multi-AZ replication and durability.
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?”
Go deeper
Related to this question
About these practice questions
This CLF-C02 question is part of Courseiva's 988-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.