nerdexam
Google

PROFESSIONAL-CLOUD-DEVOPS-ENGINEER · Question #146

You support an application deployed on Compute Engine. The application connects to a Cloud SQL instance to store and retrieve data. After an update to the application, users report errors showing data

The correct answer is B. Use Stackdriver Profiler to visualize the resources utilization throughout the application.. Given database timeout errors following an application update despite stable user count, utilize Cloud Profiler to analyze the application's resource utilization and execution paths to pinpoint performance bottlenecks or inefficient code introduced by the update that could be cau

Submitted by tyler.j· Apr 18, 2026Managing a service incident

Question

You support an application deployed on Compute Engine. The application connects to a Cloud SQL instance to store and retrieve data. After an update to the application, users report errors showing database timeout messages. The number of concurrent active users remained stable. You need to find the most probable cause of the database timeout. What should you do?

Options

  • ACheck the serial port logs of the Compute Engine instance.
  • BUse Stackdriver Profiler to visualize the resources utilization throughout the application.
  • CDetermine whether there is an increased number of connections to the Cloud SQL instance.
  • DUse Cloud Security Scanner to see whether your Cloud SQL is under a Distributed Denial of

How the community answered

(54 responses)
  • A
    11% (6)
  • B
    63% (34)
  • C
    20% (11)
  • D
    6% (3)

Why each option

Given database timeout errors following an application update despite stable user count, utilize Cloud Profiler to analyze the application's resource utilization and execution paths to pinpoint performance bottlenecks or inefficient code introduced by the update that could be causing the database timeouts.

ACheck the serial port logs of the Compute Engine instance.

Serial port logs are primarily for low-level system and boot diagnostics, not for troubleshooting application-specific database timeout issues after an update.

BUse Stackdriver Profiler to visualize the resources utilization throughout the application.Correct

After an application update, Cloud Profiler can visualize the application's resource utilization (CPU, memory, I/O, contention), helping to identify if the update introduced inefficient code, slow queries, or contention that causes database operations to time out even with a stable user count.

CDetermine whether there is an increased number of connections to the Cloud SQL instance.

While increased connections can cause timeouts, the question states active users remained stable, making an application change (diagnosable by profiler) a more probable cause for connection-related issues like leaks or inefficient use rather than just an overall load increase; Cloud Monitoring would typically be used to check this metric.

DUse Cloud Security Scanner to see whether your Cloud SQL is under a Distributed Denial of

Cloud Security Scanner is for security vulnerabilities, and a DDoS attack is less probable as the primary cause for database timeouts occurring specifically 'after an update to the application' compared to an application-introduced performance bug.

Concept tested: Application performance debugging, Cloud Profiler, database timeouts

Source: https://cloud.google.com/profiler/docs/concepts/overview

Topics

#Application performance tuning#Cloud Profiler#Troubleshooting#Database timeouts

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice