Google Professional Cloud DevOps Engineer Question 167
Select 3Google Cloud PlatformYour team manages a web application running on Google Kubernetes Engine (GKE) that is experiencing intermittent crashes. You want to use Google Cloud Error Reporting to identify recurring errors and prioritize fixes. What steps should you take to enable Error Reporting for this application?
- A
Ensure the application writes error logs with a recognized format to stdout or stderr.
- B
Enable the Error Reporting API in your Google Cloud project.
- C
Install a third-party library to parse logs and send errors to Error Reporting.
- D
Ensure Stackdriver Logging (Cloud Logging) is enabled in your GKE cluster.
- E
Manually tag each error occurrence in the source code with a unique identifier.
Show answer and explanation
Correct answers: A, B, D
Explanation
To use Google Cloud Error Reporting with a GKE application, the application must log errors in a recognized format (e.g., stack traces) to stdout or stderr. Cloud Logging must also be enabled to capture the logs. Finally, the Error Reporting API must be enabled in the Google Cloud project. These configurations allow Error Reporting to automatically group, display, and prioritize recurring errors, without requiring manual tagging or third-party tools.
- A. Correct.
Correct. Google Cloud Error Reporting automatically identifies and processes errors from logs if they are in a recognized format (e.g., stack traces). Writing errors to stdout or stderr is sufficient for GKE applications.
- B. Correct.
Correct. The Error Reporting API must be enabled in your project to allow the service to process and display errors.
- C. Incorrect.
Incorrect. No third-party library is required to use Google Cloud Error Reporting as it integrates seamlessly with Cloud Logging.
- D. Correct.
Correct. Cloud Logging must be enabled to capture application logs, which are then analyzed by Error Reporting.
- E. Incorrect.
Incorrect. Manually tagging errors is not required for Error Reporting. The service automatically groups similar errors based on stack traces or message patterns.