A gaming company deploys a web portal using Elastic Beanstalk and sometimes releases updates three or four times per day. The company wants to deliver new features to all users quickly while minimizing user impact and maximizing availability. Which Elastic Beanstalk deployment policy best meets these goals?

An immutable deployment policy creates a new, separate Auto Scaling group for the updated application version. Once the new instances pass health checks, traffic is shifted to them, and the old instances are terminated. This approach ensures zero downtime, easy rollback if issues arise (by simply terminating the new instances), and prevents issues from partially updated instances, which is crucial for frequent updates and minimizing user impact. Rolling deployments update instances in batches, which can cause downtime or performance degradation during the update and makes rollbacks more complex. All-at-once deployments update all instances simultaneously, leading to significant downtime. Canary deployments are a good strategy for testing, but immutable deployments are better for rapid, low-risk full-scale releases as they provide a cleaner cutover and rollback mechanism.