Set Up an App Dev Environment on Google Cloud: Challenge Lab Reviews

Binisa G. · Reviewed 27 days ago

Aditya M. · Reviewed 27 days ago

ashish s. · Reviewed 27 days ago

Pablo y. · Reviewed 27 days ago

Julio Cesar L. · Reviewed 27 days ago

Suphlay K. · Reviewed 27 days ago

Mike G. · Reviewed 27 days ago

Souravi B. · Reviewed 27 days ago

Коваль С. · Reviewed 27 days ago

SEBASTIAN P. · Reviewed 27 days ago

The lab assume to many things that if you are not a devops you can do it, without help. Its a shame

Facundo Gonzalo U. · Reviewed 27 days ago

Sejal C. · Reviewed 27 days ago

Yeison J. · Reviewed 27 days ago

Sahil L. · Reviewed 27 days ago

Royston P. · Reviewed 27 days ago

Luis Enrique S. · Reviewed 27 days ago

I created the Cloud Function successfully with the correct trigger, it worked, the thumbnail was created, and yet the lab failed to recognise that the funciton was created and therefore did not give me the correct score.

Felipe C. · Reviewed 27 days ago

Rafael T. · Reviewed 27 days ago

Antonio F. · Reviewed 27 days ago

Nadim B. · Reviewed 27 days ago

Mohammad Faheem A. · Reviewed 27 days ago

Valentina G. · Reviewed 27 days ago

Pedro A. M. · Reviewed 27 days ago

The lab experience was extremely frustrating and consumed a huge amount of time and credits for issues unrelated to the actual exercise. Main problems encountered: * The `index.js` code box silently truncated the code. Part of the file disappeared without warning, causing broken deployments and syntax errors. I lost around 10 minutes debugging something caused by the UI itself. * The account/session repeatedly disconnected during the lab. * Identity confirmation/password verification frequently failed even with the correct credentials. * The web console became practically unusable, forcing me to complete most tasks entirely through Cloud Shell CLI. * IAM permission propagation delays are excessive. Even trivial role assignments required waiting 2–3 minutes before becoming effective. * Eventarc / Pub/Sub / Cloud Functions permissions are very fragile and poorly initialized in fresh lab projects. * Trigger creation for Cloud Storage functions failed multiple times because required service accounts and permissions were not automatically configured. * Uploading files to Cloud Storage and waiting for triggers/functions to execute also introduced long delays, making debugging extremely slow. * Error messages were often incomplete or misleading, especially around Eventarc Service Agents and Cloud Storage Pub/Sub permissions. Suggestions for improvement: * Ensure code editors never truncate pasted code silently. * Pre-provision Eventarc and required service agents before the lab starts. * Reduce IAM propagation delays or add automatic retries during deployment. * Improve error diagnostics for Cloud Functions Gen2 + Eventarc + Cloud Storage integrations. * Stabilize authentication/session handling in temporary Qwiklabs accounts. * Provide CLI-first instructions for advanced labs instead of relying heavily on the unstable UI. The technical content of the lab is good, but the platform reliability and infrastructure delays make the experience unnecessarily difficult.

Gianluigi M. · Reviewed 27 days ago

Mike G. · Reviewed 27 days ago