Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 674 discussion

A: RDS DB instance Autoscaling is not a thing C: You cannot read from standby even if this was done. E: Does not solve any problem Correct answer B: Read replicas distribute load and help improving performance D: Caching of any kind will help with performance Remember: " The database experiences a heavy read load during periods of high traffic."

RDS auto scaling helps capacity issue, not heavy read workload issue.

By creating a read replica, you offload read traffic from the primary DB instance to the replica, distributing the load and improving overall performance during periods of heavy read traffic. Amazon ElastiCache can be used to cache frequently accessed data, reducing the load on the database. This is particularly effective for read-heavy workloads, as it allows the application to retrieve data from the cache rather than making repeated database queries.

i think we need Multi az DB, wtih ElastiCache

Not A - There is no such thing as "auto scaling for a DB instance". There is automatic storage scaling, but storage is not the issue here. B - Yes, read replica will help with "heavy read load" Not C - "send read traffic to the standby DB instance" does not work D - "Configure the application ..." might be a bit simplified, but Elasticache helps with read load Not E - That might have impact on latency, but not on database load; and all instances in same AZ would be against WAF

A and B should be most correct ans

Should be A and B

B. Create a read replica for the DB instance. Configure the application to send read traffic to the read replica. By creating a read replica, you offload read traffic from the primary DB instance to the replica, distributing the load and improving overall performance during periods of heavy read traffic. D. Create an Amazon ElastiCache cluster. Configure the application to cache query results in the ElastiCache cluster. Amazon ElastiCache can be used to cache frequently accessed data, reducing the load on the database. This is particularly effective for read-heavy workloads, as it allows the application to retrieve data from the cache rather than making repeated database queries.