Continuous Deployment automation is absent on the public-health immunization registry ART, so every validated change waits for a quarterly cutover. What CD purpose should the RTE summarize?
Select an answer to reveal the explanation.
Short Explanation
If every registry fix sits on the dock until the quarterly boat leaves, the pipeline is a calendar, not a path. Continuous Deployment is the automated walk from validated change into staging and production-like environments. The RTE names that purpose; the ART still decides when citizens see it.
Full Explanation
Continuous Deployment automates promotion of validated changes into staging and production-like environments so the ART is not gated by a quarterly cutover. On an immunization registry train, that capability shortens the wait after development without automatically releasing every commit. The RTE summarizes CD as a CDP stage and supports investment in it. Equating CD with PI Planning, with manual clinic entry, or with mandatory go-live of every commit misstates the stage.