Google Professional Cloud Database Engineer Question 112
Select 2Google Cloud PlatformYou are managing a Cloud SQL instance running MySQL for a critical application. The application team reports intermittent performance issues during peak traffic hours. You need to configure database monitoring and troubleshooting to identify the root cause of the performance issues. What steps should you take to effectively monitor and troubleshoot the database? (Choose TWO)
- A
Enable the Query Insights feature in Cloud SQL to analyze query performance and identify slow queries.
- B
Set up a Stackdriver (Cloud Monitoring) alert to notify you when CPU utilization exceeds a defined threshold.
- C
Increase the instance size of the Cloud SQL database to prevent further performance issues.
- D
Periodically restart the Cloud SQL instance during peak traffic hours to clear any potential bottlenecks.
- E
Use the slow query log feature to capture queries that exceed a specified execution time.
Show answer and explanation
Correct answers: A, B
Explanation
To effectively monitor and troubleshoot database performance issues, you should use tools like Query Insights to analyze query performance and set up Cloud Monitoring alerts to track resource usage. These steps help identify the root cause of the problem, such as inefficient queries or resource bottlenecks, rather than applying temporary fixes like restarting the instance or increasing its size without proper analysis.
- A. Correct.
Enabling Query Insights allows you to monitor and analyze query performance in real-time, helping you identify slow or problematic queries that could be causing performance issues.
- B. Correct.
Setting up Cloud Monitoring alerts for CPU utilization allows you to proactively respond to high resource usage, which could be a symptom of the performance issues during peak times.
- C. Incorrect.
Increasing the instance size without investigating the root cause may temporarily alleviate the issue but is not a troubleshooting step or monitoring configuration.
- D. Incorrect.
Restarting the instance during peak traffic hours is not a recommended best practice and does not help in identifying the root cause of performance issues.
- E. Incorrect.
While slow query logs can be useful, enabling Query Insights provides a more comprehensive and real-time analysis of query performance, making it a better option for monitoring and troubleshooting.