During a canary deployment, what is typically done after the canary group proves stable?

• A. Rollback all changes
• B. Ignore feedback and continue
• C. Penalize the developers
• D. Proceed to full deployment, updating the remaining servers

Answer: (D)

Canary deployment is a controlled rollout approach where a new release is released to a small subset of servers or users first to watch how it behaves in real, real-world conditions. Once that canary group proves stable—no notable errors, performance stays within acceptable limits, and user experience remains good—the next step is to roll the update out to the remaining servers. This phased expansion lets you confirm that the new version scales and behaves as expected before a full deployment, reducing risk and catching issues early.

Metrics matter here—watch error rates, latency, resource usage, and user feedback to confirm stability before widening the rollout. Rolling back everything would be chosen only if the canary reveals problems, which is exactly what this process aims to prevent by not pushing blindly to everyone. Ignoring feedback or treating the rollout as a done deal defeats the purpose of canaries and isn’t how a safe deployment is managed.