You are implementing multi-agent orchestration on Azure using a gra…

Question

You are implementing multi-agent orchestration on Azure using a graph-based framework. The design needs an orchestrator that delegates to specialist subagents, supports conditional branches, and can wait for human approval on high-risk steps. Which approach fits?

Accepted Answer

Implement an orchestrator-subagent pattern in Agent Framework / LangGraph (or equivalent): graph nodes for orchestrator and specialists, conditional edges for routing, and an interrupt/HITL node for approval before high-risk tools. — Correct answer: B. LangGraph-style orchestrator-subagent graphs give you real control flow: route to specialists, branch on conditions, and park for human approval before the scary tools. Manual copy-paste between five chats is not an orchestration framework.

Answer

Encode the entire business process as a single non-branching string replacement script with no agent nodes.

Answer

Run five unrelated chat sessions and ask the user to copy-paste outputs between them manually.

Answer

Use only peer-to-peer spontaneous calls with no graph, no orchestrator, and no HITL hooks.

You are implementing multi-agent orchestration on Azure using a graph-based framework. The design needs an orchestrator that delegates to specialist subagents, supports conditional branches, and can wait for human approval on high-risk steps. Which approach fits?

Short Explanation

Full Explanation