A DevOps engineer will deploy a Ruby application that needs to connect to an RDS for MySQL database, scale automatically, be highly available, preserve its data across application stack changes, support automated deployments with automatic rollback, and alert the team when a deployment fails. Which combination of steps meets these requirements? (Choose three.)

Deploying the application to Elastic Beanstalk (EB) and provisioning a separate RDS instance ensures the database persists independently, even if the EB environment is terminated. This addresses the requirement to preserve data across application stack changes. Configuring an email notification in the EB environment directly addresses the need to alert the team on deployment failures. Using the immutable deployment strategy for new application versions ensures automatic rollback in case of deployment issues, as new instances are launched with the new version and traffic is only shifted after they pass health checks. Incorrect options: Creating the RDS instance as part of the EB environment configuration would lead to data loss if the environment is terminated. An EventBridge rule for AWS Health events is for infrastructure health, not application deployment failures. The rolling deployment strategy does not provide automatic rollback in the same robust way as immutable deployments, which launch an entirely new set of instances before switching traffic.