exam questions

Exam Professional Cloud Architect All Questions

View all questions & answers for the Professional Cloud Architect exam

Exam Professional Cloud Architect topic 1 question 112 discussion

Actual exam question from Google's Professional Cloud Architect
Question #: 112
Topic #: 1
[All Professional Cloud Architect Questions]

You are moving an application that uses MySQL from on-premises to Google Cloud. The application will run on Compute Engine and will use Cloud SQL. You want to cut over to the Compute Engine deployment of the application with minimal downtime and no data loss to your customers. You want to migrate the application with minimal modification. You also need to determine the cutover strategy. What should you do?

  • A. 1. Set up Cloud VPN to provide private network connectivity between the Compute Engine application and the on-premises MySQL server. 2. Stop the on-premises application. 3. Create a mysqldump of the on-premises MySQL server. 4. Upload the dump to a Cloud Storage bucket. 5. Import the dump into Cloud SQL. 6. Modify the source code of the application to write queries to both databases and read from its local database. 7. Start the Compute Engine application. 8. Stop the on-premises application.
  • B. 1. Set up Cloud SQL proxy and MySQL proxy. 2. Create a mysqldump of the on-premises MySQL server. 3. Upload the dump to a Cloud Storage bucket. 4. Import the dump into Cloud SQL. 5. Stop the on-premises application. 6. Start the Compute Engine application.
  • C. 1. Set up Cloud VPN to provide private network connectivity between the Compute Engine application and the on-premises MySQL server. 2. Stop the on-premises application. 3. Start the Compute Engine application, configured to read and write to the on-premises MySQL server. 4. Create the replication configuration in Cloud SQL. 5. Configure the source database server to accept connections from the Cloud SQL replica. 6. Finalize the Cloud SQL replica configuration. 7. When replication has been completed, stop the Compute Engine application. 8. Promote the Cloud SQL replica to a standalone instance. 9. Restart the Compute Engine application, configured to read and write to the Cloud SQL standalone instance.
  • D. 1. Stop the on-premises application. 2. Create a mysqldump of the on-premises MySQL server. 3. Upload the dump to a Cloud Storage bucket. 4. Import the dump into Cloud SQL. 5. Start the application on Compute Engine.
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
victory108
Highly Voted 3 years, 3 months ago
C. 1. Set up Cloud VPN to provide private network connectivity between the Compute Engine application and the on-premises MySQL server. 2. Stop the on-premises application. 3. Start the Compute Engine application, configured to read and write to the on-premises MySQL server. 4. Create the replication configuration in Cloud SQL. 5. Configure the source database server to accept connections from the Cloud SQL replica. 6. Finalize the Cloud SQL replica configuration. 7. When replication has been completed, stop the Compute Engine application. 8. Promote the Cloud SQL replica to a standalone instance. 9. Restart the Compute Engine application, configured to read and write to the Cloud SQL standalone instance.
upvoted 33 times
don_v
9 months, 2 weeks ago
Agree with C. The only confusing is step "5. Configure the source database server to accept connections from the Cloud SQL replica." Is that not replication should go in the opposite direction from the on-premise (a.k.a. "source") database to Cloud SQL replica (presuming the latter is configured with a public IP address)?
upvoted 1 times
...
...
kopper2019
Highly Voted 3 years, 3 months ago
Ans C, from this guy muhasinem External replica promotion migration In the migration strategy of external replica promotion, you create an external database replica and synchronize the existing data to that replica. This can happen with minimal downtime to the existing database. When you have a replica database, the two databases have different roles that are referred to in this document as primary and replica. After the data is synchronized, you promote the replica to be the primary in order to move the management layer with minimal impact to database uptime. In Cloud SQL, an easy way to accomplish the external replica promotion is to use the automated migration workflow. This process automates many of the steps that are needed for this type of migration.
upvoted 22 times
...
de1001c
Most Recent 4 months, 3 weeks ago
Selected Answer: C
Minimal downtime. Downtime in A is time to take mysql dump + fix potential failures, not good. Downtime in C is just the time from restart the service.
upvoted 1 times
...
Gino17m
6 months, 1 week ago
Selected Answer: C
I wonder how Examtopics determines the so-called "Correct Answer" ..... C is correct
upvoted 1 times
...
heretolearnazure
1 year, 2 months ago
Answer is C
upvoted 1 times
...
aliounegdiop
1 year, 5 months ago
B is the correct answ
upvoted 2 times
...
BiddlyBdoyng
1 year, 6 months ago
Option A, writing to two databases form the app :( Option C all the way, it also aligns to GCP Data Migration Service.
upvoted 2 times
...
DRK8109
1 year, 6 months ago
mysql dump always causes long downtime.
upvoted 4 times
...
musumusu
1 year, 7 months ago
Correct Answer A C is unnecceory expensive and loss of data at after step 3
upvoted 2 times
...
BeCalm
1 year, 7 months ago
C seems to be the best answer but it is still a bit confusing. So basically there's a bi-directional sync between the 2 databases? Cloud instance is the primary and is writing into the on-prem and on-prem is being replicated into the Cloud.
upvoted 2 times
...
NodummyIQ
1 year, 10 months ago
Option C is not the correct answer because it involves modifying the application to read and write to both the on-premises MySQL server and Cloud SQL, which would involve significant modification to the application and could introduce potential complications or errors. It is generally better to minimize modification to the application when performing a migration. Option D, on the other hand, involves simply importing a mysqldump of the on-premises MySQL server into Cloud SQL and starting the application on Compute Engine, which is a simpler and more straightforward approach that involves minimal modification to the application.
upvoted 2 times
...
SureshbabuK
1 year, 10 months ago
Selected Answer: C
Examtopic providing A as correct answer is causing confusion,
upvoted 6 times
...
Jose56
1 year, 11 months ago
Selected Answer: C
C for minimal downtime
upvoted 2 times
...
megumin
1 year, 11 months ago
Selected Answer: C
C is ok
upvoted 1 times
...
zr79
2 years ago
Answer is C we have a new service https://cloud.google.com/database-migration
upvoted 7 times
...
minmin2020
2 years ago
Selected Answer: C
C because it has minimal modification to the application or database. Also it's easier to fail back to the original solution if the cloud implementation has issues (assuming that there will be a "post-go-live" monitoring period).
upvoted 2 times
...
minmin2020
2 years ago
C because it has minimal modification to the application or database. Also it's easier to fail back to the original solution if the cloud implementation has issues (assuming that there will be a "post-go-live" monitoring period).
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago