A security workflow invokes a Step Functions workflow when EventBridge matches certain events coming from multiple AWS services. CloudTrail records user actions, but some important events are not triggering the workflow. CloudTrail logs show no direct errors. Which steps will help identify the root cause of the missing EventBridge invocations? (Choose three.)

Enabling EventBridge schema discovery helps confirm if the incoming events from CloudTrail align with the EventBridge rule's event pattern. Mismatched schemas are a common reason for events not triggering rules, even without direct errors. Setting up CloudWatch monitoring for EventBridge and Step Functions metrics, with anomaly alerts, provides proactive detection of issues in event delivery or workflow invocations, indicating when events aren't reaching their target. Inspecting EventBridge failed-invocation metrics directly reveals if events are attempting to trigger the rule but failing, often due to insufficient IAM permissions on the rule's role. Adding a Lambda to log events is reactive and less efficient than schema discovery for initial diagnosis. Examining Step Functions execution history is useful if invocations are occurring but failing, but it won't help if events aren't even reaching Step Functions. Confirming Step Functions permissions is relevant if invocations are failing, but not for events that aren't triggering the workflow at all.