A platform team wants every multi-agent change—prompt files, tool schemas, orchestration graphs, and Azure infrastructure—to follow the same quality bar before production. Which CI/CD requirement set best fits AI-500 deployment guidance?
Select an answer to reveal the explanation.
Short Explanation
The correct answer is B. Treat prompts, tools, graphs, and infra as code in one pipeline with unit, integration, regression, and automated evaluation gates before prod. Skipping tests from laptops is chaos. Non-determinism means you design evals carefully, not that you ban tests. Portal-first manual snowflakes fight IaC.
Full Explanation
Option B is correct. Deployment skills require CI/CD for integration and release, including infrastructure-as-code and testing strategies (unit, regression, integration, automated evaluations). Gating multi-agent artifacts on those checks enforces a consistent quality bar.
Option A is incorrect because workstation deploys without tests bypass review, reproducibility, and safety gates.
Option C is incorrect because non-determinism motivates statistical and rubric-based automated evaluations rather than abandoning testing.
Option D is incorrect because manual portal configuration diverges from code and undermines repeatable IaC releases.