A legacy Elastic Beanstalk civic app must move toward containers with an upgrade path that stages features and supports rollback. Which approach best fits?
Select an answer to reveal the explanation.
Short Explanation
Do not yank the Beanstalk rug. Ease into containers with feature flags so you can turn a risky feature off and roll back—citizens should not notice the renovation dust.
Full Explanation
Application upgrade paths for new platforms should be incremental: feature flags and rollback-capable deployments reduce blast radius versus irreversible cutovers. Abrupt deletion, unmanaged pets without pipelines, and removing version control undermine controlled modernization.