Invoking Lambda for Redshift Load Status via EventBridge
A company loads transaction data for each day into Amazon Redshift tables at the end of each day. The company wants to have the ability to track which tables have been loaded and which tables still need to be loaded. A data engineer wants to store the load statuses of Redshift tables in an Amazon DynamoDB table. The data engineer creates an AWS Lambda function to publish the details of the load statuses to DynamoDB. How should the data engineer invoke the Lambda function to write load statuses to the DynamoDB table?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The core concept tested is using Amazon EventBridge as a serverless event bus to decouple data ingestion from status tracking, avoiding direct polling or complex orchestration.
This question addresses integrating Amazon Redshift Data API with AWS Lambda and EventBridge to track table load statuses. It establishes that publishing events to EventBridge is the correct mechanism to trigger downstream processing.
Candidates often choose SQS (Option C) thinking it's for buffering, but Redshift Data API natively integrates with EventBridge for monitoring events, not SQS.
Community Discussion (7 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Using the Amazon Redshift Data API to publish events to Amazon EventBridge allows the system to react automatically when data loading operations complete or fail. EventBridge rules can then filter these events and invoke the Lambda function asynchronously, which writes the status to DynamoDB. This pattern leverages native AWS integrations for reliable, scalable event-driven architecture.Why the Other Options Are Wrong
Option A creates unnecessary coupling by having one Lambda invoke another, which is less efficient than an event bus. Option C is incorrect because the Redshift Data API does not have a native integration to push messages directly to an SQS queue; it publishes to EventBridge. Option D relies on CloudTrail, which logs API calls for security auditing but is not designed for real-time operational event processing like load status updates, and typically has higher latency.Community Comment Notes
Many learners initially questioned if the Data API could 'publish' directly to EventBridge, noting that while the documentation shows monitoring events, the integration is indeed supported for this use case. Some users suggested CloudTrail (D) as an alternative, but experts clarified that CloudTrail is for audit trails, not functional workflow triggers. The consensus remains that EventBridge is the standard service for handling such operational events in AWS.Official Reference
Exam Strategy
Always look for native integrations between services. If a service generates events (like database operations), check if it supports publishing to EventBridge before considering manual polling or secondary functions.
Frequently Asked Questions
Why not use CloudTrail to trigger Lambda?
CloudTrail is for security auditing and logging API calls, not for real-time operational workflows. It lacks the low-latency event routing needed for immediate load status updates.
Can Redshift Data API send to SQS?
No, the Redshift Data API natively integrates with Amazon EventBridge for monitoring and event notifications. It does not have a direct connector to SQS.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →