SAP-C02 Question 295
Single answerA media streaming company is experiencing performance issues with their application. The application uses an Amazon RDS MySQL database for storing metadata and an Amazon S3 bucket for storing media files. Users report slow response times when accessing the application, especially during peak hours. After analyzing the workload, you identify that the database is facing high read traffic due to frequent metadata lookups. Which solution should you implement to meet the performance objectives?
- A
Enable Amazon RDS read replicas and distribute the read traffic across replicas.
- B
Migrate the database to Amazon Aurora for better performance and scalability.
- C
Enable Amazon ElastiCache as a caching layer for frequently accessed metadata.
- D
Store the metadata in Amazon S3 instead of Amazon RDS to reduce database load.
Show answer and explanation
Correct answer: C
Explanation
The application is experiencing performance issues due to high read traffic on the database. Using Amazon ElastiCache as a caching layer is the most effective solution in this scenario as it reduces the load on the database by serving frequently accessed metadata from the cache, thereby improving response times.
- A. Incorrect.
This is a valid option to improve performance by offloading read traffic to read replicas, but it might not fully address the performance objectives for high-frequency lookups. Caching is a better fit for frequently accessed data.
- B. Incorrect.
Migrating to Amazon Aurora can improve performance, but it does not directly address the issue of high read traffic. It also involves significant effort and might not be the most efficient solution for the specific problem.
- C. Correct.
Using Amazon ElastiCache as a caching layer can significantly reduce database load for frequently accessed metadata. This is an optimal solution to meet performance objectives in this scenario.
- D. Incorrect.
Storing metadata in Amazon S3 is not suitable for this use case because S3 is designed for object storage and not for real-time queryable data. This would likely worsen performance.