A team deploys multi-agent infrastructure and prompt/tool packages by clicking in the Azure portal and copying files over SSH. Releases are inconsistent across environments. What CI/CD approach should they adopt?
Select an answer to reveal the explanation.
Short Explanation
Correct answer: D. Treat multi-agent systems like real software: IaC and app artifacts in git, automated tests/evals in pipelines, versioned promotions with gates. Portal click-ops and wiki memories (A), open production SSH (B), and USB sneaker-net (C) guarantee drift and weak audit trails. Include evaluation suites in the pipeline so quality is a release criterion, not an afterthought.
Full Explanation
CI/CD requirements for multi-agent solutions include integration/release automation, infrastructure-as-code, and testing. Option D codifies environments, versioned promotions, and gated approvals. Options A–C are manual, insecure, or non-repeatable. A solid pipeline builds container/agent packages, applies IaC, runs unit/integration/evaluation tests, and deploys via DTAP or progressive delivery with rollback. Secrets stay in Key Vault, not in pipeline logs.