A municipal DevOps policy says the test environment deploys from the develop branch while production deploys only from tagged releases on main. How should the team wire deployments?
Select an answer to reveal the explanation.
Short Explanation
Branches and tags are the labels on the shipping crates. Point test at develop and production only at tagged main releases so unfinished work never rides into citizen-facing systems. Feature-branch prod deploys and hand-copied zips skip that gate.
Full Explanation
Code repositories feed environment-specific deployments. Associating non-production with an integration branch (such as develop) and production with annotated release tags on main is a standard promotion model for developer workflows using CodePipeline or similar CI. It keeps unfinished routes out of production while preserving a clear audit of what was released. Feature-branch production deploys, auto-promoting develop, or manual S3 zip copies undermine that control.