An administrator needs to deploy a new release of an application in a way that allows a quick rollback to the previous version of the application. Which of the following is the BEST strategy to apply?

Question

Options

• ADeploy the application to a set of servers in small batches. If a rollback is necessary, restore the
• BDeploy the application to a subset of servers that expose the new application. Direct all traffic to
• CDeploy the application to the servers in a backup datacenter or secondary cloud deployment.
• DDeploy the application to all servers in the datacenter or cloud environment. If a rollback is

• A
  12% (4)
• B
  3% (1)
• C
  6% (2)
• D
  79% (26)

Explanation

Based on the context of the truncated answer choices, option D describes a deployment strategy where the new version is pushed to all servers while retaining the previous deployment artifacts or snapshots, enabling an immediate, full-environment rollback if needed. Deploying to all servers at once (sometimes paired with pre-deployment snapshots or versioned artifact storage) gives the fastest possible rollback path because no traffic-splitting or partial environment management is required-you simply redeploy the previous known-good version across the entire fleet. Options A (rolling batches) and B (canary/subset routing) are safer for risk mitigation during rollout but introduce complexity and partial states. Option C (secondary datacenter) requires DNS/traffic failover and is slower. When the priority is speed of rollback after a full release, a full-environment deployment backed by versioned artifacts or snapshots is the most direct approach.

No community discussion yet for this question.