An AI architect at a national healthcare provider is maintaining an agentic AI system.

The NVIDIA implementation angle is not cosmetic here: TensorRT-LLM and NIM reduce inference overhead, but they still need serving-level tuning to avoid queue buildup under concurrency. Triton plus Prometheus/Grafana gives live metrics; NGC/model repositories support versioned lifecycle control. Cron logs are not enough for healthcare operations. Option C wins because it optimizes the system boundary around the risky component rather than hoping the base model behaves consistently. The selected option specifically C states “Deploy agent models on NVIDIA Triton Inference Server with Prometheus and Grafana for performance alerting, and manage model lifecycle via NGC and the Triton model repository.”, which matches the operational requirement rather than a superficial wording match. The durable control mechanism is matching model precision, batch windows, model instances, and GPU memory behavior to the latency service-level objective. The losing choices mostly optimize for short-term convenience; hardware upgrades alone do not fix poor batching, serial ensembles, guardrail overhead, or KV-cache pressure. For certification purposes, read the question as asking for controlled autonomy, not raw LLM creativity.