Google Cloud Certified Professional Cloud Architect Practice Mode

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose AE1

  B - Cannot be this as Activity Logs track GCP-level events, like instance creation, deletion, metadata changes, and API calls. They do not contain OS-level debugging info or kernel/module failure data. D - Host Errors might cause 1 crash randomly. I see this happening at work all the time. But a bunch of them at once. Unlikely F - We know that this is only happening 50% of the time. How will you reproduce this locally? The other 50% of the time it works flawlessly

• Chose ACE1

  GCE Activity log does not provide debug logs as they lack kernel application-level details, while The serial console provides low level access to VMs boot and kernel logs. Therefore, C wins in this case.

• Chose ACE1

  A & E - Use Cloud Logging (Previously Stackdriver logging) search and filter module log entries. Provides syslog, kernel logs, app logs etc and can be filterer by VM name, time range, severity.. C - Serial console output - Kernel panics, boot failures or critical errors related to a kernel module often print messages directly to serial console before OS might even fully functional. [Option B could be helpful but for the scenario in question I won't go to GCE activities logs(Cloud Audit Logs) skipping C (Serial Console Output). It gives the information what's happening to VM from control pane's perspective, it won't directly tell me kernel module's internal errors... ]