Topic 1 Question 34
3 つ選択Your development team has installed a new Linux kernel module on the batch servers in Google Compute Engine (GCE) virtual machines (VMs) to speed up the nightly batch process. Two days after the installation, 50% of the batch servers failed the nightly batch run. You want to collect details on the failure to pass back to the development team. Which three actions should you take?
Use Stackdriver Logging to search for the module log entries
Read the debug GCE Activity log using the API or Cloud Console
Use gcloud or Cloud Console to connect to the serial console and observe the logs
Identify whether a live migration event of the failed server occurred, using in the activity log
Adjust the Google Stackdriver timeline to match the failure time, and observe the batch server metrics
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
ユーザの投票
コメント(17)
ACE A. Use Stackdriver Logging to search for the module log entries = Check logs C. Use gcloud or Cloud Console to connect to the serial console and observe the logs = Check grub messages, remember new kernel module was installed. E. Adjust the Google Stackdriver timeline to match the failure time, and observe the batch server metrics = Zoom into the time window when problem happened.
👍 38rishab862021/06/04Go for A,B,E. C is when the VM is running , but in this case the sentence says “recollect”. It means that “error ever” already happened.
👍 8haroldbenites2021/12/04I would say that Q26 = ABE A - since it investigates logs of Linux kernel module installed recently. For that Log Agent should be installed on VMs and Linux syslog is streamed by default to Stackdriver Logging via agent. So, this answer is relevant to Q's context, it checks if new Linux kernel runs OK. B - investigates "app-level" issues on GCE, logs API called from this VM, system events, etc. C - review of Serial Log is useful only for HW/OS crashes, and only during short period of time (since only last 1MB of logs are stored there, if more logs needed then they are streamed to Stackdriver logging). So, this option doesn't fit 2 days period and also serves different failure types. D - live migration event is irrelevant to this Q (transferring hot/running context of one VM to another transparently, so original VM can be maintained – BIOS/HW updates). Even if that happens, then GCE activity logs in B should cover this. E - monitoring of metrics at the time of failure makes sense for troubleshooting. F - smth long and ridiculous.
👍 6MaxNRG2021/10/24
シャッフルモード