A recent Compute Engine VM won't boot due to a typo in a low-level Linux config file and you haven't performed other maintenance. How do you fix the file?

The correct answer is to configure and log in to the Compute Engine instance through the serial port, and change the file. When a VM fails to boot due to a configuration error, standard SSH access is unavailable because the operating system isn't fully loaded. The serial console provides a low-level, text-based interface that operates independently of the VM's operating system, allowing you to debug boot issues, edit critical configuration files, and access the GRUB bootloader or single-user mode. Downloading and re-uploading the file via scp is not possible if the VM cannot boot, as scp relies on a running SSH server. Logging in via SSH is also not possible for the same reason. A remote desktop client is used for graphical interfaces and would not be available or useful for a low-level boot issue on a Linux VM.