Answer-first summary for fast verification
Answer: Check Compute Engine OS logs using the serial port, and check the Cloud Logging logs to confirm access to the serial port.
To troubleshoot a Compute Engine image that isn't booting, the most effective first step is to check the serial port logs. Google Cloud provides serial console output, which captures boot-time messages, kernel errors, or service failures. Option D suggests checking Compute Engine OS logs via the serial port and validating access through Cloud Logging. This approach is non-destructive and directly addresses boot-related issues. Other options, like rebuilding the image locally (C) or exporting the disk (B), are less immediate or more complex. Option A (rebuilding in a new branch) skips root-cause analysis. Thus, D is the best choice for initial investigation.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
As a developer collaborating with the CI/CD team to debug a new feature, you encounter an issue where a Compute Engine image built using HashiCorp Packer from your development branch fails to boot. The image was created successfully, but it does not start properly. How should you proceed with the CI/CD team to investigate this problem?
A
Create a new feature branch, and ask the build team to rebuild the image.
B
Shut down the deployed virtual machine, export the disk, and then mount the disk locally to access the boot logs.
C
Install Packer locally, build the Compute Engine image locally, and then run it in your personal Google Cloud project.
D
Check Compute Engine OS logs using the serial port, and check the Cloud Logging logs to confirm access to the serial port.