Question 713 of 988
CLF-C02 Cloud Technology and Services Practice Question
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?
⚠ Common exam trap
Candidates often confuse SNS with SQS because both are messaging services, but SNS is a push-based pub/sub system that does not durably store messages, whereas SQS is a pull-based queue that provides persistent storage and decoupling, which is exactly what the scenario requires.
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 (Amazon SQS)
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.
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 Notification Service (Amazon SNS)
Why it's wrong here
Amazon SNS is a pub/sub messaging service; it pushes messages to subscribers but does not store messages persistently in a queue. If a subscriber is unavailable, messages may be lost. It is not suitable for reliable message storage until processing.
When this WOULD be correct
A company needs to send order notifications to multiple subscribers (e.g., email, SMS, and a processing system) simultaneously, and message durability is not the primary concern because the processing system is always available or uses a separate queue.
- ✓
Amazon Simple Queue Service (Amazon SQS)
Why this is correct
Amazon Simple Queue Service (SQS) is a fully managed message queuing service that decouples the frontend from the order-processing backend. It durably stores messages across multiple Availability Zones, buffers spikes in order volume, and lets producers and consumers scale independently. With features like visibility timeouts and dead-letter queues, SQS ensures every order message is retained and processed reliably, exactly matching the requirement for a durable buffer between tiers.
- ✗
Amazon Kinesis Data Streams
Why it's wrong here
Amazon Kinesis Data Streams is designed for real-time data streaming and processing, not for reliable message queuing between decoupled application tiers. While it can handle high throughput and scale, its primary purpose is continuous data ingestion and analysis, not acting as a buffer for individual order requests waiting for backend processing. It would be a suitable choice if the requirement was to ingest and analyse a continuous flow of order data, rather than store discrete order messages reliably.
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., for fraud detection, user behavior analytics), and retain the data for up to 7 days. Kinesis Data Streams would be the correct choice for this streaming data pipeline.
- ✗
AWS Step Functions
Why it's wrong here
AWS Step Functions is a serverless orchestration service that coordinates multiple AWS services into state-machine workflows, managing transitions and retries. Unlike a queue, it does not provide a durable buffer for decoupled components: messages are not stored persistently for later consumption, and the service is designed to coordinate workflow states rather than accept and hold discrete order messages. It could be used to orchestrate the order pipeline, but it would not satisfy the buffering and decoupling requirement that SQS provides.
When this WOULD be correct
A company needs to coordinate a multi-step order processing workflow that involves invoking multiple AWS services (e.g., Lambda, DynamoDB, SNS) in a specific sequence, with error handling and retries. Step Functions would be correct to manage the workflow logic and state transitions.
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 (Amazon SQS)Correct answer▾
Why this is correct
Amazon Simple Queue Service (SQS) is a fully managed message queuing service that decouples the frontend from the order-processing backend. It durably stores messages across multiple Availability Zones, buffers spikes in order volume, and lets producers and consumers scale independently. With features like visibility timeouts and dead-letter queues, SQS ensures every order message is retained and processed reliably, exactly matching the requirement for a durable buffer between tiers.
✗Amazon Simple Notification Service (Amazon 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, but it does not store messages durably or allow backend polling; if the backend is unavailable, messages are lost unless configured with a dead-letter queue, which is not the primary use case.
★ When this WOULD be the correct answer
A company needs to send order notifications to multiple subscribers (e.g., email, SMS, and a processing system) simultaneously, and message durability is not the primary concern because the processing system is always available or uses a separate queue.
Why candidates choose this
Candidates may confuse SNS with SQS because both are messaging services, and they might think SNS can store messages for later processing, not realizing SNS is push-based and lacks built-in message persistence.
✗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 volumes of data for processing by multiple consumers, not for simple decoupling and reliable message storage with independent scaling of a single backend. It does not inherently guarantee exactly-once message processing or simple queue semantics needed for order processing.
★ 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., for fraud detection, user behavior analytics), and retain the data for up to 7 days. Kinesis Data Streams would be the correct choice for this streaming data pipeline.
Why candidates choose this
Candidates may confuse Kinesis Data Streams with a message queue because both can handle data between producers and consumers, but Kinesis is optimized for real-time streaming analytics, not for reliable, decoupled message queuing with independent scaling.
✗AWS Step FunctionsWrong answer — click to see why▾
Why this is wrong here
AWS Step Functions is a serverless orchestration service for coordinating multiple AWS services into workflows, not a message queue. It does not provide a durable buffer for storing order requests until the backend is ready to process them, nor does it handle traffic spikes by decoupling frontend and backend tiers.
★ When this WOULD be the correct answer
A company needs to coordinate a multi-step order processing workflow that involves invoking multiple AWS services (e.g., Lambda, DynamoDB, SNS) in a specific sequence, with error handling and retries. Step Functions would be correct to manage the workflow logic and state transitions.
Why candidates choose this
Candidates may confuse Step Functions with a queuing service because it can manage asynchronous tasks and retries, leading them to think it can decouple application tiers. However, it lacks the message buffering and independent scaling capabilities of 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?”
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
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 →
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.