Redesign a retail order platform as serverless microservices with EventBridge

SAP-C02 By islever Editorial Last updated

Determine a new architecture for existing workloads. Determine opportunities for modernization and enhancements. Design reliable and resilient architectures.

Short answer

C Use EKS Fargate microservices, Aurora Serverless MySQL, Redshift Serverless, and EventBridge to distribute the incoming events.

Question

A retail company wants to improve its application architecture. The company's applications register new orders, handle returns of merchandise, and provide analytics. The applications store retail data in a MySQL database and an Oracle OLAP analytics database. All the applications and databases are hosted on Amazon EC2 instances. Each application consists of several components that handle different parts of the order process. These components use incoming data from different sources. A separate ETL job runs every week and copies data from each application to the analytics database. A solutions architect must redesign the architecture into an event-driven solution that uses serverless services. The solution must provide updated analytics in near real time. Which solution will meet these requirements?
  1. Migrate the individual applications as microservices to Amazon Elastic Container Service (Amazon ECS) containers that use AWS Fargate. Keep the retail MySQL database on Amazon EC2. Move the analytics database to Amazon Neptune. Use Amazon Simple Queue Service (Amazon SQS) to send all the incoming data to the microservices and the analytics database.
  2. Create an Auto Scaling group for each application. Specify the necessary number of EC2 instances in each Auto Scaling group. Migrate the retail MySQL database and the analytics database to Amazon Aurora MySQL. Use Amazon Simple Notification Service (Amazon SNS) to send all the incoming data to the correct EC2 instances and the analytics database.
  3. Migrate the individual applications as microservices to Amazon Elastic Kubernetes Service (Amazon EKS) containers that use AWS Fargate. Migrate the retail MySQL database to Amazon Aurora Serverless MySQL. Migrate the analytics database to Amazon Redshift Serverless. Use Amazon EventBridge to send all the incoming data to the microservices and the analytics database. Correct Answer
  4. Migrate the individual applications as microservices to Amazon AppStream 2.0. Migrate the retail MySQL database to Amazon Aurora MySQL. Migrate the analytics database to Amazon Redshift Serverless. Use AWS IoT Core to send all the incoming data to the microservices and the analytics database.

Key Takeaways

The weekly ETL job is the root of the analytics latency, so replacing it with an event bus that fans every incoming data event out to both the microservices and the analytics database removes the batch window entirely and delivers the near real-time requirement.

A retail company's order registration, returns handling, and analytics applications are multi-component applications running on EC2 with MySQL and an Oracle OLAP database, and a weekly ETL job copies data into the analytics database. The redesign must be event-driven, use serverless services, and provide analytics in near real time.

Common mistake: Using SQS as the fan-out mechanism. SQS is a queue where each message is consumed by a single consumer, so competing consumers would each need their own queue and the analytics database would not receive the same events as the microservices, making near real-time distribution to both awkward.

Expert Analysis

Why the Answer Is Correct

Amazon EventBridge is an event bus that delivers each event to every interested consumer, which is exactly the fan-out pattern the architecture needs: incoming data goes to the bus and both the application microservices and the analytics path receive it. The applications become microservices on EKS with Fargate, which is serverless at the compute layer, so the team does not manage EC2 instances. The retail MySQL database moves to Aurora Serverless MySQL and the Oracle OLAP analytics database moves to Redshift Serverless, so the data stores are also serverless. Because the ETL job is replaced by the event bus, the analytics warehouse is updated as events arrive rather than weekly, which delivers the near real-time requirement.

Why the Other Options Are Wrong

A: Amazon Neptune is a graph database, which is the wrong data model for retail order and returns analytics, and keeping MySQL on EC2 leaves a server-managed database in an architecture that must use serverless services. B: Fixed-size Auto Scaling groups of EC2 instances and Aurora MySQL are not serverless, and SNS notification delivery is not the mechanism to route each event's data to specific processing components, so the redesign requirement is not met. D: AppStream 2.0 is a managed desktop application streaming service and AWS IoT Core is an IoT device messaging service, so neither is a general application event bus, making this option irrelevant to the workload described.

Community Comment Notes

The community voted 100 to 0 for C, and the top-voted comment identified the two decisive disqualifiers in A and B, that SQS is not for near real-time distribution and that MySQL on EC2 is not serverless, while option D uses AppStream for desktop streaming and IoT Core for IoT. Another commenter noted the single-word reason, serverless.

Official Reference

https://docs.aws.amazon.com/redshift/latest/mgmt/serverless-ch.html

This link opens the official vendor documentation in a new tab.

Community Votes

C
100%

100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. CMMC 👍 5 Answered C
    #A - SQS is not for near real time. MySQL on EC2 is not serverless #B is not serverless #D is incorrect - Appstream for desktop app streaming and IoT Core for IoT
  2. Dgix 👍 3 Answered C
    C is serverless. D is rubbish.
  3. AzureDP900 👍 1
    C is right. This solution involves migrating individual applications as microservices to Amazon EKS containers that use Fargate, moving the retail MySQL database to Amazon Aurora Serverless MySQL, and migrating the analytics database to Amazon Redshift Serverless. Using Amazon EventBridge allows you to send all incoming data to the microservices and the analytics database in near real time.
  4. oayoade 👍 2 Answered C
    "serverless"

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Modernize centralized firewall appliances with a Gateway Load Balancer and Auto Scaling

S-grade

Use Lambda over a CloudWatch Logs stream to count unique users per client

S-grade

Serve global game assets with Route 53 latency records and health checks

S-grade

Reach a cross-account S3 data lake through a gateway endpoint and an access point bucket policy

S-grade

Practice All SAP-C02 Questions

Access 85 questions with complete answers and detailed explanations.

View Full SAP-C02 Practice Test →

← Back to SAP-C02 Study Guide