You made a typo in a low-level Linux configuration file that prevents your Compute Engine instance from booting to a normal run level. You just created the Compute Engine instance today and have done

Question

Options

• ADownload the file using scp, change the file, and then upload the modified version
• BConfigure and log in to the Compute Engine instance through SSH, and change the file
• CConfigure and log in to the Compute Engine instance through the serial port, and change the file
• DConfigure and log in to the Compute Engine instance using a remote desktop client, and change

• A
  6% (2)
• B
  3% (1)
• C
  72% (23)
• D
  19% (6)

Explanation

When a Compute Engine instance cannot boot to a normal run level, standard access methods fail: SSH (B) requires the OS networking stack to be running, SCP (A) also depends on SSH, and Remote Desktop (D) requires a fully booted OS with a display manager. The serial port console provides out-of-band access to the instance at the hardware level, bypassing the OS boot process. By enabling the serial port and logging in via the Cloud Console or gcloud, you can access an emergency shell or single-user mode to fix the misconfigured file. This is the standard recovery approach for non-bootable Linux instances on GCP.

No community discussion yet for this question.