For maintenance with zero downtime and the ability to recover in about ten minutes, which methodology should be selected?

For maintenance with zero downtime and the ability to recover in about ten minutes, which methodology should be selected?

• A. Rolling update
• B. Patching directly
• C. Blue-green deployment
• D. Three staging environments

Answer: (D)

Maintaining service without downtime relies on redundancy and a fast path to switch production away from a problematic change. Having multiple staging environments gives you a built-in, ready-to-switch setup that mirrors production, so you can keep user traffic flowing while updates are tested and applied safely. With three staging environments, one can serve as the live production mirror, while another remains a fully tested, production-like environment that can take over quickly if something goes wrong, and the third serves as a safe space for ongoing validation and maintenance work. During maintenance, you route traffic to the standby environment that is known-good and prepped for production. Updates can be applied in the primary environment while the standby handles requests, and if issues appear, you can promote the standby or roll back to a previously stable state in minutes. This setup supports both zero-downtime execution of maintenance and a rapid, roughly ten-minute recovery window because the switch is already designed into the environment infrastructure. Other approaches can also reduce downtime—rolling updates spread changes across instances, and blue-green deployments switch all traffic to a separate, fully updated environment—but they require different configurations (like dual production-like environments or per-connection routing). Patching directly without a switch typically incurs downtime. The three-staging-environments approach emphasizes having ready-to-switch, production-like environments to keep services live while maintenance is performed and to enable quick rollback.

Maintaining service without downtime relies on redundancy and a fast path to switch production away from a problematic change. Having multiple staging environments gives you a built-in, ready-to-switch setup that mirrors production, so you can keep user traffic flowing while updates are tested and applied safely.

With three staging environments, one can serve as the live production mirror, while another remains a fully tested, production-like environment that can take over quickly if something goes wrong, and the third serves as a safe space for ongoing validation and maintenance work. During maintenance, you route traffic to the standby environment that is known-good and prepped for production. Updates can be applied in the primary environment while the standby handles requests, and if issues appear, you can promote the standby or roll back to a previously stable state in minutes. This setup supports both zero-downtime execution of maintenance and a rapid, roughly ten-minute recovery window because the switch is already designed into the environment infrastructure.

Other approaches can also reduce downtime—rolling updates spread changes across instances, and blue-green deployments switch all traffic to a separate, fully updated environment—but they require different configurations (like dual production-like environments or per-connection routing). Patching directly without a switch typically incurs downtime. The three-staging-environments approach emphasizes having ready-to-switch, production-like environments to keep services live while maintenance is performed and to enable quick rollback.