Accessing the Google Cloud Console and Cloud Shell avis

PRANEETH G. · Examiné il y a 17 jours

YALAMAREDDY PREETHI 2. · Examiné il y a 17 jours

Mateusz B. · Examiné il y a 17 jours

Shreya U. · Examiné il y a 17 jours

DEEKSHA MURALIDHARAN 2. · Examiné il y a 17 jours

PRANEETH G. · Examiné il y a 17 jours

Sahil c. · Examiné il y a 17 jours

JAYASHREE S. · Examiné il y a 17 jours

Maciej M. · Examiné il y a 17 jours

SHIV K. · Examiné il y a 17 jours

Emilia M. · Examiné il y a 17 jours

Sahil c. · Examiné il y a 17 jours

Helma Z. · Examiné il y a 17 jours

Sahak S. · Examiné il y a 17 jours

Martynas V. · Examiné il y a 17 jours

Nisha M. · Examiné il y a 17 jours

Aditi K. · Examiné il y a 17 jours

Mazen M. · Examiné il y a 17 jours

Sergei K. · Examiné il y a 17 jours

Miguel V. · Examiné il y a 17 jours

Alex A. · Examiné il y a 17 jours

Ankit G. · Examiné il y a 17 jours

YASH R. · Examiné il y a 17 jours

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. · Examiné il y a 17 jours

VIGNESH M. · Examiné il y a 17 jours