Explanation:
Reporting workloads are typically read-heavy. In an Amazon Aurora cluster, you can add a reader instance to offload read traffic from the writer instance. By directing the weekly automated report to a reader instance, the primary writer instance remains available and performant for the web application's frontend users. Option C is incorrect because Aurora clusters only have one writer instance (unless using Multi-Master, which is not the standard solution for this scenario).
Ultimate access to all questions.
Question 19: Users of a company's internal web application recently experienced application performance issues for a brief period. The application includes frontend web servers that run in an Amazon Elastic Kubernetes Service (Amazon EKS) cluster. The application also includes a backend Amazon Aurora PostgreSQL DB cluster that includes one DB instance.
A SysOps administrator determines that the source of the performance issues was high utilization of the DB cluster. The single writer instance experienced more than 90% utilization for 11 minutes. The cause of the high utilization was an automated report that is scheduled to run one time each week.
What should the SysOps administrator do to ensure that users do not experience performance issues each week when the report runs?
A
Increase the size of the DB instance. Monitor the performance during the next scheduled run of the report.
B
Add a reader instance. Change the database connection string of the report application to use the newly created reader instance.
C
Add another writer instance. Change the database connection string of the report application to use the newly created writer instance.
D
Configure auto scaling for the DB cluster. Set the minimum capacity units, maximum capacity units, and target utilization.
E
N/A
F
N/A
No comments yet.