API Gateway is needed to get the data so option A and C are out. “The company wants to use these data points in its existing analytics platform” so there is no need to add Kynesis. Option D is also out. This leaves us with option B as the correct one.

I dont understand why you will vote B? how are you going to store data with just lambda? > Which action meets these requirements for storing and retrieving location data In this use case there will obviously be a ton of data and you want to get real-time location data of the bicycles, and to analyze all these info kinesis is the one that makes most sense here.

Option A makes more sense as this provide both storing option as S3 and rest endpoint in Athena to retrieve data points integrating with S3

B for sure

you can't store data in lambda

Track location, it should be streaming

D is more reasonable than B

https://docs.aws.amazon.com/lambda/latest/dg/services-apigateway.html

Amazon API Gateway with Amazon Kinesis Data Analytics is used for processing and analyzing streaming data in real-time using SQL or Apache Flink. While it's suitable for real-time analytics, it's not typically used for storing and retrieving data in a RESTful API format.

The company wants to use these data points in its existing analytics platform We don't need analytics platform, B. The correct answer

B. The q states that they already have an analytics platform, I thought D but that would be changing the platforms.

Keyword: "Accessible from the REST API". So option A and C are not correct Option. Remaining Options B and D. Option B is not a correct answer because After API Gateway to Lambda Function, what next ?. where will data go ?. but with Option D API Gateway with Kenesis Data Stream you have an option of sending data(through Firehose) to third party partner destination like DataDog, NewRelic, MongoDB, Splunk etc. Correct Answer D

selected answer: D kinesis can store the data for analysis.

We need API Gateway for rest apis, so A and C are out. Among B and D, there is an existing analytics platform so no need for Kinesis. Also, Kinesis Data Analytics relies on data source: either Kinesis Data Firehose or Kinesis Data Streams. It cannot work directly with API Gateway, so option D) is out. That leaves B).

D because B mentions no way to store data.

Comparison to other options: A. Athena and S3: While storing data in S3 and querying it with Athena is cost-effective, it wouldn't provide real-time data access needed for the API. C. QuickSight and Redshift: QuickSight and Redshift are excellent for analytics, but wouldn't directly expose data through the API. You'd still need a Lambda function to act as an intermediary. D. API Gateway and Kinesis Data Analytics: Kinesis Data Analytics is suitable for real-time streaming analysis, but it wouldn't directly provide a REST API endpoint. You'd need additional setup like API Gateway or Lambda for API access.

Kinesis Data Analytics requires a Kinesis Data Streams or Kinesis Data Firehose as input streams, so you cannot directly connect it to API Gateway, therefore B is the answer