Question #1210
A retail company uses an inventory management system backed by Amazon RDS for MySQL. During peak sales periods, employees execute real-time analytical queries for stock monitoring, causing transaction timeouts in the order fulfillment process. The company wants to resolve the timeouts without restricting employee access to real-time analytics.
Create a read replica. Route analytical queries to the read replica.
Create a read replica. Split the inventory application's read and write operations between the primary DB instance and the read replica.
Migrate the inventory system to Amazon Aurora Serverless with auto-scaling capacity.
Limit analytical queries to predefined intervals during off-peak hours.
Explanation
The correct answer is A. Creating a read replica allows analytical queries to be routed to it, reducing load on the primary RDS instance. This isolates transactional (write) workloads on the primary from read-heavy analytical queries, resolving timeouts without restricting real-time access.
Why other options are incorrect:
- B: Splitting read/write operations may not specifically address ad-hoc analytical queries from employees, which are likely outside the application's normal read traffic.
- C: Migrating to Aurora Serverless adds complexity and does not directly resolve contention between transactional and analytical workloads.
- D: Limiting queries to off-peak hours violates the requirement for real-time analytics.
Key Points:
1. Read replicas handle read traffic, reducing primary DB load.
2. Real-time analytics require near-up-to-date data, achievable via asynchronous replication.
3. Separating workloads prevents resource contention.
Answer
The correct answer is: A