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

Elasti Cache if for reading common results. The script is looking for new movies added. Read replica would be the best choice.

• You have a production DB that is taking on a normal load • You want to run a reporting application to run some analytics • You create a read replica to run the new workload there • The prod application is unaffected • Read replicas are used for SELECT (=read) only kind of statements Therefore I believe B to be the better answer. As for "D" - ElastiCache use cases are: 1. Your data is slow or expensive to get when compared to cache retrieval. 2. Users access your data often. 3. Your data stays relatively the same, or if it changes quickly staleness is not a large issue. 1 - Somewhat true. 2 - Not true for our case. 3 - Also not true. The data changes throughout the day. For my understanding, caching has to do with millisecond results, high-performance reads. These are not the issues mentioned in the questions, therefore B.

Read replicas are replications of original databases and are the most suitable option for running scripts here.

Ans B - as per Gil80 (1 year, 10mth ago) "Selected Answer: B • You have a production DB that is taking on a normal load • You want to run a reporting application to run some analytics • You create a read replica to run the new workload there • The prod application is unaffected • Read replicas are used for SELECT (=read) only kind of statements Therefore I believe B to be the better answer. As for "D" - ElastiCache use cases are: 1. Your data is slow or expensive to get when compared to cache retrieval. 2. Users access your data often. 3. Your data stays relatively the same, or if it changes quickly staleness is not a large issue. 1 - Somewhat true. 2 - Not true for our case. 3 - Also not true. The data changes throughout the day. For my understanding, caching has to do with millisecond results, high-performance reads. These are not the issues mentioned in the questions, therefore B."

option B for sure, read replica is designed for this very use case, improving performance, on the other hand, enabling multi-AZ improves availability and not performance.

A. Having multi-AZ database would increase availability, bu not performance. C. Not practical. Huge Operational Overhead. (Solution should be LEAST operational overhead) D. Good for fixed queries with fixed results. not a good fit in this case as script is looking for new results in DB. It has to scan the database. Correct Answer B. Read replica ensure you have dedicated read instance with its own resources.

Just read from read replica. A: This will make it HA but won't solve any problems C: We want an AWS solution not change the development team's ways of working D: Elasticache is cache of read queries when data doesn't change. It's useless for finding new data.

Answer C is inconcevable according to LEAST operational overhead? We will exclude answer D because question is about RDS databases and ElastiCache is not. Between answers A and B , A is the most appropriate answer due to 2 foolowing points: - Possible to transfrom a Single-AZ RDS to Multi-AZ - LEAST operational overhead

It is A , because the scenario mention "single db instance" which is not possible to enable read replica

lol seriously the person who wrote the answer wants us to fail

This is what we do in the real world.

- Cached data might not always be up-to-date, so you need to manage cache expiry and invalidation carefully. - It may require some code changes to implement caching logic in your script. - ElastiCache comes with additional costs, so you should assess the cost implications based on your usage.

Why not D: While ElastiCache can be relatively easy to set up, it still requires ongoing management, monitoring, and potentially scaling as the dataset and query load grow. This introduces operational overhead that may not align with the goal of minimizing operational work.

the correct answer should be A, you can't create a read replica on a single-AZ DB instance

a read replica is always fit for these type of scenarios.

The key requirements are: The script must report a final total during business hours Resolve the issue of inadequate database performance for development tasks when the script is running With the least operational overhead

A. Modifying the DB to be a Multi-AZ deployment improves high availability and fault tolerance but does not directly address the performance issue during the script execution. C. Instructing the development team to manually export the entries in the database introduces manual effort and is not a scalable or efficient solution. D. While using ElastiCache for caching can improve read performance for common queries, it may not be the most suitable solution for the scenario described. Caching is effective for reducing the load on the database for frequently accessed data, but it may not directly address the performance issue during the script execution. Creating a read replica of the database (option B) provides a scalable solution that offloads read traffic from the primary database. The script can be configured to query the read replica, reducing the impact on the primary database during the script execution.