What is the most idiomatic (used for its intended purpose) design to call each API request in the Mule application?

A mule application is being designed to perform product orchestration. The Mule application needs to join together the responses from an inventory API and a Product Sales History API with the least latency.

To minimize the overall latency.

What is the most idiomatic (used for its intended purpose) design to call each API request in the Mule application?
A . Call each API request in a separate lookup call from Dataweave reduce operator
B . Call each API request in a separate route of a Scatter-Gather
C . Call each API request in a separate route of a Parallel For Each scope
D . Call each API request in a separate Async scope

Answer: B

Explanation:

Scatter-Gather sends a request message to multiple targets concurrently. It collects the responses

from all routes, and aggregates them into a single message.

Reference: https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept