You are designing a multi-agent solution for corporate travel. A supervisor must route requests to specialized agents (flights, hotels, policy compliance) that may run concurrently, then merge results for the user. Which logical orchestration pattern best fits?
Select an answer to reveal the explanation.
Short Explanation
You need hub-and-spoke because the supervisor routes, specialists work in parallel when independent, and results aggregate. A single mega-prompt loses clear scopes, unsupervised peer-to-peer with internet scans is chaotic and insecure, and forced full sequencing wastes time when flights and hotels are independent. Define clear personas and tool boundaries on each spoke.
Full Explanation
Architecting multi-agent solutions includes selecting orchestration patterns such as hub-and-spoke, sequential, parallel, peer-to-peer, and orchestrator-subagent. The travel scenario needs routing, specialization, concurrent work, and aggregation, matching hub-and-spoke. The single monolithic prompt abandons multi-agent structure. Peer-to-peer only with unrestricted internet scans removes control and introduces unsafe discovery. Strictly sequential chaining ignores beneficial parallelism. Define clear personas and tool boundaries on each spoke. Specify protocols for supervisor-to-agent messaging, timeouts, and failure handling when a spoke fails.