Migrate a MySQL Database to Google Cloud SQL: Challenge Lab Reviews

Loic N. · Reviewed شهران ago

David D. · Reviewed شهران ago

Vitalii L. · Reviewed شهران ago

RAUSHAN Y. · Reviewed شهران ago

Mukesh Kumar Y. · Reviewed شهران ago

John L. · Reviewed شهران ago

Shawn M. · Reviewed شهران ago

Jason E. · Reviewed شهران 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 شهران ago

Brajesh S. · Reviewed شهران ago

Shaik Salima G. · Reviewed شهران ago

Sumesh S. · Reviewed شهران ago

Ram K. · Reviewed شهران ago

Lalit P. · Reviewed شهران ago

Sachin D. · Reviewed شهران ago

Shivashankar S. · Reviewed شهران ago

YOGESH R. · Reviewed شهران ago

Tomasz G. · Reviewed شهران ago

Raju V. · Reviewed شهران ago

at last thanks!

Jamiil Toure A. · Reviewed شهران ago

Raju V. · Reviewed شهران ago

ee

sanjay v. · Reviewed شهران ago

The lab environment is fundamentally broken on provisioning. The blog VM instance deployed with a corrupted local MySQL init state and a completely missing /var/www/html/wordpress application directory. Because of this, the baseline data dump (wp_backup.sql) could not be restored at startup. Task 5 fails while the lab infrastructure builds resources exclusively in us-east1. Even after manually downloading the WordPress source, configuring the database manually, and injecting the expected tables/metadata, the validation check remains unreachable due to this network routing misalignment.

Ananth P. · Reviewed شهران ago

Aditi J. · Reviewed شهران ago

Szymon J. · Reviewed شهران ago