A weekday release for a multi-instance Elastic Beanstalk permitting site must replace instances gradually while keeping enough capacity online. Which strategy fits that platform constraint?
Select an answer to reveal the explanation.
Short Explanation
Rolling is swapping tires while the bus keeps rolling—batches out, batches in, seats still available for permit applicants. Flattening the whole Auto Scaling group at lunch is how you invent an outage.
Full Explanation
Rolling deployments replace instances in controlled batches so the service retains capacity throughout the update, which fits Elastic Beanstalk and EC2 Auto Scaling weekday releases. Full-fleet termination or unrelated Lambda canary settings do not match a multi-instance Beanstalk rolling requirement.