Q: Explain the difference between Blue/Green deployment and Canary deployment.

• Blue/Green: You maintain two identical production environments. The current live environment is "Blue". You deploy the new code to the "Green" environment, run integration tests against it in isolation, and when ready, you instantaneously flip the router/load balancer to send 100% of user traffic to Green. If something goes wrong, you instantly flip the router back to Blue for a zero-downtime rollback. It requires 2x the infrastructure capacity.
• Canary: You deploy the new code to a small subset of servers (the "canary"), and route only a tiny percentage of traffic (e.g., 5%) to it. You monitor the error rates and metrics on the canary. If stable, you gradually increase traffic (10%, 25%, 100%). If it fails, only 5% of users are impacted, and it automatically rolls back. It requires complex traffic routing (like a Service Mesh or ALB weighted rules).

Execute the resolution runbook and verify workload health: