What should the solutions architect do to meet these requirements?

A company is developing a mobile game that streams score updates to a backend processor and then posts results on a leaderboard A solutions architect needs to design a solution that can handle large traffic spikes process the mobile game updates in order of receipt and store the processed updates in a highly available database. The company also wants to minimize the management overhead required to maintain the solution

What should the solutions architect do to meet these requirements?
A . Push score updates to Amazon Kinesis Data Streams Process the updates in Kinesis
Data Streams with AWS Lambda Store the processed updates in Amazon DynamoDB

B . Push score updates to Amazon Kinesis Data Streams Process the updates with a fleet of Amazon EC2 instances set up for Auto Scaling Store the processed updates in Amazon Redshifi
C . Push score updates to an Amazon Simple Notification Service (Amazon SNS) topic Subscnbe an AWS Lambda function to the SNS topic to process the updates Store the processed updates in a SQL database running on Amazon EC2
D . Push score updates to an Amazon Simple Queue Service (Amazon SQS) queue Use a fleet of Amazon EC2 instances with Auto Scaling to process the updates in the SQS queue Store the processed updates in an Amazon RDS Multi-AZ DB instance

Answer: A

Explanation:

https://docs.aws.amazon.com/streams/latest/dev/introduction.html

You can use Amazon Kinesis Data Streams to collect and process large streams of data records in real time. You can use Kinesis Data Streams for rapid and continuous data intake and aggregation. The type of data used can include IT infrastructure log data, application logs, social media, market data feeds, and web clickstream data. Because the response time for the data intake and processing is in real time, the processing is typically lightweight.

Latest SAA-C02 Dumps Valid Version with 230 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments