Accessing the Google Cloud Console and Cloud Shell Reviews

PRANEETH G. · Reviewed 17 days ago

YALAMAREDDY PREETHI 2. · Reviewed 17 days ago

Mateusz B. · Reviewed 17 days ago

Shreya U. · Reviewed 17 days ago

DEEKSHA MURALIDHARAN 2. · Reviewed 17 days ago

PRANEETH G. · Reviewed 17 days ago

Sahil c. · Reviewed 17 days ago

JAYASHREE S. · Reviewed 17 days ago

Maciej M. · Reviewed 17 days ago

SHIV K. · Reviewed 17 days ago

Emilia M. · Reviewed 17 days ago

Sahil c. · Reviewed 17 days ago

Helma Z. · Reviewed 17 days ago

Sahak S. · Reviewed 17 days ago

Martynas V. · Reviewed 17 days ago

Nisha M. · Reviewed 17 days ago

Aditi K. · Reviewed 17 days ago

Mazen M. · Reviewed 17 days ago

Sergei K. · Reviewed 17 days ago

Miguel V. · Reviewed 17 days ago

Alex A. · Reviewed 17 days ago

Ankit G. · Reviewed 17 days ago

YASH R. · Reviewed 17 days ago

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. · Reviewed 17 days ago

VIGNESH M. · Reviewed 17 days ago