DVA-C02 Elastic Beanstalk-managed RDS Practice Question

• ✓ A.Create a standalone Amazon RDS instance and reconfigure the application to use it instead of the in-environment database.
• B.Take a snapshot of the database before each deployment and restore it after the deployment completes.
• C.Use the Elastic Beanstalk environment's 'Swap environment URLs' feature to perform a blue/green deployment.
• D.Create a new Elastic Beanstalk environment with a new RDS instance and migrate data manually.

Why A: Decoupling the RDS database from the Elastic Beanstalk environment by creating a standalone RDS instance ensures that the database is not tied to the environment's lifecycle. In-environment databases are automatically deleted when the environment is terminated or updated, risking data loss. By reconfiguring the application to point to an external RDS instance, the database persists independently of environment operations, meeting the requirement to avoid data loss during code updates or environment changes.

• A.Update the application code directly on the EC2 instances without redeploying the environment.
• B.Create a new environment configuration, update the code, and swap the CNAME of the environments.
• ✓ C.Decouple the database from the Elastic Beanstalk environment by creating a separate RDS instance and connecting the application to it externally.
• D.Use Elastic Beanstalk's platform updates while keeping the database attached to the environment.

Why C: When an RDS instance is included in an Elastic Beanstalk environment, it is tied to the environment's lifecycle. If the environment is terminated or rebuilt, the database is also deleted. Decoupling the database by creating a standalone RDS instance and connecting the application to it externally ensures the database persists independently of application deployments, allowing code updates without risking data loss.