Your company has developed an operations system for an e-commerce organization having multiple offices across the country. The operations team pushes the new changes to the production frequently. The product uses AWS RDS Multi-AZ MySQL with read-replicas. The web application is running on EC2 with ELB in front. The last feature update created an issue with the database, and part of the system is down due to that. The development team has rolled out a couple of more patches to fix the issue. But some users are still facing the outages. The management has finally decided to roll back the update to the last known stable version until all the issues are resolved in the QA environment. Which of the following options is the most suitable to perform the rollback cost-efficiently?

Answer options:

A.Use the DB snapshot with Point-in-time recovery to rollback the database, and rollback the EC2 servers with a previously working AMI.
B.Create a totally new environment with the last known stable build. Use the Route53 Weighted policy to redirect the traffic to the new environment. Delete the old environment.
C.Use the DB snapshot with Point-in-time recovery and restore on top of the original database.
D.Create a CloudFormation template with RollingUpdate policy to create a new frontend and change the Route53 record to redirect traffic to the new frontend with the existing database.

Correct Answer: A
Option A is CORRECT because point-in-time recovery helps to recover the database to a certain point in time. The EC2 servers can be recovered with the previous AMI.
Option B is INCORRECT because this method is not cost-efficient as a new set of resources need to be configured.
Option C is INCORRECT because it does not mention how to roll back the application.
Option D is INCORRECT because the database problem is still there, and the traffic still goes to the existing problematic database.