At production scale, Option A preserves separability between reasoning, state, tools, and runtime operations.
For a production build, Triton dynamic batching and model configuration are where throughput and tail latency tradeoffs become controllable. The selected option specifically A states "Use Docker containers orchestrated by Kubernetes, implement MLOps pipelines for CI/CD, monitor agent health with Prometheus
/Grafana.", which matches the operational requirement rather than a superficial wording match. Kubernetes, CI/CD, and Prometheus/Grafana are production operations basics. Manual scripts and single-node deployments cannot sustain agent fleets. The high-value engineering move is dynamic batching, model instance tuning, concurrency control, precision optimization, KV-cache-aware LLM serving, and end-to-end latency waterfalls. The distractors fail because sequential microservices can add avoidable hops and tail latency even when every individual model looks fast. Anything less would make the agent fragile when traffic, schemas, policies, or user behavior shift. For LLM systems, the bottleneck often shifts between compute kernels, KV cache memory, request queues, and guardrail/tool latency.