On success, a license-PDF Lambda should hand a summary payload to EventBridge; on failure after retries, it should notify an ops SQS queue. Which feature routes those outcomes?
Select an answer to reveal the explanation.
Short Explanation
Success goes to the town herald (EventBridge); failures after retries go to the ops mailbox (SQS). Lambda Destinations are that labeled outbox. Duration alarms alone, API Gateway sync responses, and weekly S3 inventory mail don't give async success/failure routing.
Full Explanation
Lambda Destinations route asynchronous invocation results to targets such as EventBridge on success and SQS on failure after retries, beyond the original caller. CloudWatch duration alarms observe metrics but do not deliver success payloads. API Gateway synchronous responses apply to sync invokes. Weekly S3 inventory is not a real-time destination mechanism.