Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Google Cloud Certified Professional Cloud Database Engineer · Google Cloud
Select 2 answers.
This question asks for 2 answers, but our data marks only 1. Compare with the community discussion below for the full answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
The two main issues at hand are replication lag and slow report performance. While option B, creating additional read replicas, could address the load issue, it would require changes to the current reports, which is not desirable. Instead, option A, implementing secondary indexes in Cloud SQL, could enhance report speed without altering the reports. As for the replication lag, option C suggests enabling parallel replication in Cloud SQL, which is a plausible solution. To do that you disable replication on the replica (not the primary), set flags on the replica and optionally set flags on the primary instance to optimize performance for parallel replication. Therefore, considering the constraints and the context, options A and C are the most suitable choices.
B - Addresses performance improvements: Reduce the burden on the primary instance by offloading replication work to multiple read replicas. https://cloud.google.com/sql/docs/mysql/replication#cascading-replicas C- Addresses lag time because Parallel replication reduces replication lag by increasing the number of SQL threads that work to execute these transactions. https://cloud.google.com/sql/docs/mysql/replication/manage-replicas#configuring-parallel-replication
Just got this question and there is no A, and it is not 'choose two' but one answer only.