Rollback must be near-instant after a bad release without rebuilding every server from scratch. Which strategy best supports that requirement?
Select an answer to reveal the explanation.
Short Explanation
When you need an undo button that works in seconds, keep the old stage warm and just flip the lights back — that is blue-green. Rebuilding every server from scratch is the long way home. Near-instant rollback without a full rebuild points straight at traffic-switch blue-green.
Full Explanation
Blue-green keeps the previous environment available so rollback is primarily a traffic redirection rather than a time-consuming rebuild or package rollback across the live fleet. In-place reversions and image rebuilds take longer and increase risk during an incident. Load-balancer deletion or DNS TTL tricks are not controlled deployment rollback mechanisms.