Como acessar o Console do Google Cloud e o Cloud Shell avaliações

Mateusz B. · Revisado há 23 days

Shreya U. · Revisado há 23 days

DEEKSHA MURALIDHARAN 2. · Revisado há 23 days

PRANEETH G. · Revisado há 23 days

Sahil c. · Revisado há 23 days

JAYASHREE S. · Revisado há 23 days

Maciej M. · Revisado há 23 days

SHIV K. · Revisado há 23 days

Emilia M. · Revisado há 23 days

Sahil c. · Revisado há 23 days

Helma Z. · Revisado há 23 days

Sahak S. · Revisado há 23 days

Martynas V. · Revisado há 23 days

Nisha M. · Revisado há 23 days

Aditi K. · Revisado há 24 days

Mazen M. · Revisado há 24 days

Sergei K. · Revisado há 24 days

Miguel V. · Revisado há 24 days

Alex A. · Revisado há 24 days

Ankit G. · Revisado há 24 days

YASH R. · Revisado há 24 days

Lab issues identified during the session: APT Package Manager Lock: Upon starting the VM, the system immediately triggers background security updates that hold the dpkg lock for several minutes. This prevents the manual installation of nginx as instructed, causing "Could not get lock" errors. The lab should include a wait command or pre-install the service. Serial Port Metadata Conflict: The current UI for enabling the serial port via metadata is outdated. The Google Cloud Console now triggers a red validation error, forcing users to find the new "Remote Access" section instead of following the manual metadata entry shown in the instructions. Validation Lag: There is a significant delay (over 1-2 minutes) between completing the index.html task and the "Check my progress" button recognizing the change, even when curl localhost confirms the file is correctly served. Suggestion: Please update the instructions to account for background system updates and the new UI layout for serial port access.

Luis M. · Revisado há 24 days

VIGNESH M. · Revisado há 24 days

Udhaya N. · Revisado há 24 days

MATAM PRAJWAL 2. · Revisado há 24 days