DEA-C01 · Question #250
A company uses AWS Glue jobs to implement several data pipelines. The pipelines are critical to the company. The company needs to implement a monitoring mechanism that will alert stakeholders if the…
The correct answer is C. Create an Amazon EventBridge rule to match AWS Glue job failure events. Define an Amazon. By creating an EventBridge rule that matches Glue job state-change events where the state is FAILED, you can emit a custom CloudWatch metric without writing any code. Then you define a CloudWatch alarm on that metric to notify an SNS topic upon breach. This approach requires no…
Question
A company uses AWS Glue jobs to implement several data pipelines. The pipelines are critical to the company. The company needs to implement a monitoring mechanism that will alert stakeholders if the pipelines fail. Which solution will meet these requirements with the LEAST operational overhead?
Options
- ACreate an Amazon EventBridge rule to match AWS Glue job failure events. Configure the rule to
- BConfigure an Amazon CloudWatch Logs log group for the AWS Glue jobs. Create an Amazon
- CCreate an Amazon EventBridge rule to match AWS Glue job failure events. Define an Amazon
- DConfigure an Amazon CloudWatch Logs log group for the AWS Glue jobs. Create an Amazon
How the community answered
(27 responses)- A7% (2)
- B4% (1)
- C74% (20)
- D15% (4)
Explanation
By creating an EventBridge rule that matches Glue job state-change events where the state is FAILED, you can emit a custom CloudWatch metric without writing any code. Then you define a CloudWatch alarm on that metric to notify an SNS topic upon breach. This approach requires no Lambda functions or log parsing (just the rule, the metric, and the alarm) minimizing operational
Topics
Community Discussion
No community discussion yet for this question.