DAS-C01 · Question #107
A company is building a service to monitor fleets of vehicles. The company collects IoT data from a device in each vehicle and loads the data into Amazon Redshift in near-real time. Fleet owners…
The correct answer is A. Use S3 event notifications to trigger an AWS Lambda function to copy the vehicle reference data. Using S3 event notifications to trigger an AWS Lambda function provides near-real-time loading. The moment a CSV file lands in S3, the S3 event fires, Lambda executes, and the reference data is copied into Amazon Redshift (via a COPY command or direct insert). This eliminates…
Question
A company is building a service to monitor fleets of vehicles. The company collects IoT data from a device in each vehicle and loads the data into Amazon Redshift in near-real time. Fleet owners upload .csv files containing vehicle reference data into Amazon S3 at different times throughout the day. A nightly process loads the vehicle reference data from Amazon S3 into Amazon Redshift. The company joins the IoT data from the device and the vehicle reference data to power reporting and dashboards. Fleet owners are frustrated by waiting a day for the dashboards to update. Which solution would provide the SHORTEST delay between uploading reference data to Amazon S3 and the change showing up in the owners' dashboards?
Options
- AUse S3 event notifications to trigger an AWS Lambda function to copy the vehicle reference data
- BCreate and schedule an AWS Glue Spark job to run every 5 minutes.
- CSend reference data to Amazon Kinesis Data Streams.
- DSend the reference data to an Amazon Kinesis Data Firehose delivery stream.
How the community answered
(27 responses)- A78% (21)
- B4% (1)
- C11% (3)
- D7% (2)
Explanation
Using S3 event notifications to trigger an AWS Lambda function provides near-real-time loading. The moment a CSV file lands in S3, the S3 event fires, Lambda executes, and the reference data is copied into Amazon Redshift (via a COPY command or direct insert). This eliminates the current 24-hour delay. A Glue Spark job every 5 minutes (B) introduces up to a 5-minute delay plus job startup time and is more expensive. Options C and D (Kinesis Streams and Firehose) would require changing how fleet owners upload their data, adding complexity and not matching the existing S3 upload workflow.
Topics
Community Discussion
No community discussion yet for this question.