A new app version only reveals some issues once it receives production traffic. To reduce impact and the number of affected users, which deployment strategy should you use?

Canary deployment is the best strategy here because it gradually rolls out the new version to a small subset of users first. This allows you to monitor for issues with real production traffic without affecting the majority of your user base. If problems arise, you can quickly revert the small canary group, minimizing impact. Blue/green deployment switches all traffic to the new version at once, which is risky if issues are only apparent under load. Rolling deployment updates instances one by one, but still exposes a significant portion of users to potential problems before they are fully identified. Recreate deployment takes down the old version completely before bringing up the new one, leading to downtime and a high-risk cutover.