In the given deployment example, what happens if problems arise after the update is deployed?

• A. Rollback to the previous build
• B. Push another hotfix without rollback
• C. Ignore the issue until next release
• D. Remediate by redeploying the same version

Answer: (A)

When problems arise after a deployment, the fastest and safest recovery approach is to roll back to the previous build that was working correctly. This restores the system to a known good state quickly, reducing downtime and user impact while engineers diagnose and fix the new issue. By returning to the prior stable version, you preserve service continuity and create a safer window to validate fixes before attempting another deployment.

Deploying another hotfix without rollback can complicate the fault, potentially layering new changes on top of the problem and making it harder to identify the root cause. Ignoring the issue until the next release leaves users with a broken experience and delays a proper fix. Redeploying the same version would reintroduce the same problem and waste time, because you haven’t removed the faulty change that caused the issue in the first place.