Distinguish deployment from release in software delivery.

Distinguish deployment from release in software delivery.

• A. Release means database changes only; deployment means features are live
• B. Deployment and release are the same thing
• C. Deployment makes changes to the environment; release makes features available to users
• D. Release is about performance tuning

Answer: (C)

The main idea being tested is how deployment and release differ in software delivery. Deployment is the technical process of moving code and changes into an environment (such as staging or production) and making the system ready to run those changes. It can involve deploying new code, database migrations, and updating services, and it can happen without users seeing any change—think of a dark deploy or a blue-green rollout where the code is live but features aren’t yet exposed. Release, on the other hand, is about making those features visible and usable by users. It’s the activation of the new functionality for end users, which can be controlled through feature flags, rollout plans, and communications. You can deploy code without releasing it to users, and you can release features through toggles even while the underlying code is already in production. So the correct choice captures the distinction: deployment changes the environment, while release makes features available to users. The other options mix up these roles or assert they are the same, which isn’t accurate—for example, release isn’t limited to database changes, deployment isn’t the same as releasing features, and release isn’t primarily about performance tuning.

The main idea being tested is how deployment and release differ in software delivery. Deployment is the technical process of moving code and changes into an environment (such as staging or production) and making the system ready to run those changes. It can involve deploying new code, database migrations, and updating services, and it can happen without users seeing any change—think of a dark deploy or a blue-green rollout where the code is live but features aren’t yet exposed.

Release, on the other hand, is about making those features visible and usable by users. It’s the activation of the new functionality for end users, which can be controlled through feature flags, rollout plans, and communications. You can deploy code without releasing it to users, and you can release features through toggles even while the underlying code is already in production.

So the correct choice captures the distinction: deployment changes the environment, while release makes features available to users. The other options mix up these roles or assert they are the same, which isn’t accurate—for example, release isn’t limited to database changes, deployment isn’t the same as releasing features, and release isn’t primarily about performance tuning.