A company migrated a monolithic application to a single Amazon EC2 instance and Amazon RDS. The application modules are tightly coupled so the app runs on only one EC2 instance. The EC2 instance experiences high CPU utilization during peak times, and RDS read performance degrades. The company wants to reduce EC2 CPU usage and improve RDS read performance. Which solution meets these requirements?

The correct solution addresses both high EC2 CPU utilization and degraded RDS read performance. Resizing the EC2 instance to one with more CPU capacity directly mitigates the high CPU usage of the monolithic application. Configuring an Auto Scaling group with a minimum and maximum size of 1 ensures the instance is always running and can be managed by ASG features like health checks, even if scaling isn't needed for this monolithic app. Adding an RDS read replica and directing read requests to it offloads the primary RDS instance, improving its performance and reducing the overall load, which can indirectly benefit the EC2 instance by speeding up database interactions. Incorrect options: Redirecting all read/write traffic to an RDS read replica is incorrect because read replicas are designed for reads only; writes must go to the primary instance. Resizing the RDS DB instance to one with more CPU capacity might help, but it doesn't solve the EC2 CPU issue and isn't as effective for read performance as a read replica. An ASG with a max size of 2 won't help a monolithic app that runs on only one instance. Resizing both EC2 and RDS to more CPU capacity is an option, but it doesn't leverage the read replica for improved read performance, which is a key requirement.