AWS Solutions Architect Associate SAA-C03 Sign in Try 10 free questions

Free SAA-C03 practice: SQS vs SNS vs EventBridge

Three messaging services, three jobs — queue for one, notify many, or route events by rule. Six comparison questions, SAA-C03, 2026 edition.

Try 6 free SQS-vs-SNS-vs-EventBridge questions in the exam's own style — every answer explained, no sign-up.

Straight to the 6 free questions ↓

SQS, SNS and EventBridge all move messages, and the SAA-C03 tests whether you can pick the right one. The distinction is the delivery model: buffer for one, broadcast to many, or route by rule.

The three jobs

  • Amazon SQS — a queue. Buffers messages durably until a single consumer pulls and processes them at its own pace, with retries and dead-letter queues. The answer to “don’t lose work; let the consumer catch up”.
  • Amazon SNS — publish/subscribe. Pushes one message to many subscribers at once — simple, low-latency, high-throughput fan-out. The answer to “notify several things immediately”.
  • Amazon EventBridge — an event bus. Routes events to many targets by content-based rules, with filtering, scheduled events, and third-party SaaS integration. The answer to “route events by what they contain, or on a schedule, or from a SaaS source”.

Buffer, broadcast, or route — that triad answers most questions.

The two distinctions the exam plants

SNS vs SQS is push vs pull: SNS broadcasts to all subscribers; SQS holds work for one consumer to pull. Reversing them is the classic distractor.

SNS vs EventBridge is the subtler one. Both fan out, but choose SNS for simple, very high-throughput fan-out, and EventBridge when you need rule-based routing, rich filtering across many AWS targets, scheduling, or SaaS event sources. Simple broadcast → SNS; smart routing → EventBridge.

They combine

These are not mutually exclusive. The classic pattern publishes to an SNS topic that fans out to several SQS queues, giving both broadcast and per-consumer durable buffering. EventBridge similarly routes an event to an SQS queue or Lambda target. Read the requirement for the primary need.

How to use the six questions below

Answer each before opening the explanation, and when you miss, name the delivery model the requirement wanted — “buffer for one”, “push to many”, “route by rule”, “on a schedule”, “from a SaaS source”. Every explanation states that model and dismantles the distractors. For the domain overview, see Design Resilient Architectures.

Three AWS messaging services compared. Amazon SQS is a queue that buffers messages durably for a single consumer to pull and process at its own pace. Amazon SNS is publish/subscribe that pushes one message to many subscribers at once for simple, high-throughput fan-out. Amazon EventBridge is an event bus that routes events to many targets by content-based rules, with filtering, scheduled events and integration with third-party SaaS event sources.

6 free SAA-C03 practice questions

Answers and explanations — no email wall
SAA-C03 Question 1 of 6

A single event must be delivered immediately to many subscribers at once — several Lambda functions and an email endpoint — with simple, high-throughput fan-out. Which service fits best?

Answer: A — Amazon SNS.

SNS is publish/subscribe: one message published to a topic is pushed to all subscribers at once — simple, low-latency, high-throughput fan-out. Why not the others: SQS is a queue delivering each message to a single consumer, not a broadcast. Direct calls to each subscriber couple the producer to every recipient and fail if one is down. Kinesis is for high-volume streaming with ordered replayable records, heavier than simple fan-out. Push one message to many is SNS.

SAA-C03 Question 2 of 6

Work items must be buffered durably so a single processing service can pull and handle them at its own pace, retrying failures. Which service fits?

Answer: A — Amazon SQS.

SQS is a queue that stores messages durably until a consumer pulls them, processes at its own rate, and can retry or dead-letter failures — the buffering-for-one-consumer job. Why not the others: SNS pushes to subscribers and does not hold work for a single consumer to pull. EventBridge routes events to targets by rule; it is not a durable work queue you pull from. A database used as a queue re-implements SQS poorly, with polling and locking overhead. Durable buffering for a consumer is SQS.

SAA-C03 Question 3 of 6

A company needs to route events to many different targets based on the content of each event, with rich filtering rules — for example, sending only high-value orders to one workflow and refunds to another. Which service is designed for this?

Answer: A — Amazon EventBridge.

