A company is designing an event-driven order processing system. Each order requires multiple independent validation steps. Each validation step is implemented as an idempotent AWS Lambda function and needs only a subset of the order event data. The components must be loosely coupled and each validation Lambda should receive only the data it requires. Which solution meets these requirements?

The correct solution uses Amazon EventBridge because it natively supports content-based routing and input transformation, which directly addresses the requirements. EventBridge rules can filter events and use input transformers to select and reshape specific parts of the event data before sending it to the target Lambda functions. This ensures each validation Lambda receives only the necessary data and maintains loose coupling. The SQS queue per validation step option adds unnecessary complexity with an intermediary Lambda for transformation and publishing. The SNS topic with message body filtering can filter, but it doesn't easily support transforming the message content to send only the required subset of data to each subscriber. The single SQS queue with a transforming Lambda that synchronously invokes other Lambdas creates tight coupling and introduces a single point of failure and bottleneck.