Explanation:
When a Compute Engine instance cannot boot due to a configuration error, standard methods like SSH or SCP may not work because the SSH service depends on the system reaching a normal run level. Similarly, remote desktop clients require GUI services which are unlikely to be running. The correct approach is to use the serial port console, which provides low-level access to the instance even if it fails to boot properly. This allows direct troubleshooting and editing of configuration files without relying on the instance's network services.
Ultimate access to all questions.
How can you fix a boot failure on a newly created Compute Engine instance caused by a typo in a low-level Linux configuration file, when no other maintenance has been performed besides editing files?
A
Download the file using scp, change the file, and then upload the modified version
B
Configure and log in to the Compute Engine instance through SSH, and change the file
C
Configure and log in to the Compute Engine instance through the serial port, and change the file
D
Configure and log in to the Compute Engine instance using a remote desktop client, and change the file
No comments yet.