Which solution will meet these requirements?
Create an Amazon RDS Proxy. Assign the proxy to the DB instance.
Create a read replica for the DB instance. Move the read traffic to the read replica.
Enable Performance Insights. Monitor the CPU load to identify the timeouts.
Take regular automatic snapshots. Copy the automatic snapshots to multiple AWS Regions.
Explanations:
Creating an Amazon RDS Proxy helps manage database connections efficiently, reducing the impact of failovers by maintaining a persistent connection pool. This can minimize the application timeouts experienced during failover events by quickly rerouting requests to the standby instance.
While creating a read replica can offload read traffic from the primary instance, it does not address the issue of failover times for write operations or application timeouts. The primary instance still needs to fail over to the standby, which can take time.
Enabling Performance Insights helps monitor database performance but does not provide a solution for reducing failover time. It can identify performance issues but does not actively mitigate them during a failover.
Taking regular automatic snapshots and copying them to multiple regions helps with disaster recovery and data protection, but it does not reduce failover time. Snapshots are not useful for immediate failover scenarios and do not address the application’s resilience during database outages.
I chart that the answer is:
Create an Amazon RDS Proxy. Assign the proxy to the DB instance.
Based on what I know, the answer is:
Create an Amazon RDS Proxy. Assign the proxy to the DB instance.