A citizen payments API must support instant rollback if a new release fails health checks. Which deployment strategy best meets that requirement?
Select an answer to reveal the explanation.
Short Explanation
Blue/green keeps the old city hall open while the new wing gets inspected. If the new release fails its health check, flip citizens back to the old door—no rebuild-from-scratch panic.
Full Explanation
Blue/green deployments maintain a parallel environment so rollback is a traffic shift to the last known-good version when health checks fail—appropriate for high-risk citizen payment APIs. All-at-once without a retained environment lengthens rollback. Manual FTP and disabled health checks are unsafe operational practices for production payment workloads.