Which solution will meet these requirements?
Configure an Amazon ElastiCache cluster in front of the RDS instance. Update the reporting job to query the ElastiCache cluster.
Deploy an RDS read replica. Update the reporting job to query the reader endpoint.
Create an Amazon CloudFront distribution. Set the RDS instance as the origin. Update the reporting job to query the CloudFront distribution.
Increase the size of the RDS instance.
Explanations:
ElastiCache is designed to cache data for faster access, but it is not ideal for handling complex queries or reporting jobs that need to extract data from a relational database.
Deploying a read replica will offload read traffic from the primary RDS instance, improving performance for the reporting job by querying the replica. This solution enhances both performance and availability.
Amazon CloudFront is a content delivery network (CDN) that caches static content, not for dynamic database queries. It cannot be used to optimize the performance of RDS.
Increasing the RDS instance size may help to some extent, but it does not address the issue of high read IOPS and does not improve performance for read-heavy workloads like reporting jobs.
I assess that the answer is:
Deploy an RDS read replica. Update the reporting job to query the reader endpoint.