AWS Certified Solutions Architect – Associate (SAA-C03) — Question 275

A company is using AWS to design a web application that will process insurance quotes. Users will request quotes from the application. Quotes must be separated by quote type, must be responded to within 24 hours, and must not get lost. The solution must maximize operational efficiency and must minimize maintenance.

Which solution meets these requirements?

Answer options

• A. Create multiple Amazon Kinesis data streams based on the quote type. Configure the web application to send messages to the proper data stream. Configure each backend group of application servers to use the Kinesis Client Library (KCL) to pool messages from its own data stream.
• B. Create an AWS Lambda function and an Amazon Simple Notification Service (Amazon SNS) topic for each quote type. Subscribe the Lambda function to its associated SNS topic. Configure the application to publish requests for quotes to the appropriate SNS topic.
• C. Create a single Amazon Simple Notification Service (Amazon SNS) topic. Subscribe Amazon Simple Queue Service (Amazon SQS) queues to the SNS topic. Configure SNS message filtering to publish messages to the proper SQS queue based on the quote type. Configure each backend application server to use its own SQS queue.
• D. Create multiple Amazon Kinesis Data Firehose delivery streams based on the quote type to deliver data streams to an Amazon OpenSearch Service cluster. Configure the application to send messages to the proper delivery stream. Configure each backend group of application servers to search for the messages from OpenSearch Service and process them accordingly.

Correct answer: C

Explanation

Using a single Amazon SNS topic with SQS subscriptions and SNS message filtering provides a fully managed, serverless, and highly durable solution that requires minimal operational maintenance. Amazon SQS ensures that messages are not lost and can be stored safely for up to 14 days, easily meeting the 24-hour response requirement. Kinesis-based solutions (Options A and D) introduce unnecessary operational complexity and management overhead, while Option B lacks the durable queueing of SQS to guarantee message preservation during backend processing delays.