Read-heavy catalog queries are overwhelming the primary Amazon RDS database for a city services directory. Writes remain modest. How should the architect scale reads?
Select an answer to reveal the explanation.
Short Explanation
When everyone is browsing the catalog, give them read replicas and keep the primary for writes. Shrinking the primary or deleting indexes makes the traffic jam worse, not better.
Full Explanation
RDS and Aurora read replicas offload read traffic from the primary, which is appropriate when reads dominate and writes stay modest. Removing indexes, undersizing the primary while keeping all reads there, or collapsing to a single AZ does not scale read capacity.