An IT service provider is using continuous integration and is considering the introduction of continuous delivery. Which is a benefit of this proposed change for the service provider?
A.
Developers spend less time fixing issues in their code
B.
Code is tested iteratively and frequently
C.
Deployments of software builds are scripted to allow for automation
D.
Users experience changes which are smaller and more frequent
Continuous delivery (CD) in ITIL 4 extends continuous integration (CI) by ensuring that every validated change is ready for deployment to production, enabling smaller and more frequent releases. The key benefit for users is that they experience changes which are smaller and more frequent (Option D), reducing risk, improving feedback cycles, and delivering value faster.
Option A (Developers spend less time fixing issues in their code):Incorrect, as while CD may reduce some issues through automation, this is not its primary benefit, and CI already includes frequent testing to catch issues early.
Option B (Code is tested iteratively and frequently):Incorrect, as iterative and frequent testing is a feature of continuous integration, not a new benefit introduced by continuous delivery.
Option C (Deployments of software builds are scripted to allow for automation):Incorrect, as scripting and automation are part of both CI and CD pipelines, not a unique benefit of introducing CD.
Option D (Users experience changes which are smaller and more frequent):Correct, as CD enables rapid, incremental releases to production, directly benefiting users with faster and less disruptive updates.
[Reference:ITIL 4 Practitioner: Deployment Management, Section on Continuous Delivery – Highlights smaller, frequent releases as a key advantage for user value delivery., ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit