Enterprise policy requires multi-agent solutions to move through Development, Test, Acceptance, and Production with infrastructure-as-code and a documented rollback. Which design meets this?
Select an answer to reveal the explanation.
Short Explanation
Answer C. Multi-environment release strategies include DTAP, rollback, release management, and IaC CI/CD. Promote multi-agent artifacts through gated environments. Shared prod/experiment sandboxes, portal hotfixes on personal accounts, and zip-via-email are not enterprise release designs.
Full Explanation
Correct answer: C. Specify CI/CD and multi-environment releases for multi-agent systems: IaC for Azure resources, automated unit/integration/regression tests and evaluations, controlled promotion DTAP-style, and rehearsed rollback (previous prompt/graph/model deployment).
A is incorrect: mixing experimental agents with live traffic violates isolation and change control.
B is incorrect: unaudited portal edits under personal identities break governance.
D is incorrect: ad-hoc script zips lack repeatability, review, and infrastructure consistency.
Include agent-specific artifacts (prompts, MCP server versions, evaluation baselines) in the release package.