Exam SAA-C03 All QuestionsBrowse all questions from this exam
Question 90

A company is using a SQL database to store movie data that is publicly accessible. The database runs on an Amazon RDS Single-AZ DB instance. A script runs queries at random intervals each day to record the number of new movies that have been added to the database. The script must report a final total during business hours.

The company's development team notices that the database performance is inadequate for development tasks when the script is running. A solutions architect must recommend a solution to resolve this issue.

Which solution will meet this requirement with the LEAST operational overhead?

    Correct Answer: B

    Creating a read replica of the database will distribute the load by allowing the script to query the read replica instead of the primary database. This improves performance without affecting the primary database, which is used for development tasks. It also meets the requirement of having the least operational overhead, as managing a read replica is straightforward compared to other solutions like manual exports or setting up a caching layer.

Discussion
alvarez100Option: B

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

Gil80Option: 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.

NitiATOS

I will support this by point to the question : " with the LEAST operational overhead?" Configuring the read replica is much easier than configuring and integrating new service.

slimenOption: B

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

cookieMrOption: B

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.

MehulKapadiaOption: B

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.

awsgeek75Option: B

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.

bujumanOption: A

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

smdrouissOption: A

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

pentium75

Doesn't it become a multi-instance DB when you add a read replica? A can't be because you can't read from the passive replica of a multi-AZ DB.

tom_cruiseOption: B

This is what we do in the real world.

joshikOption: B

- 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.

underdogpexOption: B

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.

Router

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

effiecancode

Actualy you can

TariqKipkemeiOption: B

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

Guru4CloudOption: B

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

MostafaWardanyOption: B

For LEAST operational overhead, I recommended to use read replica DB

BmarodiOption: B

The option B will reduce burden on DB, becase the script will read only from replica, not from DB, hence option B is correct answer.

Siva007Option: B

B is correct. Read replica for read only script any analytical loads.