Which solution will meet these requirements?
Resize the EC2 instance to an EC2 instance type that has more CPU capacity. Configure an Auto Scaling group with a minimum and maximum size of 1. Configure an RDS read replica for read requests.
Resize the EC2 instance to an EC2 instance type that has more CPU capacity. Configure an Auto Scaling group with a minimum and maximum size of 1. Add an RDS read replica and redirect all read/write traffic to the replica.
Configure an Auto Scaling group with a minimum size of 1 and maximum size of 2. Resize the RDS DB instance to an instance type that has more CPU capacity.
Resize the EC2 instance to an EC2 instance type that has more CPU capacity. Configure an Auto Scaling group with a minimum and maximum size of 1. Resize the RDS DB instance to an instance type that has more CPU capacity.
Explanations:
Resizing the EC2 instance to a larger type provides more CPU capacity, which helps reduce high CPU utilization. Configuring an Auto Scaling group allows for future scaling needs, and adding an RDS read replica improves read request performance by offloading read traffic from the primary RDS instance.
While resizing the EC2 instance and adding an RDS read replica are beneficial, redirecting all read/write traffic to the replica is incorrect. RDS read replicas can only handle read requests; write operations must go to the primary instance. This option misunderstands the architecture.
Configuring an Auto Scaling group with a minimum size of 1 and a maximum size of 2 does not solve the problem of high CPU utilization directly on the EC2 instance since the application is tightly coupled and cannot effectively utilize multiple instances. Additionally, resizing the RDS instance alone may not address the high CPU utilization issue.
Although resizing the EC2 instance and the RDS instance can help alleviate CPU issues, the solution does not include any mechanism to handle read requests specifically, such as using a read replica. Simply resizing instances does not address potential bottlenecks in read performance effectively.
As far as I’m aware, the answer is:
Resize the EC2 instance to an EC2 instance type that has more CPU capacity. Configure an Auto Scaling group with a minimum and maximum size of 1. Configure an RDS read replica for read requests.