An ML-based monitoring service is configured as an EventBridge API destination to consume Auto Scaling events. CloudWatch indicates the EventBridge rule is firing, but the monitoring service is not receiving events. The SysOps administrator wants to capture client error details with minimal operational effort. Which solution should be implemented?

Attaching an Amazon SQS standard queue as a dead-letter queue (DLQ) for the EventBridge target is the most efficient solution. When EventBridge fails to deliver an event to its target (the monitoring service, in this case), the event is sent to the DLQ. Inspecting messages in the SQS queue will provide the exact error details from the failed delivery attempts, directly addressing the need to capture client error details with minimal operational effort. Creating an EventBridge archive and replaying events is more complex and doesn't immediately provide error details for the current failures. Creating a second EventBridge rule with a Lambda function adds unnecessary complexity and latency. Configuring an Amazon SNS topic for error messages is a viable option for notifications, but an SQS DLQ provides the actual failed event messages, which is crucial for detailed error inspection.