Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 107 discussion

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.

better for streaming data

D. Use Amazon API Gateway with Amazon Kinesis Data Analytics. Why? Real-time Data Processing: Amazon Kinesis Data Analytics can process streaming data (e.g., bicycle locations) in real-time. REST API Access: Amazon API Gateway can provide a secure REST API for accessing the processed data. Scalability & Performance: Kinesis efficiently ingests large volumes of data during peak hours. Integration with Analytics: The processed data can be stored in Amazon S3, DynamoDB, or Redshift for further analytics.

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.

when choosing between B and D: "The company wants to use these data points in its existing analytics platform." so need for Lambda to integrate data points in its existing analytics platform

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.

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.

lambda can store data in db which is not mentioned but can be implemented, wherein kinesis data analytics would be more complex to implement just for simple location tracking. Also, a data analytics tool is already there. Hence, B is more suitable.

Amazon Kinesis Data Analytics allows you to build more complex analytics applications that support flexible processing choices and robust fault-tolerance with exactly-once processing without duplicates, and analytics that can be performed over an entire data stream across multiple logical partitions. With KDA, you can analyze data over multiple types of aggregation windows (tumbling window, stagger window, sliding window, session window) using either the event time or the processing tim

Lambda is not most viable, or real time

Given that the company already has an existing analytics platform and needs a solution for storing and retrieving location data that can be accessed through a REST API, the best choice is: B. Use Amazon API Gateway with AWS Lambda

Kinesis is specifically designed for telemetry data, making it a better fit for tracking bicycle locations.

B. Amazon API Gateway com AWS Lambda: Essa combinação é útil para fornecer APIs REST, mas o Lambda não é otimizado para ingestão contínua de dados de localização em tempo real. Ele seria mais adequado para processos eventuais ou tarefas específicas.

the best answer is B: Use Amazon API Gateway with AWS Lambda Reasoning: API Gateway provides the required REST API endpoint Lambda can handle real-time processing of location data This combination is cost-effective and scalable Can easily integrate with other AWS services for analytics Provides the necessary multi-tier architecture (API Layer, Processing Layer, Storage Layer)

A common use is the real-time aggregation of data followed by loading the aggregate data into a data warehouse or map-reduce cluster. https://docs.aws.amazon.com/streams/latest/dev/introduction.html#using-the-service

D is the most viable multi-tier option, as it supports real-time data ingestion, analytics, and accessibility through a REST API.