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

Loic N. · Reviewed 2 ay ago

David D. · Reviewed 2 ay ago

Vitalii L. · Reviewed 2 ay ago

RAUSHAN Y. · Reviewed 2 ay ago

Mukesh Kumar Y. · Reviewed 2 ay ago

John L. · Reviewed 2 ay ago

Shawn M. · Reviewed 2 ay ago

Jason E. · Reviewed 2 ay 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 2 ay ago

Brajesh S. · Reviewed 2 ay ago

Shaik Salima G. · Reviewed 2 ay ago

Sumesh S. · Reviewed 2 ay ago

Ram K. · Reviewed 2 ay ago

Lalit P. · Reviewed 2 ay ago

Sachin D. · Reviewed 2 ay ago

Shivashankar S. · Reviewed 2 ay ago

YOGESH R. · Reviewed 2 ay ago

Tomasz G. · Reviewed 2 ay ago

Raju V. · Reviewed 2 ay ago

at last thanks!

Jamiil Toure A. · Reviewed 2 ay ago

Raju V. · Reviewed 2 ay ago

ee

sanjay v. · Reviewed 2 ay 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 2 ay ago

Aditi J. · Reviewed 2 ay ago

Szymon J. · Reviewed 2 ay ago