AWS Certified SysOps Administrator – Associate (legacy) — Question 410

Your business is building a new application that will store its entire customer database on a RDS MySQL database, and will have various applications and users that will query that data for different purposes.
Large analytics jobs on the database are likely to cause other applications to not be able to get the query results they need to, before time out. Also, as your data grows, these analytics jobs will start to take more time, increasing the negative effect on the other applications.
How do you solve the contention issues between these different workloads on the same data?

Answer options

• A. Enable Multi-AZ mode on the RDS instance
• B. Use ElastiCache to offload the analytics job data
• C. Create RDS Read-Replicas for the analytics work
• D. Run the RDS instance on the largest size possible

Correct answer: C

Explanation

Creating RDS Read Replicas is the ideal solution because it offloads read-heavy analytical queries from the primary database instance, effectively eliminating resource contention. Multi-AZ deployments are designed for high availability and disaster recovery rather than scaling read traffic, as the standby instance cannot accept active read traffic. Scaling the instance size or using ElastiCache are less effective and cost-efficient for isolating long-running, complex analytical queries.