What should the solutions architect do to separate the read requests from the write requests?
Enable read-through caching on the Amazon Aurora database.
Update the application to read from the Multi-AZ standby instance.
Create a read replica and modify the application to use the appropriate endpoint.
Create a second Amazon Aurora database and link it to the primary database as a read replica.
Explanations:
Enabling read-through caching does not effectively separate read requests from write requests; it may reduce I/O but won’t address the latency issue directly related to database reads.
Reading from a Multi-AZ standby instance is not a recommended practice, as standby instances are meant for failover, not for load balancing read requests. This approach does not alleviate the latency on write requests.
Creating a read replica allows for read requests to be directed to the replica, thus separating them from write requests going to the primary instance, which helps reduce latency and I/O contention.
Creating a second Aurora database linked as a read replica is unnecessary and adds complexity. A read replica of the existing database is sufficient for separating read from write requests.
To the best of my knowledge, the answer is:
Create a read replica and modify the application to use the appropriate endpoint.
I rate that the answer is:
Create a read replica and modify the application to use the appropriate endpoint.