Topic 1 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?
Modify the DB instance to be a Multi-AZ deployment.
Create a read replica of the database. Configure the script to query only the read replica.
Instruct the development team to manually export the entries in the database at the end of each day.
Use Amazon ElastiCache to cache the common queries that the script runs against the database.
ユーザの投票
コメント(17)
- 正解だと思う選択肢: B
Elasti Cache if for reading common results. The script is looking for new movies added. Read replica would be the best choice.
👍 22alvarez1002022/10/16 - 正解だと思う選択肢: 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:
- Your data is slow or expensive to get when compared to cache retrieval.
- Users access your data often.
- 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.
👍 10Gil802022/11/07 - 正解だと思う選択肢: B
CORRECT The best solution to meet the requirement with the least operational overhead would be to create a read replica of the database and configure the script to query only the read replica. Option B.
A read replica is a fully managed database that is kept in sync with the primary database. Read replicas allow you to scale out read-heavy workloads by distributing read queries across multiple databases. This can help improve the performance of the database and reduce the impact on the primary database.
By configuring the script to query the read replica, the development team can continue to use the primary database for development tasks, while the script's queries will be directed to the read replica. This will reduce the load on the primary database and improve its performance.
👍 6Buruguduystunstugudunstuy2022/12/20
シャッフルモード