Architects must specify observability so on-call engineers can reconstruct why five agents produced a wrong refund decision. Which observability components should be included?
Select an answer to reveal the explanation.
Short Explanation
Correct answer: A. When five agents touch a refund, you need a flight recorder: correlation IDs across services, structured logs of who thought what and which tools fired, and replay so you can re-run the path. Node CPU charts alone won’t explain a bad decision.
Full Explanation
Technology component specification includes observability: cross-service trace correlation, structured logging of agent reasoning paths, and agent replay capture for reproducible debugging. Option A matches those requirements and supports multi-agent incident response.
Option B is insufficient: infrastructure metrics lack agent reasoning and tool-level causality.
Option C is not systematic or scalable observability.
Option D actively undermines reliability and auditability.
Exam tip: Multi-agent observability answers should mention correlation IDs, reasoning/tool logs, and replay—not only host metrics.