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? (Choose three.)

The three correct actions focus on collecting relevant diagnostic information. Searching Stackdriver Logging for module-specific entries (A) is crucial because the new kernel module is the suspected cause, and its logs would provide direct insights. Connecting to the serial console (C) allows direct access to the VM's boot and kernel messages, which are essential for diagnosing kernel-related issues, especially if the VM is unresponsive. Adjusting the Stackdriver timeline and observing batch server metrics (E) helps correlate system performance (CPU, memory, disk I/O) with the failure event, identifying potential resource exhaustion or abnormal behavior caused by the module. Incorrect options: Reading the debug GCE Activity log (B) is less effective for application or kernel-level issues; it primarily tracks GCE infrastructure events. Identifying live migration events (D) is generally irrelevant to a kernel module failure. Exporting a debug VM image (F) is overly complex and time-consuming for initial diagnostics, and a local server might not accurately replicate the GCE environment.