What is a primary benefit of a rolling deployment?

What is a primary benefit of a rolling deployment?

• A. Eliminate the need for backups
• B. Minimize impact by updating servers gradually
• C. Increase instantaneous downtime
• D. Require full system reboot

Answer: (B)

Rolling deployments update servers in small batches instead of updating everything at once. This approach keeps most servers serving traffic while a subset is updated, so if something goes wrong you can stop, fix, or roll back without affecting the entire service. Traffic can gradually move to the updated instances, allowing real-world validation with minimal disruption. The net effect is reduced impact and lower downtime during the rollout, which is the main benefit. Backup strategies are still important, and a rolling deployment doesn’t imply a full system reboot across all servers.

Rolling deployments update servers in small batches instead of updating everything at once. This approach keeps most servers serving traffic while a subset is updated, so if something goes wrong you can stop, fix, or roll back without affecting the entire service. Traffic can gradually move to the updated instances, allowing real-world validation with minimal disruption. The net effect is reduced impact and lower downtime during the rollout, which is the main benefit. Backup strategies are still important, and a rolling deployment doesn’t imply a full system reboot across all servers.