Once the city’s pipeline verifies a build, the same automation releases the artifact to staging without waiting for a separate weekly install crew. Which concept does this highlight?
Select an answer to reveal the explanation.
Short Explanation
When green builds roll into staging by themselves, you’re looking at continuous delivery/deployment—the ‘ship it’ half of CI/CD. The install crew’s weekly queue becomes the exception, not the rule. Automation carries the artifact the last mile.
Full Explanation
Once the city's pipeline verifies a build and the same automation releases the artifact to staging without waiting for a separate weekly install crew, the concept is continuous deployment or continuous delivery of verified artifacts into target environments. Trusted builds move forward automatically so municipal staging stays aligned with main and install-crew latency no longer gates learning. Air-gapping the repository from all runners after the first green build stops delivery instead of enabling it. Requiring USB-only installs even when the pipeline already produced the package reintroduces manual delay the scenario removes. Treating staging as an unmanaged laptop under someone's desk abandons environment parity and auditability for city services. Exam caveat: continuous delivery often keeps a production approval gate while continuous deployment may promote automatically; exam language may blur the terms—focus on automated promotion of verified artifacts. Operational check: after a green pipeline, confirm the artifact reaches staging without a weekly install crew, verify version metadata matches the commit, retain production approvals if policy requires, and document the civic promotion path in the release runbook.