A company is refactoring a monolithic application into a modern design on AWS. The CI/CD pipeline must: allow multiple releases per hour, and enable rapid rollbacks. Which deployment design meets these requirements?

This option describes a blue/green deployment strategy using Elastic Beanstalk's environment swapping feature. This approach allows for zero-downtime deployments and rapid rollbacks by simply swapping the CNAMEs of the old and new environments. If issues arise, swapping back to the old environment is quick and easy, meeting the "rapid rollbacks" requirement. The other options are less suitable: Replacing EC2 instances with new AMIs can cause downtime during the replacement process and rollbacks are slower as new instances need to be launched. Reprovisioning infrastructure with Systems Manager and updating user data is a more complex and potentially slower deployment method, making rapid rollbacks difficult. Deploying updates via Auto Scaling with prebuilt AMIs is a rolling update strategy. While it minimizes downtime, rolling back requires another rolling update, which is not as fast as a CNAME swap.