Which statement best describes canary deployment evaluation?

Which statement best describes canary deployment evaluation?

• A. You release to all users at once.
• B. You deploy to production without monitoring.
• C. You gradually expose more users to the new version and monitor metrics.
• D. You never roll back once deployed.

Answer: (C)

Canary deployment evaluation is about releasing the new version to a small, controlled portion of users first and then gradually expanding exposure while watching production metrics. This approach lets you learn in real time how the change behaves under real load, catching issues early with a minimal impact on the overall user base. Key signals to monitor include error rates, latency, resource usage, and any business or feature-specific metrics; if everything stays healthy, you slowly roll out to more users. If problems appear, you can stop the rollout or roll back with less disruption and risk. That’s why the option describing gradually exposing more users to the new version and monitoring metrics is the best fit. Releasing to everyone at once eliminates the safety net, deploying without monitoring is unsafe, and not rolling back after deployment ignores the fundamental safety mechanism of canary testing.

Canary deployment evaluation is about releasing the new version to a small, controlled portion of users first and then gradually expanding exposure while watching production metrics. This approach lets you learn in real time how the change behaves under real load, catching issues early with a minimal impact on the overall user base. Key signals to monitor include error rates, latency, resource usage, and any business or feature-specific metrics; if everything stays healthy, you slowly roll out to more users. If problems appear, you can stop the rollout or roll back with less disruption and risk.

That’s why the option describing gradually exposing more users to the new version and monitoring metrics is the best fit. Releasing to everyone at once eliminates the safety net, deploying without monitoring is unsafe, and not rolling back after deployment ignores the fundamental safety mechanism of canary testing.