What deployment strategy updates a small subset of servers first to test before proceeding to the rest?

• A. Rolling deployment
• B. Hotfix
• C. Canary deployment
• D. Blue-green deployment

Answer: (C)

The idea being tested is reducing risk by exposing a new release to only a small portion of the environment first and watching how it behaves before wider rollout. This approach is exactly what a canary deployment does: the update is released to a limited set of servers (or traffic) in production, metrics and logs are monitored for errors or performance problems, and only if everything looks good is the update gradually rolled out to the rest. If issues arise, the change can be halted or rolled back with minimal impact.

Other strategies don’t match this targeted, small-sample testing pattern. A rolling deployment gradually updates the fleet, but it doesn’t inherently emphasize testing a tiny pilot group before proceeding. A blue-green deployment relies on switching traffic between two complete environments, which is a full swap rather than a staged, observational rollout. A hotfix is a rapid corrective patch applied to address a specific problem, not a method for validating a new release in production before wider distribution.