Como configurar um ambiente de desenvolvimento de apps no Google Cloud: laboratório com desafio avaliações

Luis Enrique S. · Revisado há 4 months

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. · Revisado há 4 months

Rafael T. · Revisado há 4 months

Antonio F. · Revisado há 4 months

Nadim B. · Revisado há 4 months

Mohammad Faheem A. · Revisado há 4 months

Valentina G. · Revisado há 4 months

Pedro A. M. · Revisado há 4 months

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. · Revisado há 4 months

Mike G. · Revisado há 4 months

Willian C. · Revisado há 4 months

Qasim H. · Revisado há 4 months

Ritwij R. · Revisado há 4 months

great test

Manish J. · Revisado há 4 months

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. · Revisado há 4 months

Marc P. · Revisado há 4 months

KEVIN YECITH M. · Revisado há 4 months

Selvakumar B. · Revisado há 4 months

Sifiso D. · Revisado há 4 months

naga p. · Revisado há 4 months

Ankit K. · Revisado há 4 months

Mansoor A. · Revisado há 4 months

pal c. · Revisado há 4 months

Jose M G. · Revisado há 4 months

i have problems with the task to create run function

Limbert A. · Revisado há 4 months