Umgebung für die Anwendungsentwicklung in Google Cloud einrichten: Challenge-Lab Rezensionen

Pablo y. · Vor 27 Tage überprüft

Julio Cesar L. · Vor 27 Tage überprüft

Suphlay K. · Vor 27 Tage überprüft

Mike G. · Vor 27 Tage überprüft

Souravi B. · Vor 27 Tage überprüft

Коваль С. · Vor 27 Tage überprüft

SEBASTIAN P. · Vor 27 Tage überprüft

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. · Vor 27 Tage überprüft

Sejal C. · Vor 27 Tage überprüft

Yeison J. · Vor 27 Tage überprüft

Sahil L. · Vor 27 Tage überprüft

Royston P. · Vor 27 Tage überprüft

Luis Enrique S. · Vor 27 Tage überprüft

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. · Vor 27 Tage überprüft

Rafael T. · Vor 27 Tage überprüft

Antonio F. · Vor 27 Tage überprüft

Nadim B. · Vor 27 Tage überprüft

Mohammad Faheem A. · Vor 27 Tage überprüft

Valentina G. · Vor 27 Tage überprüft

Pedro A. M. · Vor 27 Tage überprüft

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. · Vor 27 Tage überprüft

Mike G. · Vor 27 Tage überprüft

Willian C. · Vor 27 Tage überprüft

Qasim H. · Vor 27 Tage überprüft

Ritwij R. · Vor 27 Tage überprüft