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

Shawn M. · Reviewed 27 gün ago

Jason E. · Reviewed 27 gün 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 gün ago

Brajesh S. · Reviewed 27 gün ago

Shaik Salima G. · Reviewed 27 gün ago

Sumesh S. · Reviewed 27 gün ago

Ram K. · Reviewed 27 gün ago

Lalit P. · Reviewed 27 gün ago

Sachin D. · Reviewed 27 gün ago

Shivashankar S. · Reviewed 27 gün ago

YOGESH R. · Reviewed 27 gün ago

Tomasz G. · Reviewed 27 gün ago

Raju V. · Reviewed 27 gün ago

at last thanks!

Jamiil Toure A. · Reviewed 27 gün ago

Raju V. · Reviewed 27 gün ago

ee

sanjay v. · Reviewed 27 gün 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 27 gün ago

Aditi J. · Reviewed 28 gün ago

Szymon J. · Reviewed 28 gün ago

Danushka S. · Reviewed 28 gün ago

Vicente O. · Reviewed 28 gün ago

Iqbaal R. · Reviewed 28 gün ago

Ibrahim A. · Reviewed 28 gün ago

server error 500

fauzeya n. · Reviewed 28 gün ago

alola o. · Reviewed 28 gün ago