A market-research multi-agent system must, for each product brief, simultaneously gather competitive pricing, social sentiment, and regulatory notes from three independent specialist agents, then produce one consolidated research pack. Latency budgets require that the three specialists run at the same time rather than waiting on each other. Which orchestration pattern should the team implement?
Select an answer to reveal the explanation.
Short Explanation
You need three independent analyses at the same time, then one merged pack. That is classic parallel (concurrent) orchestration: fan out, work in parallel, reduce. Sequential chaining would add latency you do not have. Handoff gives the whole job to one specialist, which fails the multi-perspective requirement. Endless peer chat without a reducer never reliably produces a single consolidated artifact. So C is correct—parallel fan-out plus an aggregator.
Full Explanation
Correct answer: C. Multi-agent orchestration patterns include parallel (concurrent) execution when independent specialist work can proceed simultaneously and a reducer merges results. This matches simultaneous pricing, sentiment, and regulatory collection with a consolidated research pack and a latency budget that forbids sequential waiting.
A is incorrect because sequential orchestration serializes specialists, increasing end-to-end duration without adding dependency value when tasks are independent.
B is incorrect because handoff transfers exclusive ownership to a single agent and does not collect multi-specialist outputs for the same brief.
D is incorrect because unmanaged peer-to-peer chat without termination and aggregation strategies risks unbounded conversation and fails to guarantee a single consolidated deliverable.
Exam focus: match independence + latency to parallel orchestration with explicit aggregation.