关于“Migrate MySQL Data to Cloud SQL using Database Migration Service: Challenge Lab”的评价

lab issues when migration job / connection profiles names are different than source/target instances

Oskar K. · 已于 over 2 years前审核

quite hard

Dodzi A. · 已于 over 2 years前审核

Mariana A. · 已于 over 2 years前审核

Anrie S. · 已于 over 2 years前审核

Vinicius S. · 已于 over 2 years前审核

Felipe S. · 已于 over 2 years前审核

Lab is broken!

Ossie B. · 已于 over 2 years前审核

Soumen C. · 已于 over 2 years前审核

Avisek K. · 已于 over 2 years前审核

Monika G. · 已于 over 2 years前审核

Rohan P. · 已于 over 2 years前审核

Soumen C. · 已于 over 2 years前审核

Avisek K. · 已于 over 2 years前审核

Artur K. · 已于 over 2 years前审核

Gustavo Alberto V. · 已于 over 2 years前审核

Artur K. · 已于 over 2 years前审核

Vakcharla R. · 已于 over 2 years前审核

Beth D. · 已于 over 2 years前审核

Juan Alejandro O. · 已于 over 2 years前审核

OK

Jarosław K. · 已于 over 2 years前审核

I migrade 2x my stand alone to Cloud SQl sadly unable to positive check it. Name of migration job need to be that same as creating instance with is not written in task.

Mateusz K. · 已于 over 2 years前审核

Task 1 EXPLICITLY mentioned using the EXTERNAL IP Address of the VM Instance. I followed this instruction for two attempts that failed. Every other lab with a similar setup used the INTERNAL IP address instead. I used it in this last attempt and the lab finally completed.

Jose Alfron B. · 已于 over 2 years前审核

Santhosh Kumar M. · 已于 over 2 years前审核

Yuriy L. · 已于 over 2 years前审核

Jean-Luc A. · 已于 over 2 years前审核