Accessing the Google Cloud Console and Cloud Shell Reviews

YALAMAREDDY PREETHI 2. · Reviewed 3 months ago

Mateusz B. · Reviewed 3 months ago

Shreya U. · Reviewed 3 months ago

DEEKSHA MURALIDHARAN 2. · Reviewed 3 months ago

PRANEETH G. · Reviewed 3 months ago

Sahil c. · Reviewed 3 months ago

JAYASHREE S. · Reviewed 3 months ago

Maciej M. · Reviewed 3 months ago

SHIV K. · Reviewed 3 months ago

Emilia M. · Reviewed 3 months ago

Sahil c. · Reviewed 3 months ago

Helma Z. · Reviewed 3 months ago

Sahak S. · Reviewed 3 months ago

Martynas V. · Reviewed 3 months ago

Nisha M. · Reviewed 3 months ago

Aditi K. · Reviewed 3 months ago

Mazen M. · Reviewed 3 months ago

Sergei K. · Reviewed 3 months ago

Miguel V. · Reviewed 3 months ago

Alex A. · Reviewed 3 months ago

Ankit G. · Reviewed 3 months ago

YASH R. · Reviewed 3 months 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 3 months ago

VIGNESH M. · Reviewed 3 months ago

Udhaya N. · Reviewed 3 months ago