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 the path of validated changes into staging and production-like environments instead of waiting on a quarterly cutover. When public-health immunization registry CD automation is absent, the RTE should summarize that purpose. Claiming Continuous Deployment is the same as PI Planning so the next quarterly event will cover it confuses planning cadence with deployment automation. Claiming CD means clinic staff enter registry updates by hand after each immunization day describes manual data entry, not CD. Claiming CD replaces Release on Demand so the ART must go live with every commit erases the business release decision. Public-health partners need faster, safer promotion paths than a quarterly cutover ritual; Continuous Deployment addresses that path while Release on Demand retains clinic-facing timing. Exam caveat: production release for health data may remain gated; CD still automates the path up to and through controlled environments. Operational check: automate promotion of validated registry builds into a production-like environment each iteration and retire the quarterly-only cutover as the sole path. Retire quarterly-only cutover as the sole path once automated promotion into production-like environments is proven.