A multi-agent engineering team wants consistent local-to-cloud SDLC…

Question

A multi-agent engineering team wants consistent local-to-cloud SDLC: reproducible dev environments, IDE support, CLI automation, dependency control, and shared AI coding instructions. Which technology-component specification best supports this?

Accepted Answer

Standardize on dev containers (or equivalent reproducible environments), VS Code (or supported IDE) extensions for Azure/Foundry workflows, CLI for automation, dependency lockfiles, and shared AI instruction files for consistent agent-assisted development. — Correct answer: D. Multi-agent SDLC still needs grown-up engineering hygiene: dev containers so “works on my machine” dies, IDE extensions and CLI for speed, lockfiles for deps, and shared AI instructions so the whole team’s copilots pull in the same direction.

Answer

Each developer installs random global Python packages by hand with no lockfiles and edits production agents directly.

Answer

Ban all IDEs and require Notepad-only editing to reduce tooling complexity.

Answer

Avoid CLI tools so that every change must be performed exclusively through production portal click-ops.

A multi-agent engineering team wants consistent local-to-cloud SDLC: reproducible dev environments, IDE support, CLI automation, dependency control, and shared AI coding instructions. Which technology-component specification best supports this?

Short Explanation

Full Explanation