Which deployment method updates servers in successive waves to minimize impact?

Which deployment method updates servers in successive waves to minimize impact?

• A. Canary deployment
• B. Rolling deployment
• C. Hotfix
• D. Rollback

Answer: (B)

Rolling deployment gradually updates servers in successive groups across the fleet. After each group, you check health and performance before moving to the next, so any issues affect only a portion of the system and can be contained quickly. This minimizes risk and downtime because you can stop the process and roll back if problems appear. A hotfix is an urgent patch to fix a bug; a rollback undoes a previous deployment; while a canary deployment starts with a very small subset to observe behavior before broader rollout, the approach described—updating in waves across the whole fleet—is best captured by rolling deployment.

Rolling deployment gradually updates servers in successive groups across the fleet. After each group, you check health and performance before moving to the next, so any issues affect only a portion of the system and can be contained quickly. This minimizes risk and downtime because you can stop the process and roll back if problems appear. A hotfix is an urgent patch to fix a bug; a rollback undoes a previous deployment; while a canary deployment starts with a very small subset to observe behavior before broader rollout, the approach described—updating in waves across the whole fleet—is best captured by rolling deployment.