Explanation:
The correct answers are A, C, and E. Option A (Stackdriver Logging) is essential for searching module-specific log entries, which can reveal errors or warnings from the new kernel module. Option C (serial console) provides low-level access to kernel messages, boot logs, and potential panic details, crucial for kernel module issues. Option E (Stackdriver timeline adjustment) allows correlation of server metrics with the failure time, identifying performance anomalies. Option B (GCE Activity log) is less suitable as it focuses on control plane events rather than kernel-level details. Option D (live migration) is irrelevant unless specified, and Option F (export VM) is impractical and inefficient for GCP troubleshooting.
Ultimate access to all questions.
No comments yet.
Your development team installed a new Linux kernel module on the batch servers in Google Compute Engine (GCE) virtual machines (VMs) to accelerate the nightly batch process. Two days after the installation, 50% of the batch servers failed the nightly batch run. You need to collect failure details to provide to the development team.
Which three actions should you take? (Choose three.)
A
Use Stackdriver Logging to search for the module log entries
B
Read the debug GCE Activity log using the API or Cloud Console
C
Use gcloud or Cloud Console to connect to the serial console and observe the logs
D
Identify whether a live migration event of the failed server occurred, using in the activity log
E
Adjust the Google Stackdriver timeline to match the failure time, and observe the batch server metrics
F
Export a debug VM into an image, and run the image on a local server where kernel log messages will be displayed on the native screen