AWS Certified Solutions Architect Professional SAP-C02 Practice Question
Your company is re-platforming its monolithic order-management application that currently runs on Amazon EC2 into a set of microservices. Each microservice will reside in its own AWS account that is part of the company's AWS Organizations structure. The architecture team has these goals:
The existing order service must publish order-created events and automatically route them to consumer microservices in other accounts without knowing their identities.
Future microservices must be able to process historical order events that occurred before they were deployed.
The solution must minimize the amount of custom infrastructure and operational overhead.
Which approach BEST meets these requirements?
Stream events into an Amazon Kinesis Data Stream in the order service account, enable enhanced fan-out to consumer applications in other accounts, and deliver the stream to Amazon S3 through Kinesis Data Firehose for historical replay.
Publish events to a FIFO Amazon SQS queue shared with consumer accounts. Configure a dead-letter queue in each consumer account and replay messages from the dead-letter queues when a new microservice is launched.
Publish events to a custom Amazon EventBridge event bus in the order service account, enable event archiving on the bus, and create EventBridge rules that forward events to cross-account event buses in consumer accounts. Consumer accounts can create rules or replay the archive when new microservices are deployed.
Publish events to an Amazon SNS topic in the order service account, subscribe Amazon SQS queues in each consumer account, and configure SNS message archiving to Amazon S3 for later replay.
Publishing the events to an Amazon EventBridge custom event bus and turning on event archiving meets all three goals. EventBridge rules can target event buses in other AWS accounts, providing cross-account fan-out without hard-coding consumer details. Enabling an archive on the source bus preserves events for an administrator-defined retention period and allows them to be replayed later, so new services can back-process historical events. Because EventBridge is fully managed, no clusters, connectors, or custom storage solutions have to be maintained.
The other options either lack native archive/replay (SNS+SQS, SQS FIFO) or require the team to build and operate additional streaming or storage infrastructure (Kinesis Data Streams with Firehose), so they do not satisfy the low-overhead or historical-replay requirements.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is Amazon EventBridge, and how does it enable cross-account event routing?
Open an interactive chat with Bash
How does enabling event archiving on EventBridge support historical replays?
Open an interactive chat with Bash
Why is Amazon EventBridge better than other options like Amazon SNS+SQS for this use case?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Accelerate Workload Migration and Modernization
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access