Exam Professional Cloud Database Engineer topic 1 question 27 discussion

C. D is nonsense, so can be eliminated. The question tells us we’re already managing BOTH sets of MySQL instances, one on prem and the other in GCE. The question also says an objective is to offload part of the management. That can only mean leverage a managed service. The Data(base) Migration Service is a managed service used to instantiate a new migrated DB in Cloud SQL (or AlloyDB for PostgreSQL but that’s not in scope here). The question isn’t asking about database migration, so we can eliminate B. A could be used to create replicas, but doesn’t help with offloading management operations. That leaves C which does use a managed service which could be leveraged to create replicas.

https://cloud.google.com/sql/docs/mysql/replication#external-read-replicas https://cloud.google.com/sql/docs/mysql/replication#replication_use_cases

External replica is for scaling read

https://cloud.google.com/sql/docs/mysql/replication/external-

C. MySQL external replica are best for create replicas to sclae reads and offload

C is the answer as Question mentions offload part of the management operation

it's c

The ans is C

A is correct - se external server replication -==> This option allows you to set up replication between your on-premises MySQL server (in your data center) and a MySQL server running on GOOGLE CLOUD COMPUTE ENGINE.

By using external server replication, you can set up and manage replication between your on-premises MySQL database and a replica instance in Google Cloud. This enables you to scale reads, offload management operations, and distribute the workload between your data center and Google Cloud, providing the desired benefits in a hybrid configuration.

Agree with B. - Multi-cloud continuous replication Much like the read replicas across regions, if data exists in another cloud provider, a migration job can be set up which continuously replicates the database <<into Google Cloud for multi-cloud read-availability>>. Database Migration Service doesn't support a dual-write scenario, that is writing to and reading from both the source and destination. https://cloud.google.com/database-migration/docs/overview#use_cases

offload part of the management operation => cloud sql => C

A. Use external server replication. https://cloud.google.com/sql/docs/mysql/replication/external-server#config-description

A A: CORRECT. External server replication meant to serve the case as the question describe: DC -> GSQL. B: WRONG. DMS intends for one time migration + CDC but does not mean to serve as primary + replica fashion. The replica is not ready to serve the traffic. C: WRONG. Cloud SQL for MySQL external replica meant to serve the replica is outside of Google cloud, which means GSQL -> GSQL or GSQL -> DC. D: WRONG. This option is for one time only. Reference: https://cloud.google.com/sql/docs/mysql/replication/external-server https://cloud.google.com/sql/docs/mysql/replication https://cloud.google.com/database-migration/docs/overview#use_cases

I strongly believe it is A. Since the database is already in your datacenter. So you need to replicate your datacenter database to cloud to offload management. External Server Replication will replicate your database on to cloud sql. https://cloud.google.com/sql/docs/mysql/replication/external-server

C: https://cloud.google.com/sql/docs/mysql/replication

C: Use Cloud SQL for MySQL external replica.