An analytics workflow uses an AWS Lambda function invoked asynchronously to process transaction records. Sometimes the asynchronous invocations fail. When a failure occurs, the developer wants a second Lambda function to be invoked to handle the error and record details. Which solution meets this requirement?

Configuring a Lambda function destination for failures directly addresses the requirement. When an asynchronously invoked Lambda function fails, AWS can automatically send the invocation record to a specified destination, such as another Lambda function. This allows the error-handler function to be invoked with details about the failed invocation. Enabling X-Ray tracing is for monitoring and debugging, not for automatically invoking another Lambda on failure. Configuring a Lambda function trigger with a failure condition is not a standard Lambda configuration option. Creating a status-check alarm on the primary Lambda function would monitor metrics, but it wouldn't inherently pass the specific failed event details to the error-handler Lambda, nor is it the most direct solution for handling individual asynchronous invocation failures.