Developers on the housing-vouchers service merge small changes into a shared mainline several times a day, each time running automated checks. Which CI/CD concept is this?
Select an answer to reveal the explanation.
Short Explanation
Continuous integration means ‘merge early, merge often, and let the robots yell if you broke something.’ Tiny daily merges beat a giant conflict pile at month-end. Shared mainline plus automated checks is the heartbeat.
Full Explanation
Developers on the housing-vouchers service merging small changes into a shared mainline several times a day, each time running automated checks, demonstrate continuous integration of code into a shared mainline with automated verification. Frequent small integrations keep municipal codebases releasable, surface merge conflicts early, and make failures cheaper to diagnose than giant weekend batches. Cold-site disaster recovery rehearsals performed only annually are resilience exercises, not CI practice. Manual watermarking of every PDF before storage tiering is a records process unrelated to mainline code integration. Quarterly capacity reservations with no code involvement are capacity or FinOps activities, not continuous integration. Exam caveat: CI is about frequent integration plus automated build/test; continuous delivery and continuous deployment extend automation toward environments and are related but distinct concepts on Cloud+. Operational check: confirm the housing-vouchers repository merges to main multiple times daily with required checks green, track mean time to restore a broken main, discourage long-lived divergence, and publish the civic CI definition of done for the service team.