// Orchestration · Quiz
Tier 2 check Seven questions, one for each multi-agent shape: orchestrate, supervise, layer, chain, fan out, map-reduce and debate. Pick an answer, then check it. Nothing is saved or sent.
01 You need research, drafting and fact-checking, and one agent keeps losing track. You add an orchestrator. What is its job?Write the final post itself, using the others for ideas Split the goal into parts, hand each to a specialist subagent, and merge the results Score each specialist’s output and veto anything unsafe Run the same job on every chunk of the input
Check answer
02 Workers draft replies; you need a referee that can reject unsafe output. Which pattern fits best?ReAct with a longer system prompt Sequential Pipeline with three free-text stages MapReduce over the ticket history Supervisor — picks who goes next, scores, and can reject, without drafting
Check answer
03 In a three-layer Hierarchical setup (strategy, tactics, tools), the strategy agent starts calling a search tool directly. What is wrong?Nothing — any layer may call any tool Layers should only talk to their neighbours; strategy should hand the request to the tactics layer The tools layer should be removed Strategy should run in parallel with tactics
Check answer
04 Outline → draft → edit run in a fixed order. The editor keeps “fixing” things the outline never asked for. What does the Sequential Pipeline lesson suggest?Give each stage only the previous stage’s output in a small, checked format, and stop if it doesn’t match Let every stage read the full conversation so far Run the three stages at the same time Add a debate between the outliner and the editor
Check answer
05 Scenario: research docs, blog, and changelog independently, then merge. The branches do not need each other’s results. Pick the pattern.Sequential Pipeline — stage A must finish before B starts Hierarchical Agents — strategy calls tools directly Parallel Fan-Out / Fan-In — run the independent branches at once, then join Debate — pro and con argue about the docs
Check answer
06 You have one long transcript and want the same extraction job run on every chunk, then the results combined. What do you reach for?Debate — two agents argue about each chunk Supervisor — reject every chunk summary Tool Use alone — one schema, no splitting MapReduce — the same map job on every chunk, then a reduce step that combines them
Check answer
07 A single cheerful pass keeps missing rollout risks on a go/no-go call. Which orchestration shape surfaces the downside?Sequential Pipeline with more stages Debate — a pro side and a con side for a set number of rounds, then a judge Plan-and-Execute with a longer plan Parallel Fan-Out of three identical cheerleaders
Check answer
0 correct · 0 of 7 answered