To roll out a change means to release it progressively to users or servers. It is the standard collocation: "roll out the update to 10% first". "Unroll", "roll over", and "spread out" are not the term. Roll out pairs with gradually, in stages, and to a cohort, and is central to safe deployment strategies.
2 / 5
If metrics look healthy we ___ to 100% of traffic.
To ramp up means to gradually increase the share of users or traffic receiving a change. It is the natural collocation: "ramp up the rollout to 50%". "Climb up", "step over", and "build over" are not idiomatic. Ramp up pairs with rollout, traffic, and exposure, and its opposite is "ramp down" when reverting.
3 / 5
We can ___ the feature so we can toggle it without redeploying.
To flag a feature means to put it behind a feature flag (a toggle) so it can be turned on or off independently of deployment. It is the standard collocation: "flag the new checkout behind a feature flag". "Mark off", "tab", and "pin" are not the term. Flag pairs with feature and works as both noun (a feature flag) and verb.
4 / 5
We will ___ the redesign to internal users before the public sees it.
To dark-launch a feature means to release it silently (often hidden or to a limited audience) to test it in production before the public reveal. It is the established collocation: "dark-launch the new pipeline". "Night-launch", "shadow-launch out", and "quiet-fire" are not standard. Dark-launch lets teams validate behaviour under real load with minimal user impact.
5 / 5
If errors spike, we immediately ___ to the previous version.
To roll back means to revert a deployment to a known-good previous version. It is the essential safety collocation: "roll back the bad release". "Roll off", "turn back", and "fall back over" are not the term. Roll back pairs with release, deploy, and version, and is the counterpart to rolling out.