DOP-C02 · Question #328
A security team sets up a workflow that invokes an AWS Step Functions workflow when Amazon EventBridge matches specific events. The events can be generated by several AWS services. AWS CloudTrail…
The correct answer is B. Configure Amazon CloudWatch to monitor EventBridge metrics and Step Functions metrics. Set D. Review the Step Functions execution history for patterns of failures or timeouts that could E. Review metrics for the EventBridge failed invocations to ensure that the IAM execution role that is. CloudWatch provides metrics for both EventBridge and Step Functions. Monitoring these metrics will allow you to see if there are any anomalies in the event patterns or workflow invocations. You can set up alerts for any anomalies, which would indicate issues such as missed…
Question
A security team sets up a workflow that invokes an AWS Step Functions workflow when Amazon EventBridge matches specific events. The events can be generated by several AWS services. AWS CloudTrail records user activities. The security team notices that some important events do not invoke the workflow as expected. The CloudTrail logs do not indicate any direct errors related to the missing events. Which combination of steps will identify the root cause of the missing event invocations? (Choose three.)
Options
- AEnable EventBridge schema discovery on the event bus to determine whether the event patterns
- BConfigure Amazon CloudWatch to monitor EventBridge metrics and Step Functions metrics. Set
- CConfigure an AWS Lambda logging function to monitor and log events from EventBridge to
- DReview the Step Functions execution history for patterns of failures or timeouts that could
- EReview metrics for the EventBridge failed invocations to ensure that the IAM execution role that is
- FVerify that the Step Functions workflow has the correct permissions to be invoked by
How the community answered
(34 responses)- A6% (2)
- B53% (18)
- C12% (4)
- F29% (10)
Explanation
CloudWatch provides metrics for both EventBridge and Step Functions. Monitoring these metrics will allow you to see if there are any anomalies in the event patterns or workflow invocations. You can set up alerts for any anomalies, which would indicate issues such as missed events or workflows not being triggered. EventBridge provides metrics such as FailedInvocations and TriggeredRules, which help identify issues with event rule matching or invocations. Step Functions metrics, like ExecutionsStarted and ExecutionsFailed, can give insight into whether workflows were started and if they failed. Step Functions execution history can provide valuable insights into what happens after a workflow is invoked. If there are patterns of failures, errors, or timeouts in the execution, these might correlate with missing event invocations. Investigating this history helps to determine if the workflow was invoked and why it might have failed. EventBridge failed invocation metrics can indicate if the event rule matched but the invocation of the Step Functions workflow failed. This could happen if the IAM execution role attached to the EventBridge rule does not have the correct permissions to invoke the workflow. Ensuring that the EventBridge rule has the appropriate permissions for invoking the Step Functions workflow is critical for the proper functioning of the event-driven workflow. By focusing on monitoring metrics, reviewing Step Functions execution history, and ensuring EventBridge permissions are properly configured, you can effectively identify the root cause of the missing event invocations.
Topics
Community Discussion
No community discussion yet for this question.