After installing a Linux kernel module on batch GCE VMs, 50% of servers failed nightly runs. Which three actions gather diagnostic data? (Choose three.)

Searching Stackdriver Logging for module-specific entries helps identify errors or warnings related to the kernel module. Connecting to the VM serial console allows direct access to system boot messages and kernel logs, which are crucial for diagnosing kernel module issues, even if the VM is otherwise unresponsive. Adjusting the Stackdriver time range to the failure window and inspecting batch server metrics can reveal correlations between resource utilization (CPU, memory, disk I/O) and the failures, indicating potential resource contention or module-induced performance problems. Reading the debug GCE Activity log is less effective as it primarily tracks GCE infrastructure events, not guest OS kernel module issues. Checking for live migration events is unlikely to be the root cause of a kernel module failure across 50% of servers. Exporting a VM to an image is a time-consuming and complex process that doesn't directly provide real-time diagnostic data from the failing environment.