You are deploying a web application with AWS Elastic Beanstalk and need deployments that always keep the previous capacity fully available while the new version deploys. Which Elastic Beanstalk deployment policies meet this requirement? (Choose two.)

Immutable deployments launch a new, separate Auto Scaling group for the new application version. Once the new environment passes health checks, traffic is switched, and the old environment is terminated. This ensures the previous capacity remains fully available throughout the deployment. Rolling with additional batch deployments launch a new batch of instances for the new application version alongside the existing instances. This increases the total capacity temporarily during the deployment, ensuring the previous capacity is maintained until the new instances are healthy and ready to take traffic. "All at once" deployments update all instances simultaneously, causing downtime. "Rolling" deployments update instances in batches, but each batch of old instances is taken out of service before new ones are launched, reducing available capacity. "Rebuild" is not a standard Elastic Beanstalk deployment policy; it typically refers to recreating the entire environment, which would cause downtime.