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

Binisa G. · Reviewed 6 أشهر ago

Aditya M. · Reviewed 6 أشهر ago

ashish s. · Reviewed 6 أشهر ago

Pablo y. · Reviewed 6 أشهر ago

Julio Cesar L. · Reviewed 6 أشهر ago

Suphlay K. · Reviewed 6 أشهر ago

Mike G. · Reviewed 6 أشهر ago

Souravi B. · Reviewed 6 أشهر ago

Коваль С. · Reviewed 6 أشهر ago

SEBASTIAN P. · Reviewed 6 أشهر 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 6 أشهر ago

Sejal C. · Reviewed 6 أشهر ago

Yeison J. · Reviewed 6 أشهر ago

Sahil L. · Reviewed 6 أشهر ago

Royston P. · Reviewed 6 أشهر ago

Luis Enrique S. · Reviewed 6 أشهر 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 6 أشهر ago

Rafael T. · Reviewed 6 أشهر ago

Antonio F. · Reviewed 6 أشهر ago

Nadim B. · Reviewed 6 أشهر ago

Mohammad Faheem A. · Reviewed 6 أشهر ago

Valentina G. · Reviewed 6 أشهر ago

Pedro A. M. · Reviewed 6 أشهر 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 6 أشهر ago

Mike G. · Reviewed 6 أشهر ago