1 / 5
Releasing an update to a growing percentage of users over several days is a ___ rollout.
-
-
-
-
A phased (staged) rollout exposes the update to an increasing share of users, limiting the blast radius of any regression.
2 / 5
If crash reports spike during a rollout, you can ___ it to stop further distribution.
-
-
-
-
Halting (pausing) the rollout freezes the current percentage so no additional users receive the problematic build while you investigate.
3 / 5
The metric most teams watch during a phased rollout to decide whether to continue is the ___.
-
-
-
-
The crash-free user/session rate is a key health signal; a drop suggests the new build is unstable for real users.
4 / 5
After fixing an issue, you can ___ a paused rollout to continue increasing the percentage.
-
-
-
-
Resuming continues the staged rollout from where it was paused, gradually reaching 100% of users once health metrics look good.
5 / 5
Pushing the update to everyone at once, skipping stages, is a ___ release.
-
-
-
-
A full (100%) release reaches all eligible users immediately; it is faster but offers no staged safety net if something breaks.