A company has an event-driven JavaScript app built from decoupled managed AWS services that publish, consume, and route events. During testing, EventBridge rules are not delivering events to their targets. Testers need ways to view, debug, and avoid losing events without redeploying the app. Which combination of actions should the DevOps team take? (Choose three.)

To debug EventBridge rule delivery issues and prevent event loss, a multi-pronged approach is best. Configuring an Amazon SQS standard queue as a dead-letter queue (DLQ) for the EventBridge rule ensures that events that fail to be delivered to their primary target are not lost and can be inspected later. Creating a CloudWatch Logs log group and adding it as an additional target for the EventBridge rule allows for real-time logging and visibility into the events being processed by the rule, aiding in debugging. Enabling CloudTrail and creating a trail that logs to an S3 bucket provides an audit trail of API calls made to EventBridge, which can help identify configuration changes or issues that might be preventing event delivery. Using an SQS FIFO queue as a DLQ is generally unnecessary for this scenario as event order is often not critical for failed deliveries, and standard queues offer higher throughput and lower cost. Launching AWS Device Farm is irrelevant as it's for mobile app testing, not EventBridge debugging. Updating the application with AWS X-Ray SDK is for tracing requests within the application code, not for debugging EventBridge rule delivery failures directly.