Answer-first summary for fast verification
Answer: In the GCP Console, navigate to Stackdriver Logging. Consult logs for (GKE) and Cloud SQL.
The correct answer is C. In the case of a post-mortem analysis, the first step is to gather detailed logs that can provide insights into what went wrong. By navigating to Stackdriver Logging (now known as Cloud Logging) in the GCP Console, you can consult the logs for both GKE and Cloud SQL. This log analysis will help you identify the root cause of the database connection issues reported by the application. Options A and D suggest immediate actions to try to fix the issue without understanding its root cause, and option B is irrelevant as the Cloud Build Editor role is not necessary for the Cloud SQL proxy container.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
You have deployed an application to Google Kubernetes Engine (GKE) to manage containerized applications. To make the Cloud SQL database accessible to services running on Kubernetes, you are using the Cloud SQL proxy container. However, you are notified that the application is reporting database connection issues. Company policies mandate performing a detailed post-mortem analysis to identify the root cause and ensure it does not happen again. What should you do?
A
Use gcloud sql instances restart.
B
Validate that the Service Account used by the Cloud SQL proxy container still has the Cloud Build Editor role.
C
In the GCP Console, navigate to Stackdriver Logging. Consult logs for (GKE) and Cloud SQL.
D
In the GCP Console, navigate to Cloud SQL. Restore the latest backup. Use kubectl to restart all pods.