Which set of steps should the solutions architect take?
Create an Auto Scaling group for the front end with a combination of On-Demand and Spot Instances to reduce costs. Convert the Oracle database into a single Amazon RDS reserved DB instance.
Create an Auto Scaling group for the front end with a combination of On-Demand and Spot Instances to reduce costs. Create two additional copies of the database instance, then distribute the databases in separate AZs.
Create an Auto Scaling group for the front end with a combination of On-Demand and Spot Instances to reduce costs. Convert the tables in the Oracle database into Amazon DynamoDB tables.
Convert the On-Demand Instances into Spot instances to reduce costs for the front end. Convert the tables in the Oracle database into Amazon DynamoDB tables.
Explanations:
While creating an Auto Scaling group for the front end improves scalability, converting the Oracle database into a single Amazon RDS reserved instance does not eliminate licensing costs or significantly enhance reliability. It still incurs licensing fees and does not address concurrency limitations.
Creating an Auto Scaling group for the front end is beneficial, but simply creating additional copies of the Oracle database instance does not eliminate licensing costs and can complicate data management. Moreover, it doesn’t fully address the need for increased concurrency or reliability.
This option addresses scalability by creating an Auto Scaling group for the front end, and using a combination of On-Demand and Spot Instances reduces costs. Migrating from Oracle to Amazon DynamoDB eliminates licensing costs and improves reliability and concurrency due to DynamoDB’s managed, highly available, and scalable nature.
Converting On-Demand Instances to Spot Instances may reduce costs but does not address scalability and reliability effectively. While moving to Amazon DynamoDB eliminates licensing costs, it does not provide a full solution for the scalability and concurrency issues faced by the application.