(A) - You don't need to deploy an EC2 instance to host an API - Operational overhead (B) - Same as A (**C**) - Is the answer (D) - AWS Glue gets data from S3, not from API GW. AWS Glue could do ETL by itself, so don't need lambda. Non sense. https://aws.amazon.com/glue/

The company needs an API = Amazon API Gateway API A real-time data ingestion = Amazon Kinesis data stream A process that transforms data = AWS Lambda functions Kinesis Data Firehose delivery stream to send the data to Amazon S3 A storage solution for the data = Amazon S3

C is least operational overhead A: EC2 is overhead in this scenario B: Same as A D: Glue is not real time data streaming

It looks overengineered, but as it works, let's go for the C

The company needs an API = Amazon API Gateway API A real-time data ingestion = Amazon Kinesis data stream A process that transforms data = AWS Lambda functions Kinesis Data Firehose delivery stream to send the data to Amazon S3 A storage solution for the data = Amazon S3

"a real-time data ingestion" isn't firehose not realtime ? Kinesis FireHose is "Near" Real-time . It has 60 seconds gap. I think it should be D

Option C provides the least operational overhead to meet the requirements: API Gateway provides the API Kinesis Data Streams ingests the real-time data Lambda functions transform the data Firehose delivers the data to S3 storage The key advantages are: Serverless architecture requires minimal operational overhead Fully managed ingestion, processing and storage services No need to manage EC2 instances

Requirements: API- API gateway Real time data ingestion - AWS Kinesis data stream ETL(Extract Transform Load) - Kinesis Firehose Storage- S3

C - is the answer

C. By leveraging these services together, you can achieve a real-time data ingestion architecture with minimal operational overhead. The data flows from the API Gateway to the Kinesis data stream, undergoes transformations with Lambda, and is then sent to S3 via the Kinesis Data Firehose delivery stream for storage. A. This adds operational overhead as you need to handle EC2 management, scaling, and maintenance. It is less efficient compared to using a serverless solution like API Gateway. B. It requires deploying and managing an EC2 to host the API and configuring Glue. This adds operational overhead, including EC2 management and potential scalability limitations. D. It still requires managing and configuring Glue, which adds operational overhead. Additionally, it may not be the most efficient solution as Glue is primarily used for ETL scenarios, and in this case, real-time data transformation is required.

I am gonna choose D for this. Kinesis Data Stream + Data Firehose will adds up to the operational overhead, plus it is "Near real-time", not a real time solution. Lambda functions scale automatically, so no management of scaling/compute resources is needed. AWS Glue handles the data storage in S3, so no management of that is needed.

Gotta love all those chatgpt answers y'all are throwing at us. Kinesis Firehose is NEAR real-time, not real-time like your bots tell you.

option C is the best solution. It uses Amazon Kinesis Data Firehose which is a fully managed service for delivering real-time streaming data to destinations such as Amazon S3. This service requires less operational overhead as compared to option A, B, and D. Additionally, it also uses Amazon API Gateway which is a fully managed service for creating, deploying, and managing APIs. These services help in reducing the operational overhead and automating the data ingestion process.

Option C is the solution that meets the requirements with the least operational overhead. In Option C, you can use Amazon API Gateway as a fully managed service to create, publish, maintain, monitor, and secure APIs. This means that you don't have to worry about the operational overhead of deploying and maintaining an EC2 instance to host the API. Option C also uses Amazon Kinesis Data Firehose, which is a fully managed service for delivering real-time streaming data to destinations such as Amazon S3. With Kinesis Data Firehose, you don't have to worry about the operational overhead of setting up and maintaining a data ingestion infrastructure.

Option C

Option C

C is correct