EventBridge is an event bus that routes events to targets using content-based rules, so different event patterns go to different targets with rich filtering — exactly the requirement. Why not the others: SNS can filter per subscription but is oriented to pub/sub fan-out rather than routing by detailed content to many distinct AWS targets. A single SQS queue delivers to one consumer with no routing. An ALB balances HTTP traffic, not events. Content-based event routing with rules is EventBridge.

SAA-C03 Question 4 of 6

An application must react to events originating from a third-party SaaS provider (such as a payment or support platform) and route them into AWS services. Which service natively supports SaaS partner event sources?

Answer: A — Amazon EventBridge.

EventBridge integrates with third-party SaaS partners as event sources, delivering their events onto an event bus you can route into AWS — the native SaaS integration described. Why not the others: SQS and SNS handle messages your own systems publish; they do not natively ingest SaaS partner event streams. Direct Connect is a network link to on-premises, unrelated to SaaS events. Native SaaS event integration is EventBridge.

SAA-C03 Question 5 of 6

A workload needs to trigger a target on a fixed schedule — for example, running a cleanup task every night at 02:00. Which service provides scheduled, cron-style event triggering?

Answer: A — Amazon EventBridge (scheduled rules / Scheduler).

EventBridge supports scheduled rules (and EventBridge Scheduler) that trigger targets on a cron or rate schedule — the managed way to run something nightly. Why not the others: SQS delayed messages postpone a single message by up to 15 minutes, not a recurring nightly schedule. SNS has no scheduled-topic feature. A permanently running EC2 instance for cron is unnecessary standing cost when a managed scheduler exists. Managed scheduled triggering is EventBridge.

SAA-C03 Question 6 of 6

How should a solutions architect summarize when to choose SQS, SNS or EventBridge?

Answer: A — SQS to buffer work for one consumer; SNS to push one message to many subscribers; EventBridge to route events to many targets by content rules and integrate SaaS/schedules.

The clean split is buffer-for-one (SQS), push-to-many (SNS), and route-by-rule with rich filtering, scheduling and SaaS integration (EventBridge). Why not the others: they are not interchangeable — each has a distinct delivery model. The third option reverses SQS and SNS (SQS is the queue, SNS is the fan-out) and miscasts EventBridge as a load balancer. Newest is not a selection criterion. Buffer, broadcast, or route — that triad chooses the service.

That is exactly how every question in the course works — answer, explanation, why-not. The real set continues in the practice player: 10 free questions, no sign-up.

Continue with the 10 free questions →

Those 6 questions were the start.

The exam does not test whether you recognise a term — it tests whether you can rule out three plausible answers under time pressure. That is what the explanations above are for, and there are 780 more questions built exactly like them.

Collecting questions yourself

  • Scattered across forums, of unknown age
  • Answer keys without reasoning
  • No idea which domain you are weak in

Practising with a system

  • 780 questions in 12 full tests, SAA-C03 (2026)
  • Every option explained — including the wrong ones
  • Readiness per exam domain, and drills for your weakest
Start free — 10 questions

Straight into the player. No account, no email.

Frequently asked questions

SNS or EventBridge for fan-out?
Both can send an event to multiple targets. Choose SNS for simple, very high-throughput, low-latency fan-out to subscribers, SQS queues and Lambda. Choose EventBridge when you need content-based routing rules, filtering across many AWS targets, scheduled events, or integration with third-party SaaS sources. Simple broadcast leans SNS; rule-based routing leans EventBridge.
Do SNS and SQS work together?
Yes — a common pattern publishes to an SNS topic that fans out to several SQS queues, each feeding an independent consumer. SNS provides the broadcast, and each SQS queue provides durable buffering and retries for its consumer.
Are these real exam questions?
No. They are original scenarios written for this page in the exam's style and difficulty. Reproducing real exam items violates the AWS certification agreement and can cost a candidate their certification — ours come with the reasoning attached instead.
What is the one-line takeaway?
SQS buffers work for one consumer; SNS pushes one message to many; EventBridge routes events to many targets by content rules, on a schedule, and from SaaS sources.

Updated for SAA-C03 (July 2026). The sample questions above are our own work in the style of the exam — not real exam items. The exam itself is set and marked by the certification body.