- A
Amazon Simple Queue Service (SQS)
Why wrong: Amazon SQS is a message queuing service that enables decoupled communication between application components, but it is designed for point-to-point messaging. While you can configure SQS queues as subscribers to an SNS topic to achieve fan-out, SQS alone does not support sending a single message to multiple subscribers simultaneously.
- B
Amazon Simple Notification Service (SNS)
Amazon SNS is a fully managed pub/sub messaging service that supports the fan-out pattern. It can send a single message to multiple subscribers, including other AWS services like Lambda, SQS, and HTTP/S endpoints, making it the ideal choice for this requirement.
- C
Amazon Kinesis Data Streams
Why wrong: Amazon Kinesis Data Streams is designed for real-time streaming of large-scale data, such as log data or clickstreams. It can support multiple consumers through enhanced fan-out, but it is overkill for a simple notification scenario and adds unnecessary complexity and cost.
- D
AWS Step Functions
Why wrong: AWS Step Functions is a serverless orchestration service that lets you coordinate multiple AWS services into a workflow. It is not a messaging service and does not provide the pub/sub capability needed to distribute a single message to multiple subscribers.
Quick Answer
The answer is Amazon Simple Notification Service (SNS). SNS is the correct choice because it is a fully managed pub/sub messaging service that natively supports the fan-out pattern, allowing a single message published to a topic to be delivered simultaneously to multiple subscribers such as SQS queues, Lambda functions, and HTTP endpoints. This meets the requirement for durable, scalable, asynchronous communication between the order, inventory, shipping, and analytics services, as SNS persists messages across Availability Zones and automatically scales to handle high throughput. On the AWS Certified Cloud Practitioner CLF-C02 exam, this question tests your understanding of AWS messaging services and the distinction between SNS (pub/sub fan-out) and SQS (point-to-point queues). A common trap is confusing SNS with SQS, but remember that SNS pushes messages to multiple subscribers, while SQS is for decoupled, pull-based processing. For a quick memory tip: think of SNS as a "loudspeaker" that broadcasts to everyone listening, while SQS is a "mailbox" for one recipient.
CLF-C02 Cloud Technology and Services Practice Question
This CLF-C02 practice question tests your understanding of cloud technology and services. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company is building a microservices application on AWS. The application consists of multiple independent services that need to communicate asynchronously. When an order is placed, the order service must send a notification to the inventory service, the shipping service, and the analytics service simultaneously. The company wants a fully managed, durable, and scalable messaging service that supports a fan-out pattern where a single message can be delivered to multiple subscribers. Which AWS service should the company use to meet these requirements?
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 Notification Service (SNS)
Amazon Simple Notification Service (SNS) is a fully managed pub/sub messaging service that supports fan-out, where a single message published to a topic is delivered to multiple subscribers (e.g., SQS queues, Lambda functions, HTTP endpoints) simultaneously. It is durable (persists messages across AZs) and scales automatically to handle high throughput, making it ideal for the asynchronous notification requirements of the order, inventory, shipping, and analytics services.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 it's wrong here
Amazon SQS is a message queuing service that enables decoupled communication between application components, but it is designed for point-to-point messaging. While you can configure SQS queues as subscribers to an SNS topic to achieve fan-out, SQS alone does not support sending a single message to multiple subscribers simultaneously.
- ✓
Amazon Simple Notification Service (SNS)
Why this is correct
Amazon SNS is a fully managed pub/sub messaging service that supports the fan-out pattern. It can send a single message to multiple subscribers, including other AWS services like Lambda, SQS, and HTTP/S endpoints, making it the ideal choice for this requirement.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Amazon Kinesis Data Streams
Why it's wrong here
Amazon Kinesis Data Streams is designed for real-time streaming of large-scale data, such as log data or clickstreams. It can support multiple consumers through enhanced fan-out, but it is overkill for a simple notification scenario and adds unnecessary complexity and cost.
- ✗
AWS Step Functions
Why it's wrong here
AWS Step Functions is a serverless orchestration service that lets you coordinate multiple AWS services into a workflow. It is not a messaging service and does not provide the pub/sub capability needed to distribute a single message to multiple subscribers.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse SQS (point-to-point queuing) with SNS (pub/sub fan-out), mistakenly thinking SQS can deliver to multiple consumers by using multiple queues, but SNS is the correct service for simultaneous, multi-subscriber delivery without polling.
Trap categories for this question
Scenario analysis trap
Amazon Kinesis Data Streams is designed for real-time streaming of large-scale data, such as log data or clickstreams. It can support multiple consumers through enhanced fan-out, but it is overkill for a simple notification scenario and adds unnecessary complexity and cost.
Detailed technical explanation
How to think about this question
Under the hood, SNS uses a topic-based pub/sub model where each message is replicated and pushed to all subscribed endpoints (e.g., SQS queues, Lambda, HTTP/S) in parallel, with built-in retry logic and dead-letter queues for durability. A subtle behavior is that SNS does not guarantee message ordering across subscribers, which is acceptable for this use case because each service processes notifications independently. In a real-world scenario, the order service would publish a single JSON message to an SNS topic, and the inventory, shipping, and analytics services would each subscribe via their own SQS queue to decouple processing and handle failures independently.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Cloud Technology and Services — study guide chapter
Learn the concepts, then practise the questions
- →
Cloud Technology and Services practice questions
Targeted practice on this topic area only
- →
All CLF-C02 questions
1,024 questions across all exam domains
- →
AWS Certified Cloud Practitioner CLF-C02 study guide
Full concept coverage aligned to exam objectives
- →
CLF-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CLF-C02 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Cloud Concepts practice questions
Practise CLF-C02 questions linked to Cloud Concepts.
Security and Compliance practice questions
Practise CLF-C02 questions linked to Security and Compliance.
Cloud Technology and Services practice questions
Practise CLF-C02 questions linked to Cloud Technology and Services.
Billing, Pricing, and Support practice questions
Practise CLF-C02 questions linked to Billing, Pricing, and Support.
AWS shared responsibility model practice questions
Practise CLF-C02 questions linked to AWS shared responsibility model.
AWS IAM practice questions
Practise CLF-C02 questions linked to AWS IAM.
AWS pricing practice questions
Practise CLF-C02 questions linked to AWS pricing.
AWS support plans practice questions
Practise CLF-C02 questions linked to AWS support plans.
AWS S3 practice questions
Practise CLF-C02 questions linked to AWS S3.
AWS EC2 practice questions
Practise CLF-C02 questions linked to AWS EC2.
Practice this exam
Start a free CLF-C02 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this CLF-C02 question test?
Cloud Technology and Services — This question tests Cloud Technology and Services — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Amazon Simple Notification Service (SNS) — Amazon Simple Notification Service (SNS) is a fully managed pub/sub messaging service that supports fan-out, where a single message published to a topic is delivered to multiple subscribers (e.g., SQS queues, Lambda functions, HTTP endpoints) simultaneously. It is durable (persists messages across AZs) and scales automatically to handle high throughput, making it ideal for the asynchronous notification requirements of the order, inventory, shipping, and analytics services.
What should I do if I get this CLF-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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.