Google Associate Cloud Engineer Question 313
Select 3Google Cloud PlatformYou are a Google Cloud Associate Cloud Engineer tasked with diagnosing an issue in a web application hosted on Google Cloud Platform. Users are reporting intermittent connectivity issues. Which of the following steps should you take to effectively diagnose and identify the root cause of the problem using Google Cloud's diagnostic tools?
- A
Check the Google Cloud Console's Operations suite for any alerts or logs related to the application's resources.
- B
Use Google Cloud Shell to manually inspect the source code for potential bugs.
- C
Enable VPC Flow Logs for the subnet where the application is hosted to monitor network traffic.
- D
Review the Stackdriver Trace data to analyze request latency and identify potential bottlenecks.
- E
Manually restart all Compute Engine instances to see if the issue resolves.
Show answer and explanation
Correct answers: A, C, D
Explanation
Using Google Cloud's diagnostic tools such as Operations suite, VPC Flow Logs, and Stackdriver Trace provides a structured approach to diagnose and identify the root cause of application connectivity issues. These tools offer detailed insights into resource performance, network traffic, and request latency, facilitating effective troubleshooting.
- A. Correct.
The Google Cloud Console's Operations suite (formerly Stackdriver) provides centralized logging and monitoring, which is crucial for identifying issues related to the application's resources.
- B. Incorrect.
While manually inspecting the source code could be useful, it is not the most efficient method to start diagnosing connectivity issues with the application.
- C. Correct.
Enabling VPC Flow Logs allows you to capture information about the IP traffic going to and from network interfaces, which can help identify network-related issues.
- D. Correct.
Stackdriver Trace helps in analyzing the latency of requests and can identify bottlenecks in the application, making it useful for diagnosing performance issues.
- E. Incorrect.
Restarting Compute Engine instances without understanding the root cause is not a recommended practice and may not address the underlying issue.