Which combination of steps will meet these requirements?
(Choose three.)
Deploy the application on AWS Elastic Beanstalk. Deploy an Amazon RDS for MySQL DB instance as part of the Elastic Beanstalk configuration.
Deploy the application on AWS Elastic Beanstalk. Deploy a separate Amazon RDS for MySQL DB instance outside of Elastic Beanstalk.
Configure a notification email address that alerts the application team in the AWS Elastic Beanstalk configuration.
Configure an Amazon EventBridge rule to monitor AWS Health events. Use an Amazon Simple Notification Service (Amazon SNS) topic as a target to alert the application team.
Use the immutable deployment method to deploy new application versions.
Use the rolling deployment method to deploy new application versions.
Explanations:
Deploying the RDS instance as part of the Elastic Beanstalk configuration will not provide persistence beyond the lifecycle of the application environment. RDS should be managed independently for high availability and persistence.
Deploying the application on Elastic Beanstalk and a separate RDS instance for MySQL outside of Elastic Beanstalk ensures that the database remains persistent and can be managed for high availability.
Configuring an email address in the Elastic Beanstalk configuration ensures that alerts are sent to the application team when deployment fails.
Monitoring AWS Health events through EventBridge and SNS notifications would provide alerts for AWS-wide issues but is not directly related to Elastic Beanstalk deployment failures.
Using the immutable deployment method ensures that any issues with the new application version trigger automatic rollbacks, maintaining application stability.
Rolling deployment only replaces parts of the environment incrementally, which does not fully meet the automatic rollback requirement and is less reliable than immutable deployments for handling failure.