Your development team is testing out an application that is being deployed onto AWS Elastic Beanstalk. The application needs to have an RDS Instance provisioned as part of the Elastic Beanstalk setup. They also want to ensure that the database is preserved for analysis even after the environment is torn down. How can you achieve both the requirements? Choose 2 answers from the options given below.

Answer options:

A.Ensure the database is created as part of the Elastic Beanstalk development or testing environment.
B.Ensure that you only choose the MySQL engine type.
C.Ensure that the retention for the database is marked as “Create Snapshot”.
D.Ensure that the retention for the database is marked as “Automated Backup”.

Answer – A and C
The AWS documentation mentions that you should ensure the Retention field is marked as "Create Snapshot" for saving a snapshot before the termination of the environment. This will ensure that we can create a database from the snapshot that is created.
AWS Elastic Beanstalk provides support for running RDS instances in your Elastic Beanstalk environment. This works great for development and testing environments. However, it isn`t ideal for a production environment because it ties the lifecycle of the database instance to the lifecycle of your application`s environment.
Option B is incorrect since it is not necessary that the engine type only has to be MySQL.
Option D is incorrect since the option should be “Create Snapshot”.
For more information on managing a database in Elastic Beanstalk, please refer to the below URL-
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.managing.db.html
Note:
For a production environment, AWS recommends launching a database instance outside of your environment and configure your application to connect to it outside of the functionality provided by Elastic Beanstalk. Using a database instance that is external to your environment requires additional security groups and connection string configuration. However, it also lets you connect to the database from multiple environments, use database types not supported with integrated databases, perform blue/green deployments, and tear down your environment without affecting the database instance.