將 MySQL 資料庫遷移至 Google Cloud SQL：挑戰實驗室 Reviews

Peter V. · Reviewed 25 days ago

Payal L. · Reviewed 25 days ago

Gauri L. · Reviewed 25 days ago

Gokul K. · Reviewed 25 days ago

Labs are great. But the UI of is awfull. Fix it please

Egor S. · Reviewed 25 days ago

instruction for --authorized-networks not clear (use range and not ip)

Yura T. · Reviewed 25 days ago

Vikranth R. · Reviewed 25 days ago

Luiz F. · Reviewed 26 days ago

Antonio Whinnes G. · Reviewed 26 days ago

Varsha P. · Reviewed 26 days ago

Hendy Chandra H. · Reviewed 26 days ago

Error

Sohail S. · Reviewed 26 days ago

localhost being used instead of the actual ip address is kind of annoying.

Deeksha C. · Reviewed 26 days ago

shyamkumar m. · Reviewed 26 days ago

darren c. · Reviewed 26 days ago

doesn't work (task 5) and cannot understand why (have tried everything)

Deeksha C. · Reviewed 26 days ago

Loic N. · Reviewed 26 days ago

David D. · Reviewed 26 days ago

Vitalii L. · Reviewed 26 days ago

RAUSHAN Y. · Reviewed 26 days ago

Mukesh Kumar Y. · Reviewed 26 days ago

John L. · Reviewed 26 days ago

Shawn M. · Reviewed 26 days ago

Jason E. · Reviewed 26 days ago

This lab has a validation bug in Task 3. The Cloud SQL instance automatically authorizes RFC 1918 IP ranges (including 10.142.0.3 from the blog VM), but the lab's scoring system fails to detect this implicit authorization and requires manual addition of the IP, which the Google Cloud API explicitly blocks. All manual steps were completed successfully and the WordPress blog is fully functional with the Cloud SQL database. Please fix the validation logic to recognize automatically authorized IP ranges.

Alexandre C. · Reviewed 27 days ago