Subdomain 1.2: Orchestrate multi-agent systems with coordinator-subagent patterns
1.An architect reviews a multi-agent research assistant and finds that each subagent independently implements its own retry logic, logging format, and rate-limit backoff, leading to inconsistent behavior across the system. Which change best aligns this design with the hub-and-spoke coordinator pattern's intended benefits?
- A.Paste one shared retry and backoff routine into each subagent's system prompt, leaving each subagent to apply it on its own
- B.Move retry handling into the coordinator and keep logging and backoff in each subagent, leaving them tuned to their own tools
- C.Add a dedicated subagent that applies the retry, logging and backoff policy for the others, leaving the coordinator to route work
- D.Move the retry, logging and backoff policy into the coordinator, leaving subagents to report failures and results back to it
Show answer & explanation
Correct answer: D — Move the retry, logging and backoff policy into the coordinator, leaving subagents to report failures and results back to it
- A. Pasting the same routine into each prompt keeps the policy inside the subagents, so every copy is still run and interpreted independently. Copies drift as they are edited, and a prompt cannot enforce identical behavior. The coordinator gains no central control over errors.
- B. Centralizing only retries leaves logging format and rate-limit backoff defined separately in each subagent, so two of the three reported inconsistencies remain. The coordinator still cannot see or control how failures are logged or throttled.
- C. A dedicated policy subagent adds a peer that must see the others' failures. In hub-and-spoke, the coordinator is the single point through which subagent communication and error handling pass, so this adds a hop and moves control away from the hub. The coordinator also loses direct visibility into failures.
- D. Correct. In hub-and-spoke, subagents communicate only through the coordinator, so it is the natural place for retry, logging and backoff policy. Subagents then report outcomes, and behavior is uniform and observable in one place.