CGOA practice question 1 of 15

When are progressive delivery patterns useful in software development and deployment?

Answer options

A: Progressive delivery patterns are only useful for one-time, single-deployment scenarios, not ongoing, continuous delivery.

B: Progressive delivery patterns are primarily beneficial for small development teams rather than for large organizations.

C: Progressive delivery patterns are useful in several software development and deployment scenarios, as they offer advantages such as risk reduction, improved quality, and better user experience. Correct answer

D: Progressive delivery patterns are useful during initial project development instead of in subsequent phases.

Correct Answer:

C. Progressive delivery patterns are useful in several software development and deployment scenarios, as they offer advantages such as risk reduction, improved quality, and better user experience.

Explanation

Progressive delivery techniques—blue/green, canary, feature-flag rollouts—are expressly designed to let teams release code continuously while controlling blast-radius, validating behaviour in production, and gathering user feedback before 100 % exposure. This makes them valuable not just at one point in time or for a particular team size, but across many development and deployment scenarios: high-frequency releases, large-scale systems, mobile “dark-launches,” critical updates, A/B experiments, and gradual regional rollouts. Their core benefits are reduced risk of widespread failure, earlier detection of defects, protection of user experience and the ability to roll back quickly, thereby improving overall quality and reliability.

Why Incorrect

A. Limits usefulness to a single deployment; ignores continual risk-mitigation purpose of progressive delivery.
B. Benefit derives from deployment approach, not team size; large organizations gain even more from controlled rollouts.
D. Technique remains equally (or more) important in later phases when software reaches real users and needs safe updates.

References

1. The Linux Foundation, “Introduction to GitOps (LFS169x)”, Module 6: Progressive Delivery, slides 3-6 (course notes, 2023).

2. CNCF GitOps Working Group, “GitOps Principles – Progressive Delivery”, Section 3, para 2, GitHub repo commit a4f2c3 (2022).

3. G. Kim & N. Davis, “Progressive Delivery: Safer Continuous Deployment at Scale”, IEEE Software, 39(3), pp. 56-62, 2022. DOI:10.1109/MS.2021.3088012

4. Argo Rollouts Documentation (v1.5), “Concepts – Progressive Delivery Strategies”, pages 1-2, The Linux Foundation, 2023.

5. MIT xPRO Course “Cloud-Native Continuous Delivery”, Unit 4.4, lecture notes “Risk Reduction with Canary & Blue/Green”, p. 4 (2023).

Keep practicing

Take the free CGOA practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test