All level 4 passages

When Software Rolls Back

A software team releases a new version of an online service. Minutes later, error reports rise. Customers cannot complete purchases, and the support queue grows. The team could keep repairing the new version while everyone waits. Instead, it may roll back the release.

A rollback restores a previously working version. Modern deployment systems often keep an older package ready, along with records of settings and database changes. Switching back can reduce harm quickly and give engineers time to investigate while customers use the restored service.

Rolling back is not the same as reversing time. Some actions may already have changed stored data. A new version might write information in a format the old version cannot read. Customers may have submitted orders between the release and the rollback. Teams plan migrations carefully so changes can coexist with both versions, or they prepare a separate recovery step.

The decision also uses evidence. A small rise in harmless warnings may not justify disruption. Failed payments or lost records demand faster action. Teams define signals and thresholds before release, then monitor them. Gradual rollouts limit the number of users exposed while evidence accumulates. A rollback is therefore one safeguard planned before release. It gives the team a tested response if real use reveals a serious problem.

Check your understanding

Answer 4 questions about this passage and see why each answer is right

Questions and pace mode are free with sign-in.

Sign in free to answer

About pace mode

Signed in, you can choose a pace from 150 to 400 words per minute. A highlight moves through the passage, then the questions check what you understood. Choose Off to read at your own speed.

Pace mode measures this reading session. It is not a measure of your overall reading ability.

Practice reading