Option D correctly identifies the importance of explicit coordination boundaries when multiple agents participate in a complex business process.
UiPath supports agent composition by allowing published agents to be invoked as tools and by providing orchestration capabilities for coordinating agents, robotic workflows, enterprise integrations, and human activities.
Each agent should perform a clearly defined responsibility and produce structured outputs that downstream components can interpret reliably.
Handoff rules specify the circumstances in which responsibility transfers from one component to another.
For example, an invoice classification agent may pass a validated classification to a financial verification agent. The downstream agent should receive the required data through a defined input schema and return a structured result.
Where classification uncertainty is relevant, the solution can use an appropriately validated confidence threshold or business-rule condition to determine whether processing continues or requires additional review.
Option A incorrectly assumes final human review guarantees correctness. Option B undermines the benefits of specialized agents. Option C permits uncontrolled delegation without safeguards.
For predictable orchestration, architects should also define error handling, timeout behavior, retries, escalation routes, and transaction boundaries.
UiPath recommends explicit tool descriptions and clear invocation conditions so agents understand when delegation is appropriate.
Official UiPath references/topics: Agents — Agents as Tools; Building Effective Agent Tools; Prompts, including tool invocation and escalation instructions.