A city release process still waits for a monthly weekend freeze, but leadership wants every commit to trigger automated build and test instead. What DevOps shift does this describe?
Select an answer to reveal the explanation.
Short Explanation
Monthly big-bang weekends are the old fire drill. CI/CD flips that: every commit gets built and tested automatically so problems show up Tuesday at 2 p.m., not during a Saturday cutover. Less heroics, more conveyor belt.
Full Explanation
A city release process that still waits for a monthly weekend freeze, while leadership wants every commit to trigger automated build and test, describes the DevOps shift toward CI/CD automation that continuously builds and tests rather than relying only on rare manual releases. Continuous integration shrinks batch size, accelerates feedback, and reduces the risk that municipal changes pile up until a stressful freeze window. Replacing all automated tests with handwritten change-control PDFs only abandons the speed and repeatability leadership requested. Outsourcing source control to removable USB drives couriered between buildings adds loss and tampering risk while destroying collaboration. Disabling pipelines so developers deploy straight from their laptops nightly removes verification gates and creates untracked production drift. Exam caveat: CI/CD does not erase change management—it embeds quality gates in automation; regulated civic workloads may still require recorded approvals before production. Operational check: connect commits to build and test jobs, fail on test errors, publish status to pull requests, compare lead time with the old monthly freeze, and document which environments still need manual civic approval.