A retailer wants a multi-agent solution that handles “resolve a lat…

Question

A retailer wants a multi-agent solution that handles “resolve a late shipment”: detect delay, check inventory alternatives, propose options to the customer, and create a replacement order only after confirmation. How should you decompose the goal into agents and tools at the logical architecture level?

Accepted Answer

Separate agents (or subagents) for delay detection, inventory alternatives, customer communication, and order creation—each with narrowly scoped tools—and a workflow with a human-in-the-loop (or explicit customer confirmation) gate before the order-creation tool runs. — Correct answer: C. Good multi-agent architecture is mise en place: one station for detecting delay, one for inventory options, one for talking to the customer, one for writing the order—and a confirmation gate before anything expensive fires. Narrow tools beat one agent with keys to the kingdom.

Answer

One monolithic agent with a single unbounded tool that can read and write every enterprise system without sub-goals.

Answer

Three human employees only, with no software agents, because multi-agent design cannot include human-in-the-loop confirmation.

Answer

A pure batch ETL pipeline that nightly reprocesses all shipments without interactive agents or tools.

Short Explanation

Full Explanation