At Orion Media, a new version of the billing application has been moved onto the production servers, but the team has deliberately kept the new invoicing feature switched off until finance signs off next week. Which pairing correctly matches these two activities to their ITIL 4 practices?
- AMoving the code to production is deployment management; switching the feature on for users is release management. Correct
- BMoving the code to production is release management; switching the feature on for users is deployment management.
- CBoth activities belong to deployment management, since each one touches the live production environment directly.
- DBoth activities belong to release management, since each one concerns delivering a new version of the application.
Why A is correct: Correct: deployment management moves new or changed components into an environment such as production, while release management makes new or changed features actually available for use, so the sign-off switch-on is a release activity.
Why B is wrong: Tempting because both terms sound interchangeable, but this reverses them: making a feature available is release, not deployment, and moving components into an environment is deployment, not release.
Why C is wrong: Tempting because both activities involve production, but ITIL 4 deliberately separates moving components (deployment) from making features available for use (release), so collapsing them into one practice is wrong.
Why D is wrong: Tempting because a new version is involved, but physically moving components into an environment is deployment management, so treating the whole thing as release ignores the distinction ITIL 4 draws.