A multi-agent workflow calls an external pricing API tool that intermittently returns 503s. You need robust tool error handling and fallback so the orchestration does not crash the user session. What should you implement?
Select an answer to reveal the explanation.
Short Explanation
Correct answer: A. Tools fail—that’s life. Retries with backoff, result validation, cache/secondary fallback, and a graceful “we can’t price this right now” path keep the orchestrator adult. Hallucinating prices on a 503 is how finance incidents start.
Full Explanation
Developers must design tool error-handling and fallback mechanisms and implement tool result validation. Option A includes retries, validation, fallbacks, and controlled degradation—production-grade behavior for flaky tools.
Option B is unsafe hallucination on failure.
Option C is brittle and poor UX/ops practice.
Option D removes observability needed to fix the dependency.
Exam tip: Correct tool-resilience answers combine retry/validate/fallback/degrade—not silent invention of data.