An application runs on AWS Elastic Beanstalk. You must deploy updates without any downtime and route a specific percentage of incoming traffic to the new version during an evaluation period. Which Elastic Beanstalk deployment policy accomplishes this?

Traffic-splitting deployments allow you to deploy a new version of your application to a separate set of instances and then gradually shift a percentage of incoming traffic from the old version to the new version. This enables A/B testing or canary releases, where you can monitor the new version's performance with a small portion of users before fully committing. If issues arise, you can easily roll back by shifting traffic back to the old version. Rolling deployments update instances in batches, which can cause brief periods of reduced capacity or downtime during updates, and don't allow for traffic shifting. In-place deployments update the application directly on existing instances, leading to downtime. Immutable deployments launch a completely new set of instances with the new version and then swap DNS, which provides zero-downtime but doesn't offer the granular traffic routing for evaluation.