AWS Certified Developer – Associate (DVA-C02) — Question 457
An application interacts with Amazon Aurora to store and track customer information. The primary database is set up with multiple read replicas for improving the performance of the read queries. However, one of the Aurora replicas is receiving most or all of the traffic, while the other Aurora replica remains idle.
How can this issue be resolved?
Answer options
- A. Disable application-level DNS caching.
- B. Enable application-level DNS caching.
- C. Enable application pooling
- D. Disable application pooling
Correct answer: A
Explanation
When application-level DNS caching is enabled, the application resolves the Aurora reader endpoint to a single IP address and caches it, routing all subsequent traffic to that specific replica. Disabling this caching ensures that the application frequently queries DNS, allowing the load-balanced reader endpoint to distribute traffic evenly across all available replicas. Connection pooling does not resolve this DNS stickiness issue.