MemberFebruary 3, 2023 at 8:42 am
> The option that says: Reduce the load on the database tier by creating multiple read replicas for the Amazon RDS MySQL Multi-AZ cluster. Configure the web application to use the single reader endpoint of RDS for all read operations is incorrect. Creating read replicas is recommended to increase the read performance of an RDS cluster. However, the Amazon RDS MySQL does not have a single reader endpoint for read replicas. You must use Amazon Aurora for MySQL to support this.
AWS has introduced RDS clusters for MySQL. The cluster does have a reader endpoint. Above you specifically say “Amazon RDS MySQL Multi-AZ cluster” – so this answer is correct
> A Multi-AZ DB cluster has three DB instances instead of a single DB instance. Each connection is handled by a specific DB instance. When you connect to a Multi-AZ DB cluster, the host name and port that you specify point to a fully qualified domain name called an endpoint. The Multi-AZ DB cluster uses the endpoint mechanism to abstract these connections. Thus, you don’t have to hardcode all the host names or write your own logic for rerouting connections when some DB instances aren’t available.
> The writer endpoint connects to the writer DB instance of the DB cluster, which supports both read and write operations. The reader endpoint connects to either of the two reader DB instances, which support only read operations.
MemberFebruary 5, 2023 at 5:59 pm
Thanks for the feedback.
We will review the option and will update the explanation accordingly.
However, the answer will still be the same.
The goal of the question is to reduce the load on the database by reducing the number of queries going to the database.
That’s why the Route 53 option with a dummy web page and ElastiCache cluster options are chosen because they relieve the database of unnecessary and repetitive queries.
Hope this helps.
Let us know if you need further assistance. The Tutorials Dojo team is dedicated to helping you pass your AWS exam!
Kenneth Samonte @ Tutorials Dojo
Log in to reply.