A company is choosing between Amazon SQS, Amazon SNS and Amazon EventBridge to ingest events from a third-party SaaS provider and route each event to different targets such as an AWS Lambda function or an AWS Step Functions workflow based on the event's content, without writing custom dispatch code. Which two capabilities are distinctive reasons to choose Amazon EventBridge for this design? Select TWO.
- AEventBridge guarantees strict first-in-first-out ordering and exactly-once processing for every event delivered to its targets.
- BEventBridge provides a poll-based queue where each consumer deletes messages after a visibility timeout to ensure single processing.
- CEventBridge offers partner event sources that ingest events directly from supported SaaS providers onto an event bus without building a custom integration. Correct
- DEventBridge rules match on event content and route matching events to targets such as Lambda or Step Functions, applying routing logic without custom dispatch code. Correct
- EEventBridge stores messages for up to fourteen days so a single worker fleet can drain a backlog at its own pace during traffic spikes.
Why A is wrong: FIFO ordering and exactly-once delivery are properties of SQS FIFO queues, not EventBridge, which delivers events at least once without guaranteed ordering.
Why B is wrong: Visibility timeouts and poll-and-delete semantics describe SQS; EventBridge is push-based and routes events to targets rather than offering a consumer-polled queue.
Why C is correct: Partner event sources let supported SaaS providers deliver events straight onto an EventBridge bus, removing the need to build and maintain a bespoke ingestion path.
Why D is correct: Content-based rules evaluate the event payload and invoke chosen targets declaratively, which removes the custom routing code the team wants to avoid.
Why E is wrong: Durable backlog retention for self-paced workers is an SQS strength; EventBridge focuses on routing events to targets, not buffering a backlog for polling consumers.