Exam AWS Certified Data Engineer - Associate DEA-C01 topic 1 question 14 discussion

https://docs.aws.amazon.com/redshift/latest/mgmt/data-api-monitoring-events.html

The most appropriate way for the data engineer to invoke the Lambda function to write load statuses to the DynamoDB table is: B. Use the Amazon Redshift Data API to publish an event to Amazon EventBridge. Configure an EventBridge rule to invoke the Lambda function. Explanation: Option B leverages the Amazon Redshift Data API to publish events to Amazon EventBridge, which provides a serverless event bus service for handling events across AWS services. By configuring an EventBridge rule to invoke the Lambda function in response to events published by the Redshift Data API, the data engineer can ensure that the Lambda function is triggered whenever there is a new transaction data load in Amazon Redshift. This approach offers a straightforward and scalable solution for tracking table load statuses without relying on additional Lambda functions or services.

Here's why Option B is best: Amazon Redshift Data API can be used by applications and scripts to interact with Redshift (e.g., run SQL queries, check load status). Amazon EventBridge can receive custom events or service-generated events and route them to targets like Lambda. This approach decouples the data load process from status logging, using EventBridge as a clean integration point. EventBridge rule can filter and trigger the Lambda function when Redshift (or your data pipeline) signals a successful data load.

the data engineer should use Amazon EventBridge (formerly CloudWatch Events) to trigger the Lambda function based on a schedule or events that correspond to the completion of the data load process in Amazon Redshift.

The statement in B is inaccurate. You don't 'use Amazon Redshift Data API to publish' event to EventBridge. Redshift Data API has no function to write to EventBridge. Instead, the statement should be "Use EventBridge to monitor Data API events..." Perhaps this is a typo. But if I assume there are no typos in all the statements, then I would go for D. Although not a perfect solution, the cloud trail events have more info than the Redshift Data API events.

This job doesn’t need a real time check

Why not used SQS to keep API change in the Queue ?

Im not 100% sure of B or C, this is a tricky question. The reason is due to either SQS or EventBridge has not direct connection natively speaking to Redshift Data API. There is no way to publish events by itself. So, this means either SQS / EventBridge eventually need a "proxy" (e.g lambda function) in order to publish events or process events to this 2 sources. In both services we need something to publish those events from Redshift. so Yes, we need a lamda function between Redshift Data API and (SQS|EB). so either B,C doesnt seem to be 100% right. I think this question its a good candidate to be "Choose two options" but none has 100% right. Both are valid considering that there is an adapter function between 2 solutions.