An operations team deploys multi-agent solutions across DTAP environments and needs a production cutover strategy that can reverse a bad agent package within minutes if health probes fail. Which approach best meets that requirement?
Select an answer to reveal the explanation.
Short Explanation
Blue/green deployment slots keep last-known-good agent packages warm, so you can flip traffic back in minutes when health probes fail. Overwriting production and restoring old tape is too slow, and rebuilding a region is disaster recovery, not rapid rollback.
Full Explanation
Blue/green deployment slots, or equivalent parallel environments, are correct because multi-agent deployment skills include blue/green and rollback strategies as part of multi-environment release design. Parallel production environments or slots enable rapid traffic switchback when health or quality probes fail after promoting an agent package.
The approach that overwrites the only production deployment in place and restores from a week-old backup tape is incorrect because in-place overwrite destroys easy reversion, and week-old backups are too stale and slow for minute-level rollback.
The approach that requires a full regional rebuild from scratch for every rollback is incorrect because full regional rebuilds are high RTO and unsuitable as the primary rollback path for a bad agent package.
The approach that keeps production configuration only on a whiteboard in the operations room is incorrect because undocumented, non-versioned configuration cannot support reliable automated rollback.